Public report of rjsf-team/react-jsonschema-form, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 04:12 UTC · Survey ID cd_ee6ce6127edf439183da7d1bc5963848

rjsf-team/react-jsonschema-form

Measured 17 November 2026, 04:10 UTC, at code version 41d54a8

First survey, so nothing to compare with yet
CAI score 66.9out of 100 Adequate
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 83,291 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Maturity, 64.4

Findings by how serious they are

42 critical 559 serious 84 minor

7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 04:10 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

74of 74 dimensions measured by tools.
671of 685 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
74dimensions across 7 lenses, read from 83,291 lines of product code in 17 projects.
Chapters

Executive summary

rjsf-team/react-jsonschema-form falls short of our standard for production, in part because the project keeps no record of its design decisions. It scores 66.9 out of 100 and is rated Adequate, and 40 of its 42 critical findings are security problems.

Maturity, at 64.4, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 2.5 points.

Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two automatic updates take new releases before a bad one can be spotted, and two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, setting a waiting period for automatic updates and fixing the weaknesses the scanner points to would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the place where the code runs text as code or as a command needs a direct call instead. The form field without a label needs a label.

The product code is 83,291 lines, about €300,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Maturity 64.4 · counts for 46%Accessibility 65.8 · counts for 25%Code Health 66.7 · counts for 14%Production Readiness 67.9 · counts for 8%Security and Compliance 74.2 · counts for 4%Architecture 96.4 · counts for 2%Performance 100.0 · counts for 1%

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

Code composition: what the lines of code are
Product code 34%Tests 66%
Rebuild cost: about €300,000 · Estimate
Cost to rebuild€100,000 to €500,000, for 1,667 to 5,288 hours of work, about 2.1 person-years for 1 to 4 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 67. 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.
SizeMedium: 83,291 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.
Raises the score by about 2.5 points · Low effort · ADR Quality
2
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.
Raises the score by about 2.1 points · Medium effort · Architecture documentation
3
Resolve the 18 redundant comment finding(s) in Comment Value — start with getDefaultFormStateTest.ts (4), validator.test.ts (3), REDACTED (2).
Raises the score by about 0.7 points · Medium effort · Comment Value

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Files that change often carry extra risk · Combined risk
One file is changed often and is hard to read, which makes it the likeliest place for a mistake. It also has under half its code tested, or was written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to this file therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (80 files) · Code Coverage (13 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: DemoFrame.tsx
What to do: Add tests to these files and have a second person review every change to them, starting with DemoFrame.tsx.
Where the investment is most exposed · Value at risk
This code would cost about €300,000 to build again, about 2.1 person-years of work. Its weakest lens is Maturity, at 64.4 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2.5 points for low effort, because it clears the 1 ADR Quality 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.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 10% on every change. The history of the code shows how much it changes: about 778,895 lines over the last 90 days, which is about 3,158,852 lines a year. At that pace, the extra work comes to an estimated 357.3 to 2144.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch @rjsf/antd antd @rjsf/core core @rjsf/antd->@rjsf/core @rjsf/utils utils @rjsf/antd->@rjsf/utils @rjsf/bootstrap3 bootstrap3 @rjsf/bootstrap3->@rjsf/core @rjsf/bootstrap3->@rjsf/utils @rjsf/chakra-ui chakra-ui @rjsf/chakra-ui->@rjsf/core @rjsf/chakra-ui->@rjsf/utils @rjsf/core->@rjsf/utils @rjsf/validator-ajv8 validator-ajv8 @rjsf/core->@rjsf/validator-ajv8 @rjsf/daisyui daisyui @rjsf/daisyui->@rjsf/core @rjsf/daisyui->@rjsf/utils @rjsf/fluentui-rc fluentui-rc @rjsf/fluentui-rc->@rjsf/core @rjsf/fluentui-rc->@rjsf/utils @rjsf/mantine mantine @rjsf/mantine->@rjsf/core @rjsf/mantine->@rjsf/utils @rjsf/mui mui @rjsf/mui->@rjsf/core @rjsf/mui->@rjsf/utils @rjsf/playground playground @rjsf/playground->@rjsf/antd @rjsf/playground->@rjsf/bootstrap3 @rjsf/playground->@rjsf/chakra-ui @rjsf/playground->@rjsf/core @rjsf/playground->@rjsf/daisyui @rjsf/playground->@rjsf/fluentui-rc @rjsf/playground->@rjsf/mantine @rjsf/playground->@rjsf/mui @rjsf/react-bootstrap react-bootstrap @rjsf/playground->@rjsf/react-bootstrap @rjsf/shadcn shadcn @rjsf/playground->@rjsf/shadcn @rjsf/playground->@rjsf/utils @rjsf/playground->@rjsf/validator-ajv8 @rjsf/validator-ata validator-ata @rjsf/playground->@rjsf/validator-ata @rjsf/validator-cfworker validator-cfworker @rjsf/playground->@rjsf/validator-cfworker @rjsf/react-bootstrap->@rjsf/core @rjsf/react-bootstrap->@rjsf/utils @rjsf/shadcn->@rjsf/core @rjsf/shadcn->@rjsf/utils @rjsf/snapshot-tests snapshot-tests @rjsf/snapshot-tests->@rjsf/core @rjsf/snapshot-tests->@rjsf/utils @rjsf/snapshot-tests->@rjsf/validator-ajv8 @rjsf/validator-ajv8->@rjsf/utils @rjsf/validator-ata->@rjsf/utils @rjsf/validator-cfworker->@rjsf/utils

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.

333 modules, with 262 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 chakra-ui.src.components.ui.field2 core.src.components.formState3 playground.src.components.ThemeSelector4 utils.src.schema.graph.parseSchemaGraph5 validator-ajv8.src.types6 chakra-ui.src.components.ui7 utils.src.schema.graph.provenance8 utils.src.schema.graph.validationTargets9 utils.src.schema.graph.mergePlan10 utils.src.schema.graph.recursionRule11 utils.src.schema.getClosestMatchingOption12 utils.src.types13 core.src.components.IChangeEvent14 core.src.components.fields.SchemaField15 core.src.components.sanitizeFieldTree16 core.src.hooks17 daisyui.src.utils18 daisyui.src.widgets19 mantine.src20 playground.src.components.Editors21 playground.src.components.Playground22 shadcn.src.components.ui23 utils.src.getNestedControlPresentation24 utils.src.schema.getDefaultFormState25 utils.src.schema.getUiRequiredErrorSchema26 utils.src.schema.graph27 validator-ajv8.src.precompiledValidator28 validator-ata.src.precompiledValidator29 validator-cfworker.src30 core.src.components.FormRef31 core.src.components.fields32 daisyui.src33 playground.src.components34 utils.src35 utils.src.schema36 validator-ajv8.src37 validator-ata.src38 core.src.components.Form39 core.src40 core.src.components
1 chakra-ui.src.components.ui.field
2 core.src.components.formState
3 playground.src.components.ThemeSelector
4 utils.src.schema.graph.parseSchemaGraph
5 validator-ajv8.src.types
6 chakra-ui.src.components.ui1
7 utils.src.schema.graph.provenance1
8 utils.src.schema.graph.validationTargets1
9 utils.src.schema.graph.mergePlan712
10 utils.src.schema.graph.recursionRule2
11 utils.src.schema.getClosestMatchingOption12
12 utils.src.types11
13 core.src.components.IChangeEvent1
14 core.src.components.fields.SchemaField1
15 core.src.components.sanitizeFieldTree12
16 core.src.hooks12
17 daisyui.src.utils2
18 daisyui.src.widgets11
19 mantine.src12
20 playground.src.components.Editors11
21 playground.src.components.Playground11
22 shadcn.src.components.ui11
23 utils.src.getNestedControlPresentation12
24 utils.src.schema.getDefaultFormState3211
25 utils.src.schema.getUiRequiredErrorSchema2
26 utils.src.schema.graph10412823
27 validator-ajv8.src.precompiledValidator34
28 validator-ata.src.precompiledValidator34
29 validator-cfworker.src32
30 core.src.components.FormRef21
31 core.src.components.fields133211
32 daisyui.src12
33 playground.src.components2121
34 utils.src131661
35 utils.src.schema6192626132
36 validator-ajv8.src521
37 validator-ata.src16121
38 core.src.components.Form361
39 core.src72
40 core.src.components14210245
Uses a module listed above itPart of a loopThe module itself
1 chakra-ui.src.components.ui.field2 core.src.components.formState3 playground.src.components.ThemeSelector4 utils.src.schema.graph.parseSchemaGraph5 validator-ajv8.src.types6 chakra-ui.src.components.ui7 utils.src.schema.graph.provenance8 utils.src.schema.graph.validationTargets9 utils.src.schema.graph.mergePlan10 utils.src.schema.graph.recursionRule11 utils.src.schema.getClosestMatchingOption12 utils.src.types13 core.src.components.IChangeEvent14 core.src.components.fields.SchemaField15 core.src.components.sanitizeFieldTree16 core.src.hooks17 daisyui.src.utils18 daisyui.src.widgets19 mantine.src20 playground.src.components.Editors21 playground.src.components.Playground22 shadcn.src.components.ui23 utils.src.getNestedControlPresentation24 utils.src.schema.getDefaultFormState25 utils.src.schema.getUiRequiredErrorSchema26 utils.src.schema.graph27 validator-ajv8.src.precompiledValidator28 validator-ata.src.precompiledValidator29 validator-cfworker.src30 core.src.components.FormRef31 core.src.components.fields32 daisyui.src33 playground.src.components34 utils.src35 utils.src.schema36 validator-ajv8.src37 validator-ata.src38 core.src.components.Form39 core.src40 core.src.componentschakra-ui.src.components.ui.field1core.src.components.formState2playground.src.components.ThemeSelector3utils.src.schema.graph.parseSchemaGraph4validator-ajv8.src.types5chakra-ui.src.components.ui6utils.src.schema.graph.provenance7utils.src.schema.graph.validationTargets8utils.src.schema.graph.mergePlan9utils.src.schema.graph.recursionRule10utils.src.schema.getClosestMatchingOption11utils.src.types12core.src.components.IChangeEvent13core.src.components.fields.SchemaField14core.src.components.sanitizeFieldTree15core.src.hooks16daisyui.src.utils17daisyui.src.widgets18mantine.src19playground.src.components.Editors20playground.src.components.Playground21shadcn.src.components.ui22utils.src.getNestedControlPresentation23utils.src.schema.getDefaultFormState24utils.src.schema.getUiRequiredErrorSchema25utils.src.schema.graph26validator-ajv8.src.precompiledValidator27validator-ata.src.precompiledValidator28validator-cfworker.src29core.src.components.FormRef30core.src.components.fields31daisyui.src32playground.src.components33utils.src34utils.src.schema35validator-ajv8.src36validator-ata.src37core.src.components.Form38core.src39core.src.components401117122121111121221112111111123211210412823343432211332111221211316616192626132521161213617214210245+293 more modules (most-connected shown)

At a glance — Code Health · 66.7 · Adequate · gated by D2 ·

At a glance — Architecture · 96.4 · Exemplary ·

At a glance — Maturity · 64.4 · Adequate · gated by M2 ·

At a glance — Readiness · 67.9 · Adequate · gated by P2 ·

At a glance — Security · 74.2 · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 65.8 · Adequate ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection47High / Critical
A03:2025 — Software Supply Chain Failures10Medium

Roadmap

Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json; 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; Adopt pino (or winston) and log at meaningful points in the services you run.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.+2.5 ptsLowADR Quality
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.+2.1 ptsMediumArchitecture documentation
Resolve the 18 redundant comment finding(s) in Comment Value — start with getDefaultFormStateTest.ts (4), validator.test.ts (3), REDACTED (2).+0.7 ptsMediumComment Value
Adopt pino (or winston) and log at meaningful points in the services you run.+1.2 ptsMediumObservability
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+1.1 ptsMediumDocumentation (README)
Reconcile the README with reality: packages/docs/versioned_docs/version-5.24.10/usage/validation.md names Ajv 6, but the manifest declares `ajv` ^8.20.0.+1.1 ptsMediumDocumentation accuracy
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+0.5 ptsLowDocumentation Quality
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+0.9 ptsMediumKeyboard semantics

File quality

Per-file score 0–10 — a quality signature. Of 137 files carrying findings, judged against the Production bar: 2% slop · 52% mixed · 46% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
packages/core/src/components/fields/formDataForNewOption.ts5.9MixedCyclomatic Complexity: formDataForNewOption.formDataForNewOption (cyclomatic 36)
packages/utils/src/schema/getClosestMatchingOption.ts6.0MixedExplicit Debt: TodoComment
packages/core/test/StringField.test.tsx6.0MixedExplicit Debt: XxxComment
packages/playground/src/components/DemoFrame.tsx6.3MixedCyclomatic Complexity: DemoFrame.AntdPopupPatcher (cyclomatic 17)
packages/core/src/components/fields/LayoutMultiSchemaField.tsx6.3MixedGod Classes: FunctionTooLong: LayoutMultiSchemaField.LayoutMultiSchemaField
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
packages/utils/src/schema/getDefaultFormState.ts6.5MixedCyclomatic Complexity: getDefaultFormState.foldView (cyclomatic 66)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 42

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

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

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

Could not be resolved — 7

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 74 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 74 dimensions across the health lenses
D1D2D3D5D6D8D10D11D13D14D15D16D17D19D20D22D23D24D26D27D28D29D30D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X16X17X19X21X25X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 671 of 685 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e7b3-405e-77ac-a17d-863c5cf75997.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 0 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and the index lookup answered not published for every exact pin asked about (0 lookup(s)), so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/antd/src/globalUiOptions.ts`, `packages/chakra-ui/src/utils.ts`, `packages/core/src/components/fields/ObjectField.tsx`, `packages/core/src/components/fields/SchemaField.tsx`, `packages/daisyui/src/utils.ts`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/utils/src/schema/graph/parseSchemaGraph.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> start / > echo 'use "pnpm run build" from main directory and then "pnpm start" in the playground package' / use "pnpm run build" from main directory and then "pnpm start" in the playground package" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> start / > echo 'use "pnpm run build" from main directory and then "pnpm start" in the playground package' / use "pnpm run build" from main directory and then "pnpm start" in the playground package" No runtime evidence was gathered.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 170 further occurrence(s) are not listed individually; the score already reflects all 210.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 87 further occurrence(s) are not listed individually; the score already reflects all 127.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic 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 (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run 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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity4.6 / 10Weak✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

81 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was sanitizeFieldTree.walk at 109.

omitExtraData.omitExtraData::omit (cyclomatic 39) · ×2packages/utils/src/schema/omitExtraData.ts:543
CheckboxWidget.CheckboxWidget (cyclomatic 18) · ×2packages/mantine/src/widgets/CheckboxWidget.tsx:22
SelectWidget.SelectWidget (cyclomatic 16) · ×2packages/mantine/src/widgets/SelectWidget.tsx:33
sanitizeFieldTree.walk (cyclomatic 109)packages/core/src/components/sanitizeFieldTree.ts:828
ObjectField.ObjectField (cyclomatic 79)packages/core/src/components/fields/ObjectField.tsx:434

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

What to do

  1. Bring the 6 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with sanitizeFieldTree.walk (cyclomatic 109), ObjectField.ObjectField (cyclomatic 79), fancy-select.FancySelect (cyclomatic 67). — 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 6 together lifts Cyclomatic Complexity from 4.6 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity4.0 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

83 method(s) exceeded the cognitive complexity threshold of 15; the worst was sanitizeFieldTree.walk at 145.

omitExtraData.omitExtraData::omit (cognitive 40) · ×2packages/utils/src/schema/omitExtraData.ts:543
sanitizeFieldTree.walk (cognitive 145)packages/core/src/components/sanitizeFieldTree.ts:828
ObjectField.ObjectField (cognitive 97)packages/core/src/components/fields/ObjectField.tsx:434
getDefaultFormState.objectDefaults (cognitive 76)packages/utils/src/schema/getDefaultFormState.ts:1569
retrieveSchema.buildView (cognitive 73)packages/utils/src/schema/retrieveSchema.ts:715

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with sanitizeFieldTree.walk (cognitive 145). — Refactoring it lifts Cognitive Complexity from 4.0 to about 4.3/10.

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

D3 · God Classes7.9 / 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.

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

51 god class(es) detected.

FunctionTooLong: formModel.createFormModel · ×36packages/core/src/components/formModel.ts:224
FileTooLong: schema/getDefaultFormState.ts · ×14packages/utils/src/schema/getDefaultFormState.ts
TooManyMethods: Graphpackages/utils/src/schema/graph/parseSchemaGraph.ts:273

What to do

  1. Resolve the 36 FunctionTooLong finding(s) in God Classes — start with ArrayField.tsx (4), SelectWidget.tsx (3), SchemaField.tsx (2). — One of this dimension's main actionable groups (36 warning-level).
  2. Resolve the 14 FileTooLong finding(s) in God Classes — start with getDefaultFormState.ts, SchemaField.tsx, formState.ts. — One of this dimension's main actionable groups (14 warning-level).
  3. Resolve the 1 TooManyMethods finding(s) in God Classes — start with parseSchemaGraph.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D5 · Coupling9.0 / 10Stronggated by 2 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.

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

16 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.

Off the main sequence: @rjsf/utils · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).

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

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

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

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

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

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

0 of 9 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage10.0 / 10Stronggated by 13 serious findings✓ Tool-verified

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

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

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

Line coverage 97.2% — 13 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/antd/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/bootstrap3/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/chakra-ui/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/daisyui/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/fluentui-rc/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/mantine/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/mui/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/playground/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/react-bootstrap/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/shadcn/, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.

Low coverage: packages/chakra-ui/src/ChakraFrameProvider.tsx · ×13packages/chakra-ui/src/ChakraFrameProvider.tsx:1

What to do

  1. Resolve the 13 Low coverage finding(s) in Code Coverage — start with ChakraFrameProvider.tsx, FluentUIRCFrameProvider.tsx, DemoFrame.tsx. — One of this dimension's main actionable groups (13 warning-level).

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

D10 · Test Quality9.9 / 10Stronggated by 36 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.

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

3 skipped (1 with a documented reason), 31 zero-assertion, 3 racing the wall clock, no mocking-framework packages referenced (hand-written doubles or no mocking) across 9285 tests.

No assertions: types the errors of rawValidation() as the engine's · ×31packages/validator-ata/test/createPrecompiledValidator.test.ts:18
Races the wall clock: offers the default years for %s · ×3packages/utils/test/getDateElementProps.test.ts:122
Skipped test: %s widget only references elements that exist when inputWrapperOrder leaves the label out · ×2packages/mantine/test/AriaLabelledBy.test.tsx:1122
Mock-dominated test: takes no focus, and so reports no blur, on a click on a selected item of a readonly select · ×5packages/shadcn/test/SelectWidget.test.tsx:2213
Skipped (documented): (unnamed test)packages/utils/test/testUtils/nestedResourceTests.ts:164

What to do

  1. Resolve the 31 No assertions finding(s) in Test Quality — start with IChangeEvent.test.ts (4), jsonSchemaAugmentation.test.ts (3), uiSchemaTypes.test.ts (3). — One of this dimension's main actionable groups (31 warning-level).
  2. Resolve the 3 Races the wall clock finding(s) in Test Quality — start with StringField.test.tsx (2), getDateElementProps.test.ts. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Skipped test finding(s) in Test Quality — start with AriaLabelledBy.test.tsx, RatingWidget.test.tsx. — One of this dimension's main actionable groups (2 warning-level).

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

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.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (30447 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/antd/ (739 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/bootstrap3/ (430 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/chakra-ui/ (682 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/ (6339 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/daisyui/ (1044 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/fluentui-rc/ (553 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/mantine/ (1329 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/mui/ (716 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/playground/ (59 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/react-bootstrap/ (510 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/shadcn/ (678 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 1365 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1365 package(s) this repository's committed lockfile installs for a consumer — its 52 production, optional and peer dependency(ies), across 16 product package.json manifest(s), and everything those install in turn. Its 112 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 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. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under Apache-2.0 / MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 120 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: packages/utils/src/schema/sanitizeDataForNewSchema.ts (29×159=4611); packages/core/src/components/fields/SchemaField.tsx (65×57=3705); packages/core/src/components/fields/ObjectField.tsx (42×79=3318) Repeated repair below the complexity floor: packages/utils/src/types.ts (48 of 93 changes were fixes); .github/size-limit/.size-limit.js (48 of 71 changes were fixes); packages/core/src/components/fields/LayoutMultiSchemaField.tsx (18 of 34 changes were fixes)

Repeated repair: packages/utils/src/types.ts · ×69packages/utils/src/types.ts:2369
Hotspot: packages/utils/src/schema/sanitizeDataForNewSchema.ts · ×51packages/utils/src/schema/sanitizeDataForNewSchema.ts:480

What to do

  1. Resolve the 69 Repeated repair finding(s) in Churn × Complexity Hotspots — start with CheckboxesWidget.tsx (6), RadioWidget.tsx (6), index.tsx (6). — One of this dimension's main actionable groups (69 warning-level).
  2. Resolve the 51 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.tsx (4), SelectWidget.tsx (3), CheckboxWidget.tsx (3). — One of this dimension's main actionable groups (51 warning-level).

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

D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/daisyui/src/widgets/BooleanInput.tsx. Counted over 289 of the 865 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.

D17 · Explicit Debt10.0 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

4 deducted task-comment markers across 83230 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.

TodoComment · ×3packages/validator-ajv8/src/createAjvInstance.ts:14
XxxCommentpackages/core/test/StringField.test.tsx:1520

What to do

  1. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with createAjvInstance.ts, isCustomWidget.ts, getClosestMatchingOption.ts. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 XxxComment finding(s) in Explicit Debt — start with StringField.test.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 2 documentation facets pass in full; short on: F2 example. 135 document(s) read across 19 unit(s).

Documentation: no build, run or usage exampleREADME.md:1

✓ On the Gold path — maintain.

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundpackage.json:19

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

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

D22 · Internal API Consistency7.4 / 10Strong✓ Tool-verified

What it measures: Whether the internal API surface is consistent and coherent.

Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.

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

1 API inconsistencies among 38 exposed members measured against a convention their peers follow.

`SchemaUtilsType.getUiRequiredErrorSchema` types `uiSchema` as `UiSchema<T, S, F> | undefined` where 3 sibling members type it `UiSchema<T, S, F>`packages/utils/src/types.ts:2856

What to do

  1. Resolve the 1 `SchemaUtilsType.getUiRequiredErrorSchema` types `uiSchema` as… finding(s) in Internal API Consistency — start with types.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

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.

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

1 domain type(s) cross context boundaries across 17 contexts; they are measured and withheld (not published, not scored). Contexts: antd, bootstrap3, chakra-ui, core, daisyui, docs, fluentui-rc, mantine, mui, playground, react-bootstrap, shadcn and 5 more.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.5 9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

18 of 3760 judged comments only repeat the code they sit on (0.5 %). 14 comment(s) in another language or script were not judged.

redundant comment · ×18packages/core/src/components/fields/ArrayField.tsx:1107
doc comments repeat the names · ×8packages/antd/src/templates/headingLabelColClassName.ts:27

✓ On the Gold path — maintain.

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

D26 · Project Cohesion7.6 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

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

2 of 17 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×2packages/utils/package.json:1

What to do

  1. Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

10 % of calls cross a namespace and 1 % go through an interface, but 49 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)2.5 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

47 finding(s): 0 critical, 40 high, 7 medium, 0 low. 34 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 19 file(s) — `packages/antd/src/globalUiOptions.ts` (lines 39–42), `packages/chakra-ui/src/utils.ts` (lines 26–29), `packages/core/src/components/fields/ObjectField.tsx` (lines 90–91, line 91), `packages/core/src/components/fields/SchemaField.tsx` (line 391, line 399, line 418, …), `packages/daisyui/src/utils.ts` (lines 61–64), … (+14 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

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 34 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 (34 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

1 of 289 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/mantine/src/templates/icons.tsx. Counted over 289 of the 865 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filepackages/mantine/src/templates/icons.tsx:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.9 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: .size-limit.js↔formState.ts 74%; .size-limit.js↔formDataForNewOption.ts 71%; .size-limit.js↔sanitizeFieldTree.ts 70%

Change coupling: LayoutMultiSchemaField.tsx ↔ MultiSchemaField.tsx · ×4packages/core/src/components/fields/LayoutMultiSchemaField.tsx:1
Change-coupling hub: .size-limit.js → formDataForNewOption.ts, formState.ts, sanitizeFieldTree.ts.github/size-limit/.size-limit.js

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with LayoutMultiSchemaField.tsx (2), BaseInputTemplate.tsx, formDataForNewOption.ts. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with .size-limit.js. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. 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).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels6.8 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — packages/antd/src/templates/TitleField/index.tsx:36
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — packages/playground/src/components/RawValidatorTest.tsx:50

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.7 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/playground/index.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — packages/daisyui/src/widgets/DatePickerTrigger.tsx:192

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety7.0 / 10Strong✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • <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/shadcn/src/components/ui/input.tsx:16
  • <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/shadcn/src/components/ui/textarea.tsx:21

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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.

  • `SchemaUtilsType` declares 23 required operations: `getRootSchema`, `getValidator`, `doesSchemaUtilsDiffer`, `allowsAdditionalProperties`, `canExpand`, `constrainsAlike`, `findFieldInSchema`, `findSelectedOptionInXxxOf`, `getDefaultFormState`, `getDisplayLabel`, `getFilledDefault`, `getClosestMatchingOption`, `getFirstMatchingOption`, `getFromSchema`, `getFromSchema`, `getFromSchema`, `isFilesArray`, `isMultiSelect`, `isSelect`, `omitExtraData`, `retrieveSchema`, `getUiRequiredErrorSchema`, `sanitizeDataForNewSchema`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/utils/src/types.ts:2624

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs8.5 / 10Strong✓ Tool-verified

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

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

  • The guard above `return uiSchema;` also returns `uiSchema`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — packages/core/src/components/fields/fieldWidgetUtils.ts:445
  • `anyJson` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/playground/src/components/Editors.tsx:52
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — packages/daisyui/test/RatingWidget.test.tsx:243, packages/mantine/test/AriaLabelledBy.test.tsx:1122

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)7.8 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • packages/docs/versioned_docs/version-5.24.10/usage/validation.md names Ajv 6, but the manifest declares `ajv` ^8.20.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/docs/versioned_docs/version-5.24.10/usage/validation.md:624

What to do

  • Reconcile the README with reality: packages/docs/versioned_docs/version-5.24.10/usage/validation.md names Ajv 6, but the manifest declares `ajv` ^8.20.0.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging call was found in the 905 JavaScript/TypeScript production file(s) this check read across 18 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.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

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.

R10 · Code Duplication5.3 / 10Adequate✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 213 duplicated blocks under packages/ have copies in at least two of the sibling directories antd, bootstrap3, chakra-ui, core, daisyui, fluentui-rc (+9 more sibling(s) not listed) — 157 of them are reported below, and 56 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 213 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 213 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 213 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/validator-ajv8/src/processRawValidationErrors.ts:1
  • 9 duplicated blocks under packages/mui/src/ have copies in at least two of the sibling directories AddButton, ArrayFieldItemTemplate, ArrayFieldTemplate, CheckboxWidget, CheckboxesWidget, ErrorList (+7 more sibling(s) not listed) — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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/CheckboxesWidget/CheckboxesWidget.tsx:27
  • 6 duplicated blocks under packages/chakra-ui/src/ have copies in at least two of the sibling directories BaseInputTemplate, CheckboxesWidget, NativeSelectWidget, RadioWidget, RangeWidget, TextareaWidget (+1 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/chakra-ui/src/BaseInputTemplate/BaseInputTemplate.tsx:22
  • 6 duplicated blocks under packages/core/src/components/ have copies in at least two of the sibling directories fields, templates, widgets — 2 of them are reported below, and 4 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/core/src/components/templates/index.ts:54
  • 5 duplicated blocks under packages/antd/src/widgets/ have copies in at least two of the sibling directories CheckboxesWidget, DateWidget, PasswordWidget, RadioWidget, TextareaWidget — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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/antd/src/widgets/RadioWidget/index.tsx:23
  • packages/validator-ajv8/src/processRawValidationErrors.ts:1 · packages/validator-ata/src/processRawValidationErrors.ts:1 — these 2 files are line-for-line copies of one another — 124 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/validator-ajv8/src/processRawValidationErrors.ts:1
  • packages/validator-ajv8/src/precompiledValidator.ts:1 · packages/validator-ata/src/precompiledValidator.ts:1 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/validator-ajv8/src/precompiledValidator.ts:1
  • packages/validator-ata/src/validator.ts:168 · packages/validator-cfworker/src/validator.ts:147 — the two spans are one implementation copied and then locally edited — 422 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/validator-ata/src/validator.ts:168
  • packages/mui/src/CheckboxesWidget/CheckboxesWidget.tsx:27 · packages/mui/src/RadioWidget/RadioWidget.tsx:25 — the two spans are one implementation copied and then locally edited — 317 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/CheckboxesWidget/CheckboxesWidget.tsx:27
  • packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19 · packages/react-bootstrap/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19
  • packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx:75 · packages/daisyui/src/widgets/DateWidget/DateWidget.tsx:21 — the two spans are one implementation copied and then locally edited — 285 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/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx:75
  • packages/chakra-ui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12 · packages/react-bootstrap/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12 — 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/chakra-ui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12
  • packages/core/src/components/widgets/SelectWidget.tsx:64 · packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:44 — the two spans are one implementation copied and then locally edited — 320 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/widgets/SelectWidget.tsx:64
  • packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:18 · packages/mui/src/FieldTemplate/FieldTemplate.tsx:40 — 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/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:18
  • packages/chakra-ui/src/FieldTemplate/FieldTemplate.tsx:60 · packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:42 — the two spans are one implementation copied and then locally edited — 226 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/FieldTemplate/FieldTemplate.tsx:60
  • packages/core/src/components/fields/ArrayField.tsx:340 · packages/core/src/components/fields/ArrayField.tsx:398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/core/src/components/fields/ArrayField.tsx:340
  • packages/antd/src/templates/index.ts:21 · packages/mui/src/Templates/Templates.ts:22 · packages/react-bootstrap/src/Templates/Templates.ts:22 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/antd/src/templates/index.ts:21
  • packages/chakra-ui/src/Templates/Templates.ts:22 · packages/fluentui-rc/src/Templates/Templates.ts:22 · packages/mui/src/Templates/Templates.ts:22 · packages/react-bootstrap/src/Templates/Templates.ts:22 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/chakra-ui/src/Templates/Templates.ts:22
  • packages/mantine/src/widgets/PasswordWidget.tsx:29 · packages/mantine/src/widgets/TextareaWidget.tsx:28 — 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/mantine/src/widgets/PasswordWidget.tsx:29
  • packages/bootstrap3/src/OptionalDataControlsTemplate.tsx:15 · packages/core/src/components/templates/OptionalDataControlsTemplate.tsx:14 — 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/bootstrap3/src/OptionalDataControlsTemplate.tsx:15
  • packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22 · packages/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18 · packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50 — 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/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22
  • packages/mui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 · packages/mui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:24 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/mui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26
  • packages/validator-ajv8/src/processRawValidationErrors.ts:180 · packages/validator-ata/src/processRawValidationErrors.ts:170 · packages/validator-cfworker/src/processRawValidationErrors.ts:178 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/validator-ajv8/src/processRawValidationErrors.ts:180
  • packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:78 · packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:77 — 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/bootstrap3/src/WrapIfAdditionalTemplate.tsx:78
  • packages/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18 · packages/mui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:47 — 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/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18
  • packages/chakra-ui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13 · packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/chakra-ui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13
  • packages/daisyui/src/templates/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 · packages/mantine/src/templates/ArrayFieldTemplate.tsx:16 — 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/daisyui/src/templates/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26
  • packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50 · packages/react-bootstrap/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:16 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50
  • packages/react-bootstrap/src/CheckboxWidget/CheckboxWidget.tsx:13 · packages/shadcn/src/CheckboxWidget/CheckboxWidget.tsx:23 — 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/react-bootstrap/src/CheckboxWidget/CheckboxWidget.tsx:13
  • packages/react-bootstrap/src/IconButton/IconButton.tsx:12 · packages/shadcn/src/IconButton/IconButton.tsx:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react-bootstrap/src/IconButton/IconButton.tsx:12
  • packages/validator-ajv8/src/validator.ts:214 · packages/validator-ata/src/validator.ts:194 — 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/validator-ajv8/src/validator.ts:214
  • packages/antd/src/templates/WrapIfAdditionalTemplate/index.tsx:28 · packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22 · packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:24 · packages/shadcn/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:37 — the 4 copies are spread across 4 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/antd/src/templates/WrapIfAdditionalTemplate/index.tsx:28
  • packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:68 · packages/shadcn/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:93 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:68
  • packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:19 · packages/shadcn/src/SelectWidget/SelectWidget.tsx:61 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:19
  • packages/react-bootstrap/src/BaseInputTemplate/BaseInputTemplate.tsx:54 · packages/shadcn/src/BaseInputTemplate/BaseInputTemplate.tsx:61 — 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/react-bootstrap/src/BaseInputTemplate/BaseInputTemplate.tsx:54
  • packages/react-bootstrap/src/TextareaWidget/TextareaWidget.tsx:6 · packages/shadcn/src/TextareaWidget/TextareaWidget.tsx:12 — 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/react-bootstrap/src/TextareaWidget/TextareaWidget.tsx:6
  • packages/antd/src/widgets/index.ts:17 · packages/mantine/src/widgets/index.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/antd/src/widgets/index.ts:17
  • packages/bootstrap3/src/CyclicSchemaExpandTemplate.tsx:9 · packages/core/src/components/templates/CyclicSchemaExpandTemplate.tsx:8 — 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/bootstrap3/src/CyclicSchemaExpandTemplate.tsx:9
  • packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:59 · packages/mui/src/FieldTemplate/FieldTemplate.tsx:85 · packages/react-bootstrap/src/FieldTemplate/FieldTemplate.tsx:51 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:59
  • packages/mantine/src/widgets/ColorWidget.tsx:38 · packages/mantine/src/widgets/DateTime/TimeWidget.tsx:47 · packages/mantine/src/widgets/PasswordWidget.tsx:29 · packages/mantine/src/widgets/TextareaWidget.tsx:28 — the 4 copies are spread across 4 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/mantine/src/widgets/ColorWidget.tsx:38

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries9.4 / 10Exemplary✓ Tool-verified

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

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

  • packages/playground/src/app.tsx:14 imports ajv/dist/2019.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/playground/src/app.tsx:14
  • packages/playground/src/app.tsx:15 imports ajv/dist/2020.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/playground/src/app.tsx:15
  • packages/utils/src/schema/shallowAllOfMerge.ts:2 imports @x0k/json-schema-merge/lib/array, 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/utils/src/schema/shallowAllOfMerge.ts:2
  • packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:5 imports ajv/dist/runtime/uri.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:5
  • packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:6 imports ajv/dist/standalone/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:6
  • testing/testSetup.ts:6 reaches into another package with a relative path (../packages/utils/src/constants.ts) — import the package by name instead. — testing/testSetup.ts:6
  • testing/testSetup.ts:7 reaches into another package with a relative path (../packages/utils/src/logOnce.ts) — import the package by name instead. — testing/testSetup.ts:7

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • walk has cyclomatic complexity 81 and cognitive complexity 139; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/core/src/components/sanitizeFieldTree.ts:828
  • foldView has cyclomatic complexity 68 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/utils/src/schema/getDefaultFormState.ts:967
  • useSchemaFieldPlan has cyclomatic complexity 60 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/SchemaField.tsx:1265
  • objectDefaults has cyclomatic complexity 54 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/getDefaultFormState.ts:1569
  • (anonymous) has cyclomatic complexity 53 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/sanitizeDataForNewSchema.ts:842
  • walk has cyclomatic complexity 52 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/getUiRequiredErrorSchema.ts:244
  • (anonymous) has cyclomatic complexity 47 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/utils/src/schema/sanitizeDataForNewSchema.ts:526
  • getFieldComponent has cyclomatic complexity 45 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/SchemaField.tsx:682
  • sanitizeWithFills has cyclomatic complexity 44 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/sanitizeDataForNewSchema.ts:480
  • judge has cyclomatic complexity 44 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/sanitizeFieldTree.ts:405
  • omit has cyclomatic complexity 42 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/omitExtraData.ts:543
  • SchemaFieldRender has cyclomatic complexity 39 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/core/src/components/fields/SchemaField.tsx:1573
  • buildView has cyclomatic complexity 35 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/retrieveSchema.ts:715
  • AnyOfField has cyclomatic complexity 35 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/MultiSchemaField.tsx:60
  • resolveFieldPresentation has cyclomatic complexity 34 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/resolveFieldPresentation.ts:165
  • shareUnchanged has cyclomatic complexity 32 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/utils/src/replaceEqualDeep.ts:55
  • arrayDefaults has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/getDefaultFormState.ts:1971
  • renderOption has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/utils/src/getRenderedOptionSchema.ts:289
  • getInputProps has cyclomatic complexity 30 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/getInputProps.ts:56
  • BaseInputTemplate has cyclomatic complexity 29 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/mantine/src/templates/BaseInputTemplate.tsx:34
  • ArrayFieldItemInner has cyclomatic complexity 28 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/core/src/components/fields/ArrayField.tsx:656
  • (anonymous) has cyclomatic complexity 28 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/shadcn/src/components/ui/fancy-select.tsx:350
  • formDataMatching has cyclomatic complexity 26 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/getDefaultFormState.ts:2441
  • meetKeyword has cyclomatic complexity 26 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/getRenderedOptionSchema.ts:146
  • BaseInputTemplate has cyclomatic complexity 26 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/antd/src/templates/BaseInputTemplate/index.tsx:28
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:250
  • check has cyclomatic complexity 24 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/test/schema/graph/miniValidator.ts:44
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/sanitizeFieldTree.ts:1120
  • resolveUiSchema has cyclomatic complexity 23 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/resolveUiSchema.ts:44
  • warnOfUnshownOptionLabels has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/SchemaField.tsx:229
  • castToNewType has cyclomatic complexity 23 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/FallbackField.tsx:425
  • (anonymous) has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/formModel.ts:653
  • derive has cyclomatic complexity 22 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 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/utils/src/schema/graph/validationTargets.ts:724
  • FieldTemplate has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/antd/src/templates/FieldTemplate/index.tsx:26
  • applyChangeToData has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/formState.ts:1768
  • settleFormData has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/formState.ts:1296
  • getGroupAttributes has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/getGroupAttributes.ts:42
  • formDataForNewOption has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/components/fields/formDataForNewOption.ts:353
  • compileSchemaValidatorsCode has cyclomatic complexity 20 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:567
  • foldOption has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/schema/getDefaultFormState.ts:1342
R3 · Large Files8.3 / 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/utils/src/types.ts has 2730 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/utils/src/types.ts:1
  • packages/utils/src/schema/getDefaultFormState.ts has 2513 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/utils/src/schema/getDefaultFormState.ts:1
  • packages/core/src/components/formState.ts has 2087 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/formState.ts:1
  • packages/core/src/components/fields/SchemaField.tsx has 1926 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/fields/SchemaField.tsx:1
  • packages/utils/src/schema/graph/validationTargets.ts has 1849 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/utils/src/schema/graph/validationTargets.ts:1
  • packages/snapshot-tests/src/formTests.tsx has 1542 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/snapshot-tests/src/formTests.tsx:1
  • packages/core/src/components/fields/ArrayField.tsx has 1473 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/fields/ArrayField.tsx:1
  • packages/core/src/components/sanitizeFieldTree.ts has 1357 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/sanitizeFieldTree.ts:1
  • REDACTED has 1328 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/utils/src/schema/retrieveSchema.ts has 1175 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/utils/src/schema/retrieveSchema.ts:1
  • packages/utils/src/schema/graph/mergePlan.ts has 1121 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/utils/src/schema/graph/mergePlan.ts:1
  • packages/core/src/components/formModel.ts has 1118 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/formModel.ts:1
  • packages/mantine/src/utils.tsx has 1058 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/mantine/src/utils.tsx:1
  • packages/core/src/components/fields/ObjectField.tsx has 1048 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/components/fields/ObjectField.tsx:1
  • packages/utils/src/schema/sanitizeDataForNewSchema.ts has 973 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/utils/src/schema/sanitizeDataForNewSchema.ts:1
  • packages/utils/src/schema/graph/parseSchemaGraph.ts has 782 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/utils/src/schema/graph/parseSchemaGraph.ts:1
  • packages/daisyui/src/widgets/datePickerHooks.ts has 723 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/daisyui/src/widgets/datePickerHooks.ts:1
  • packages/core/src/components/fields/FallbackField.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/core/src/components/fields/FallbackField.tsx:1
  • REDACTED 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. — REDACTED:1
  • packages/utils/src/schema/getClosestMatchingOption.ts has 657 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/utils/src/schema/getClosestMatchingOption.ts:1
  • packages/core/src/components/uiState.ts has 650 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/uiState.ts:1
  • packages/core/src/components/fields/fieldWidgetUtils.ts has 639 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/fields/fieldWidgetUtils.ts:1
  • packages/core/src/components/Form.tsx has 638 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/Form.tsx:1
  • packages/utils/src/schema/omitExtraData.ts has 638 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/utils/src/schema/omitExtraData.ts:1
  • packages/snapshot-tests/src/arrayTests.tsx has 579 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/snapshot-tests/src/arrayTests.tsx:1
  • packages/core/src/components/fields/formDataForNewOption.ts has 543 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/fields/formDataForNewOption.ts:1
  • packages/snapshot-tests/src/gridTests.tsx has 530 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/snapshot-tests/src/gridTests.tsx:1
  • packages/utils/src/schema/getUiRequiredErrorSchema.ts has 528 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/utils/src/schema/getUiRequiredErrorSchema.ts:1
  • packages/core/src/components/fields/useSchemaFieldPresentation.ts has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/components/fields/useSchemaFieldPresentation.ts:1
  • packages/snapshot-tests/src/objectTests.tsx has 496 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/snapshot-tests/src/objectTests.tsx:1
  • packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx has 475 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/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:1
  • packages/utils/src/createSchemaUtils.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/utils/src/createSchemaUtils.ts:1
  • packages/utils/src/getWidget.tsx has 424 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/utils/src/getWidget.tsx:1
  • packages/shadcn/src/components/ui/fancy-select.tsx has 407 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/shadcn/src/components/ui/fancy-select.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage9.9 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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. (×5) — packages/playground/src/app.tsx:1, tsdown.base.mts:1, packages/playground/src/layout/Footer.tsx:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code9.7 / 10Exemplary✓ 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 100 application, 40 tooling and 599 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 (100 application, 40 tooling, 599 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 — scripts/get-version-tag.cjs
  • Nothing imports this binding — it is safe to review for removal. (×6) — packages/chakra-ui/src/components/ui/select.tsx:84, packages/chakra-ui/src/components/ui/select.tsx:100, packages/chakra-ui/src/components/ui/select.tsx:186, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1

What to do

  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_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.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document1.8 / 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.

  • `normalizeFormDataForValidation` is exported and takes `data: unknown` from its caller, and it calls itself at line 43 (`normalizeFormDataForValidation`) with a piece of `data` (and at line 48) — and nowhere in `normalizeFormDataForValidation` 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 `normalizeFormDataForValidation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/validator-cfworker/src/validator.ts:43
  • `copyForValidation` is exported and takes `data: unknown` from its caller, and it calls itself at line 35 (`copyForValidation`) with a piece of `data` (and at line 39) — and nowhere in `copyForValidation` 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 `copyForValidation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/validator-ajv8/src/dataForValidation.ts:35
  • `getChangedFields` is exported, takes a document from its caller (line 63) and hands it to `getChangedDescendants`, which calls itself at line 28 (`getChangedDescendants`) with a piece of `a` — and nowhere in `getChangedDescendants` 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 `getChangedDescendants` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/getChangedFields.ts:28
  • `sortedJSONStringify` is exported and takes `object: unknown` from its caller, and it calls itself at line 36 (`sortedJSONStringify`) with a piece of `object` (and at line 46) — and nowhere in `sortedJSONStringify` 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 `sortedJSONStringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/hashObject.ts:36
  • `replaceEqualDeep` is exported, takes a document from its caller (line 140) and hands it to `shareUnchanged`, which calls itself at line 67 (`shareUnchanged`) with a piece of `prev` (and at line 82, line 98) — and nowhere in `shareUnchanged` 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 `shareUnchanged` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/replaceEqualDeep.ts:67
  • `toInputValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 14 (`toInputValue`) with a piece of `value` — and nowhere in `toInputValue` 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 `toInputValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/toInputValue.ts:14
  • `getDefaultFormState` is exported, takes a document from its caller (line 2559) and hands it to `withNullFills`, which calls itself at line 462 (`withNullFills`) with a piece of `formData` — and nowhere in `withNullFills` 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 `withNullFills` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/schema/getDefaultFormState.ts:462
  • `isValueEmpty` is exported and takes `value: unknown` from its caller, and it calls itself at line 106 (`isValueEmpty`) with a piece of `value` — and nowhere in `isValueEmpty` 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 `isValueEmpty` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/schema/omitExtraData.ts:106
  • `retrieveSchema` is exported, takes a document from its caller (line 97) and hands it to `buildView`, which calls itself at line 813 (`buildView`) with a piece of `data` — and nowhere in `buildView` 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 `buildView` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/utils/src/schema/retrieveSchema.ts:813
  • `freezeFormData` is exported and takes `data: unknown` from its caller, and it calls itself at line 1656 (`freezeFormData`) with a piece of `data` — and nowhere in `freezeFormData` 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 `freezeFormData` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/core/src/components/formState.ts:1656

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.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — packages/utils/src/getDecimalSeparator.ts:15, packages/utils/src/toDisplayString.ts:52, packages/utils/src/useFileWidgetProps.ts:95, …
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/daisyui/src/theme/storedTheme.ts:32

What to do

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

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

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

X5 · Nullable reference types8.4 / 10Strong✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 4/5 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 — 6 assertion(s) across the 79291 source line(s) of the 840 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/core/src/components/fields/layoutMultiSchemaFieldSelector.ts (1), packages/playground/src/index.tsx (1), packages/utils/src/createErrorHandler.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health66.7Adequate — gated by D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96.4ExemplarySolid.
Maturity64.4Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness67.9Adequate — gated by P2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security74.2Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility65.8AdequateAcceptable, with room to improve.
Performance100.0ExemplaryStrongest area.
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 — 26 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 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 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
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> start / > echo 'use "pnpm run build" from main directory and then "pnpm start" in the playground package' / use "pnpm run build" from main directory and then "pnpm start" in the playground package" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D12 Dependency Hygiene — Not scored — 0 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and the index lookup answered not published for every exact pin asked about (0 lookup(s)), so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • 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 — D21 withholds its case and prefix conventions rows: 7 candidate(s) found and not reported.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 763 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.

Critical — 42 finding(s)
D29 · Static Analysis (SAST) · 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
  • REDACTED
  • + 9 more in this group — see findings.md.
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control packages/antd/src/templates/TitleField/index.tsx:36 — 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.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label packages/playground/src/components/RawValidatorTest.tsx:50 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 559 finding(s)
D15 · Churn × Complexity Hotspots · Repeated repair · ×69
  • Repeated repair: packages/utils/src/types.ts packages/utils/src/types.ts:2369 — packages/utils/src/types.ts changed 93 times in last 90 days and 48 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is (anonymous) at line 2369), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carries over (#5837)”; “fix 5817, 5818: read the default the fill gives a field when the schema changes (#5827)”; “fix 5744: require an array rendered as one widget only where minItems or ui:required asks (#5822)”; “fix 5729: require a ui:required property by the type the fallback UI's selector is on (#5785)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/types.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: .github/size-limit/.size-limit.js .github/size-limit/.size-limit.js:95 — .github/size-limit/.size-limit.js changed 71 times in last 90 days and 48 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is (anonymous) at line 95), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carries over (#5837)”; “fix 5817, 5818: read the default the fill gives a field when the schema changes (#5827)”; “fix 5771: score options against one copy of a part shared by many paths (#5811)”; “fix 5658: name a field below an option entry after it, and build each warning label once (#5823)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- .github/size-limit/.size-limit.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core/src/components/fields/LayoutMultiSchemaField.tsx packages/core/src/components/fields/LayoutMultiSchemaField.tsx:60 — packages/core/src/components/fields/LayoutMultiSchemaField.tsx changed 34 times in last 90 days and 18 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is LayoutMultiSchemaField.LayoutMultiSchemaField at line 60), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carries over (#5837)”; “fix 5817, 5818: read the default the fill gives a field when the schema changes (#5827)”; “fix 5812: let the tree diff judge the keys an anyOf/oneOf switch discards (#5814)”; “fix 5747: keep a LayoutGridField cell's option through an edit, and leave an option's properties to the options beside the grid (#5783)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/LayoutMultiSchemaField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/utils.tsx packages/mantine/src/utils.tsx:1027 — packages/mantine/src/utils.tsx changed 29 times in last 90 days and 15 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is utils.useGroupAriaProps at line 1027), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5503: render @rjsf/mantine's date parts through DateElement (#5767)”; “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “chore: bump minor and patch dependencies, and fix what they broke (#5749)”; “fix: stop ui:options replacing what the form passes to mantine and shadcn fields (#5737)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/utils.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/utils/src/createSchemaUtils.ts packages/utils/src/createSchemaUtils.ts:105 — packages/utils/src/createSchemaUtils.ts changed 24 times in last 90 days and 14 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is SchemaUtils.doesSchemaUtilsDiffer at line 105), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carries over (#5837)”; “fix 5817, 5818: read the default the fill gives a field when the schema changes (#5827)”; “fix 5777: remove a property sanitize clears, and sanitize array items position by position (#5790)”; “fix(utils,core)!: keep data equal to its const, read untyped old arrays against the new schema, and stop sanitize writing placeholders (#5757, #5768, #5770) (#5773)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/createSchemaUtils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core/src/components/fields/fieldWidgetUtils.ts packages/core/src/components/fields/fieldWidgetUtils.ts:73 — packages/core/src/components/fields/fieldWidgetUtils.ts changed 19 times in last 90 days and 14 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is fieldWidgetUtils.getArrayFieldMode at line 73), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5744: require an array rendered as one widget only where minItems or ui:required asks (#5822)”; “fix 5723: name and describe an object's or an array's group, and the fallback UI's type selector beside one (#5795)”; “fix 5591: plan a field by the widget it renders, and keep a widget from drawing what its field draws (#5765)”; “fix 5581: lay a fallback UI boolean out the same however its widget is named (#5734)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/fieldWidgetUtils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/daisyui/src/templates/FieldTemplate/FieldTemplate.tsx packages/daisyui/src/templates/FieldTemplate/FieldTemplate.tsx:84 — packages/daisyui/src/templates/FieldTemplate/FieldTemplate.tsx changed 21 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is FieldTemplate.FieldTemplate at line 84), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix 3882: render a checkbox for a string with a const (#5753)”; “fix 5651: read a layout grid column's span as twelfths of a row in every theme (#5707)”; “fix 4630: say on its row that an extra key the object forbids is not allowed (#5640)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/daisyui/src/templates/FieldTemplate/FieldTemplate.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/shadcn/src/SelectWidget/SelectWidget.tsx packages/shadcn/src/SelectWidget/SelectWidget.tsx:61 — packages/shadcn/src/SelectWidget/SelectWidget.tsx changed 19 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is SelectWidget.SelectWidget at line 61), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5792, 5802: name the select's list of options in daisyui and shadcn, and drop shadcn's dangling cmdk label (#5807)”; “fix 5478, 5492: give the shadcn multiple select's combobox input its field id and real ARIA state (#5764)”; “fix 5392 (item 4): give each shadcn select option its own cmdk identity (#5741)”; “fix 5711, 5586: name an untitled select or radio group (#5713)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/shadcn/src/SelectWidget/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core/src/components/fields/useSchemaFieldPresentation.ts packages/core/src/components/fields/useSchemaFieldPresentation.ts:302 — packages/core/src/components/fields/useSchemaFieldPresentation.ts changed 14 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is useSchemaFieldPresentation.useSchemaFieldPresentation at line 302), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5744: require an array rendered as one widget only where minItems or ui:required asks (#5822)”; “fix 5723: name and describe an object's or an array's group, and the fallback UI's type selector beside one (#5795)”; “fix 5720: list a field's description and help in aria-describedby in the order its theme draws them (#5794)”; “fix 5516: key antd colSpan by what SchemaField renders a property as (#5791)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/useSchemaFieldPresentation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/FileWidget.tsx packages/mantine/src/widgets/FileWidget.tsx:13 — packages/mantine/src/widgets/FileWidget.tsx changed 15 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is FileWidget.FileWidget at line 13), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix: stop ui:options replacing what the form passes to mantine and shadcn fields (#5737)”; “fix 5610: declare the per-field options RJSF's widgets read on ui:options (#5726)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/FileWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/utils/src/getWidget.tsx packages/utils/src/getWidget.tsx:131 — packages/utils/src/getWidget.tsx changed 17 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is getWidget.findWidgetType at line 131), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix 3882: render a checkbox for a string with a const (#5753)”; “fix 5446: resolve a type list's field type from its widget for every reader (#5728)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “Fix 5331: resolve a null-first type list to its first non-null type (#5428)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/getWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core/src/components/fields/BooleanField.tsx packages/core/src/components/fields/BooleanField.tsx:17 — packages/core/src/components/fields/BooleanField.tsx changed 16 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is BooleanField.BooleanField at line 17), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5591: plan a field by the widget it renders, and keep a widget from drawing what its field draws (#5765)”; “fix 5398: warn from SchemaField, for every type, when option labels are hidden (#5727)”; “fix 5365: read an empty or undefined anyOf/oneOf as no option list (#5675)”; “fix 4298: ui:enumOrder orders constant anyOf/oneOf options (#5636)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/BooleanField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/RangeWidget.tsx packages/mantine/src/widgets/RangeWidget.tsx:148 — packages/mantine/src/widgets/RangeWidget.tsx changed 16 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is RangeWidget.RangeWidget at line 148), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “chore: bump minor and patch dependencies, and fix what they broke (#5749)”; “fix 5367: mantine's wrapper props, sizes and unnamed inputs (#5716)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/RangeWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/fluentui-rc/src/SelectWidget/SelectWidget.tsx packages/fluentui-rc/src/SelectWidget/SelectWidget.tsx:42 — packages/fluentui-rc/src/SelectWidget/SelectWidget.tsx changed 15 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is SelectWidget.SelectWidget at line 42), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5711, 5586: name an untitled select or radio group (#5713)”; “fix 5651: read a layout grid column's span as twelfths of a row in every theme (#5707)”; “fix(fluentui-rc)!: put the plan on the control a user focuses, name every group and control by its label, and draw labels, headings and errors as core does (#5490 phase 3) (#5547)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/fluentui-rc/src/SelectWidget/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/CheckboxesWidget.tsx packages/mantine/src/widgets/CheckboxesWidget.tsx:29 — packages/mantine/src/widgets/CheckboxesWidget.tsx changed 14 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is CheckboxesWidget.CheckboxesWidget at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5367: mantine's wrapper props, sizes and unnamed inputs (#5716)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/CheckboxesWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/RadioWidget.tsx packages/mantine/src/widgets/RadioWidget.tsx:29 — packages/mantine/src/widgets/RadioWidget.tsx changed 14 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is RadioWidget.RadioWidget at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5367: mantine's wrapper props, sizes and unnamed inputs (#5716)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/RadioWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx:91 — packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx changed 17 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is BaseInputTemplate.BaseInputTemplate at line 91), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5600: report chakra's range value on focus, keep the form's props over ui:options.mui in mui, draw no clear button on a range, and draw mui descriptions as plain blocks (#5752)”; “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix(utils,core)!: build every id through one module, so ids can't collide or split an id list (#5626)”; “fix(mui)!: put the plan on the control a user focuses, and draw labels, headings and errors as core does (#5490 phase 3) (#5549)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx:75 — packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is DateTimeWidget.DateTimeWidget at line 75), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5395: read a daisyui date picker's stored value by the field's format (#5760)”; “fix 5667: line up array item buttons and additional property keys by grid rows (#5673)”; “fix 5396: give the daisyui date pickers one popup shell and one positioner (#5633)”; “fix(utils,core)!: build every id through one module, so ids can't collide or split an id list (#5626)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/ColorWidget.tsx packages/mantine/src/widgets/ColorWidget.tsx:23 — packages/mantine/src/widgets/ColorWidget.tsx changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ColorWidget.ColorWidget at line 23), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5610: declare the per-field options RJSF's widgets read on ui:options (#5726)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/ColorWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/DateTime/DateTimeInput.tsx packages/mantine/src/widgets/DateTime/DateTimeInput.tsx:61 — packages/mantine/src/widgets/DateTime/DateTimeInput.tsx changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is DateTimeInput.DateTimeInput at line 61), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”; “fix(core)!: take the template label's marker and `for` from the plan, put the title id on the title's text, and tag the props the plan replaces @deprecated (#5490 phase 3) (#5543)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/DateTime/DateTimeInput.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/chakra-ui/src/SelectWidget/SelectWidget.tsx packages/chakra-ui/src/SelectWidget/SelectWidget.tsx:28 — packages/chakra-ui/src/SelectWidget/SelectWidget.tsx changed 14 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is SelectWidget.SelectWidget at line 28), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5711, 5586: name an untitled select or radio group (#5713)”; “fix(chakra-ui)!: name every control by its label, put the field's id and plan on the element a user focuses, and draw headings, errors and the optional data control as core's templates do (#5490 phase 3) (#5545)”; “fix(core)!: take the template label's marker and `for` from the plan, put the title id on the title's text, and tag the props the plan replaces @deprecated (#5490 phase 3) (#5543)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/chakra-ui/src/SelectWidget/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core/src/components/uiState.ts packages/core/src/components/uiState.ts:83 — packages/core/src/components/uiState.ts changed 11 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is uiState.shownOption at line 83), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5744: require an array rendered as one widget only where minItems or ui:required asks (#5822)”; “fix 5812: let the tree diff judge the keys an anyOf/oneOf switch discards (#5814)”; “fix 5784: keep the type picked in the fallback UI on a cleared array item (#5804)”; “fix 5729: require a ui:required property by the type the fallback UI's selector is on (#5785)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/uiState.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/DateTime/AltDateWidget.tsx packages/mantine/src/widgets/DateTime/AltDateWidget.tsx:72 — packages/mantine/src/widgets/DateTime/AltDateWidget.tsx changed 11 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is AltDateWidget.AltDateWidget at line 72), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5503: render @rjsf/mantine's date parts through DateElement (#5767)”; “fix 5367: mantine's wrapper props, sizes and unnamed inputs (#5716)”; “Fix 5378: return buttonsDisabled from useAltDateWidgetProps, give an unset date part as undefined from getDateElementProps and DateElement, and pin the alt-date buttons in every theme (#5604)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/DateTime/AltDateWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/TextareaWidget.tsx packages/mantine/src/widgets/TextareaWidget.tsx:13 — packages/mantine/src/widgets/TextareaWidget.tsx changed 11 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TextareaWidget.TextareaWidget at line 13), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”; “fix(core)!: take the template label's marker and `for` from the plan, put the title id on the title's text, and tag the props the plan replaces @deprecated (#5490 phase 3) (#5543)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/TextareaWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/mantine/src/widgets/DateTime/TimeWidget.tsx packages/mantine/src/widgets/DateTime/TimeWidget.tsx:26 — packages/mantine/src/widgets/DateTime/TimeWidget.tsx changed 9 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is TimeWidget.TimeWidget at line 26), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix 5573: give a required field one cue, on an anyOf/oneOf field and a checkboxes group (#5743)”; “fix 5607: read only the ui:globalOptions a form declares, let themes and users extend them, and hand every field's widget the globals (#5611)”; “fix(mantine)!: show the errors it hid, put the plan on the control a user focuses, and draw labels, descriptions, headings and help as core does (#5490 phase 3) (#5548)”; “fix(core)!: take the template label's marker and `for` from the plan, put the title id on the title's text, and tag the props the plan replaces @deprecated (#5490 phase 3) (#5543)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/DateTime/TimeWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 44 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×51
  • Hotspot: packages/utils/src/schema/sanitizeDataForNewSchema.ts packages/utils/src/schema/sanitizeDataForNewSchema.ts:480 — packages/utils/src/schema/sanitizeDataForNewSchema.ts changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 159 in sanitizeDataForNewSchema.sanitizeWithFills at line 480. 17 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/sanitizeDataForNewSchema.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/SchemaField.tsx packages/core/src/components/fields/SchemaField.tsx:1573 — packages/core/src/components/fields/SchemaField.tsx changed 65 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in SchemaField.SchemaFieldRender at line 1573. 42 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/SchemaField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/ObjectField.tsx packages/core/src/components/fields/ObjectField.tsx:434 — packages/core/src/components/fields/ObjectField.tsx changed 42 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in ObjectField.ObjectField at line 434. 22 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/ObjectField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/schema/getDefaultFormState.ts packages/utils/src/schema/getDefaultFormState.ts:967 — packages/utils/src/schema/getDefaultFormState.ts changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in getDefaultFormState.foldView at line 967. 21 of those changes were fix/bug commits, and the other 24 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/getDefaultFormState.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/schema/omitExtraData.ts packages/utils/src/schema/omitExtraData.ts:139 — packages/utils/src/schema/omitExtraData.ts changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 95 in omitExtraData.omitExtraData at line 139. 10 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/omitExtraData.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/schema/retrieveSchema.ts packages/utils/src/schema/retrieveSchema.ts:715 — packages/utils/src/schema/retrieveSchema.ts changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in retrieveSchema.buildView at line 715. 18 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/retrieveSchema.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/MultiSchemaField.tsx packages/core/src/components/fields/MultiSchemaField.tsx:60 — packages/core/src/components/fields/MultiSchemaField.tsx changed 46 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in MultiSchemaField.AnyOfField at line 60. 27 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/MultiSchemaField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/sanitizeFieldTree.ts packages/core/src/components/sanitizeFieldTree.ts:828 — packages/core/src/components/sanitizeFieldTree.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in sanitizeFieldTree.walk at line 828. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/sanitizeFieldTree.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/ArrayField.tsx packages/core/src/components/fields/ArrayField.tsx:656 — packages/core/src/components/fields/ArrayField.tsx changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in ArrayField.ArrayFieldItemInner at line 656. 15 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/ArrayField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/schema/getUiRequiredErrorSchema.ts packages/utils/src/schema/getUiRequiredErrorSchema.ts:244 — packages/utils/src/schema/getUiRequiredErrorSchema.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in getUiRequiredErrorSchema.walk at line 244. 15 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/getUiRequiredErrorSchema.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:134 — packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in SelectWidget.SelectWidget at line 134. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/shadcn/src/components/ui/fancy-select.tsx packages/shadcn/src/components/ui/fancy-select.tsx:177 — packages/shadcn/src/components/ui/fancy-select.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in fancy-select.FancySelect at line 177. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/shadcn/src/components/ui/fancy-select.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/formModel.ts packages/core/src/components/formModel.ts:597 — packages/core/src/components/formModel.ts changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in formModel.createFormModel.change at line 597. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/formModel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:906 — REDACTED changed 37 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in LayoutGridField.LayoutGridFieldComponent at line 906. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/FallbackField.tsx packages/core/src/components/fields/FallbackField.tsx:425 — packages/core/src/components/fields/FallbackField.tsx changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in FallbackField.castToNewType at line 425. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/FallbackField.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/fields/formDataForNewOption.ts packages/core/src/components/fields/formDataForNewOption.ts:353 — packages/core/src/components/fields/formDataForNewOption.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in formDataForNewOption.formDataForNewOption at line 353. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/fields/formDataForNewOption.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/shadcn/src/components/ui/fancy-multi-select.tsx packages/shadcn/src/components/ui/fancy-multi-select.tsx:86 — packages/shadcn/src/components/ui/fancy-multi-select.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in fancy-multi-select.FancyMultiSelect at line 86. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/shadcn/src/components/ui/fancy-multi-select.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/formState.ts packages/core/src/components/formState.ts:1768 — packages/core/src/components/formState.ts changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in formState.applyChangeToData at line 1768. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/formState.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/mantine/src/templates/BaseInputTemplate.tsx packages/mantine/src/templates/BaseInputTemplate.tsx:34 — packages/mantine/src/templates/BaseInputTemplate.tsx changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in BaseInputTemplate.BaseInputTemplate at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/templates/BaseInputTemplate.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/getInputProps.ts packages/utils/src/getInputProps.ts:56 — packages/utils/src/getInputProps.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in getInputProps.getInputProps at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/getInputProps.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core/src/components/widgets/RatingWidget.tsx packages/core/src/components/widgets/RatingWidget.tsx:36 — packages/core/src/components/widgets/RatingWidget.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in RatingWidget.RatingWidget at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/core/src/components/widgets/RatingWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/utils/src/schema/graph/validationTargets.ts packages/utils/src/schema/graph/validationTargets.ts:724 — packages/utils/src/schema/graph/validationTargets.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in validationTargets.derive at line 724. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/utils/src/schema/graph/validationTargets.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/mui/src/SelectWidget/SelectWidget.tsx packages/mui/src/SelectWidget/SelectWidget.tsx:100 — packages/mui/src/SelectWidget/SelectWidget.tsx changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SelectWidget.SelectWidget at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mui/src/SelectWidget/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/mantine/src/widgets/SelectWidget.tsx packages/mantine/src/widgets/SelectWidget.tsx:33 — packages/mantine/src/widgets/SelectWidget.tsx changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SelectWidget.SelectWidget at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/mantine/src/widgets/SelectWidget.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/antd/src/widgets/SelectWidget/index.tsx packages/antd/src/widgets/SelectWidget/index.tsx:32 — packages/antd/src/widgets/SelectWidget/index.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in index.SelectWidget at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 18:17:21 +01:00' --until='2026-11-13 18:17:21 +01:00' --full-history --no-merges -- packages/antd/src/widgets/SelectWidget/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 26 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×36
  • FunctionTooLong: formModel.createFormModel packages/core/src/components/formModel.ts:224 — FunctionTooLong — createFormModel runs 510 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 410 over it, 5.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ObjectField.ObjectField packages/core/src/components/fields/ObjectField.tsx:434 — FunctionTooLong — ObjectField runs 383 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 283 over it, 3.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: sanitizeDataForNewSchema.sanitizeWithFills packages/utils/src/schema/sanitizeDataForNewSchema.ts:480 — FunctionTooLong — sanitizeWithFills runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: sanitizeFieldTree.walk packages/core/src/components/sanitizeFieldTree.ts:828 — FunctionTooLong — walk runs 293 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 193 over it, 2.93× 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: SchemaField.SchemaFieldRender packages/core/src/components/fields/SchemaField.tsx:1573 — FunctionTooLong — SchemaFieldRender runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: MultiSchemaField.AnyOfField packages/core/src/components/fields/MultiSchemaField.tsx:60 — FunctionTooLong — AnyOfField 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: datePickerHooks.useDatePicker packages/daisyui/src/widgets/datePickerHooks.ts:344 — FunctionTooLong — useDatePicker runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: fancy-multi-select.FancyMultiSelect packages/shadcn/src/components/ui/fancy-multi-select.tsx:86 — FunctionTooLong — FancyMultiSelect runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SchemaField.useSchemaFieldPlan packages/core/src/components/fields/SchemaField.tsx:1265 — FunctionTooLong — useSchemaFieldPlan runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: getDefaultFormState.objectDefaults packages/utils/src/schema/getDefaultFormState.ts:1569 — FunctionTooLong — objectDefaults runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ArrayField.ArrayFieldItemInner packages/core/src/components/fields/ArrayField.tsx:656 — FunctionTooLong — ArrayFieldItemInner runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: fancy-select.FancySelect packages/shadcn/src/components/ui/fancy-select.tsx:177 — FunctionTooLong — FancySelect runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: useSchemaFieldPresentation.useSchemaFieldPresentation packages/core/src/components/fields/useSchemaFieldPresentation.ts:302 — FunctionTooLong — useSchemaFieldPresentation runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ArrayField.ArrayField packages/core/src/components/fields/ArrayField.tsx:1253 — FunctionTooLong — ArrayField runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: LayoutGridField.LayoutGridFieldComponent REDACTED:906 — FunctionTooLong — LayoutGridFieldComponent runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: retrieveSchema.buildView packages/utils/src/schema/retrieveSchema.ts:715 — FunctionTooLong — buildView runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: formDataForNewOption.formDataForNewOption packages/core/src/components/fields/formDataForNewOption.ts:353 — FunctionTooLong — formDataForNewOption runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: getDefaultFormState.foldView packages/utils/src/schema/getDefaultFormState.ts:967 — FunctionTooLong — foldView runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: validationTargets.derive packages/utils/src/schema/graph/validationTargets.ts:724 — FunctionTooLong — derive runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: BaseInputTemplate.BaseInputTemplate packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx:91 — FunctionTooLong — BaseInputTemplate runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: LayoutMultiSchemaField.LayoutMultiSchemaField packages/core/src/components/fields/LayoutMultiSchemaField.tsx:60 — FunctionTooLong — LayoutMultiSchemaField runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SelectWidget.SelectWidget packages/mui/src/SelectWidget/SelectWidget.tsx:100 — FunctionTooLong — SelectWidget runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× 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: FallbackField.FallbackUiField packages/core/src/components/fields/FallbackField.tsx:487 — FunctionTooLong — FallbackUiField runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.SelectWidget packages/antd/src/widgets/SelectWidget/index.tsx:32 — FunctionTooLong — SelectWidget runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.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: ArrayField.FixedArray packages/core/src/components/fields/ArrayField.tsx:1030 — FunctionTooLong — FixedArray runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 11 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×31
  • No assertions: types the errors of rawValidation() as the engine's packages/validator-ata/test/createPrecompiledValidator.test.ts:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: types the errors of rawValidation() as the engine's packages/validator-ata/test/customizeValidator.test.ts: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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: types the errors of rawValidation() as the engine's packages/validator-ajv8/test/createPrecompiledValidator.test.ts:15 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: types the errors of rawValidation() as the engine's packages/validator-ajv8/test/customizeValidator.test.ts:11 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: is the selection or the emptyValue given, never any packages/utils/test/enumOptionSelectedValue.test.ts:167 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: requires the emptyValue when its type is named packages/utils/test/enumOptionSelectedValue.test.ts:185 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: resolves explicit type arguments with a schema default to the overload that returns the schema packages/utils/test/getFromSchemaTypes.test.ts: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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: types a widget's declarations without the widget owner, which has no widget beneath it packages/utils/test/getPresentationDeclaration.test.ts:295 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: reads no declaration off a component, which a wrapper would not carry packages/utils/test/getPresentationDeclaration.test.ts:303 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fits a whole set of declared templates packages/utils/test/getTemplate.test.ts:403 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: accepts any kind of component, alone or in a group packages/utils/test/getTemplate.test.ts:407 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: narrows to a component taking the props the caller names packages/utils/test/isComponentType.test.tsx:42 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: takes `components` and `errorMessage` held in a value of an interface type packages/utils/test/jsonSchemaAugmentation.test.ts:20 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: takes Ajv's `nullable` as a boolean packages/utils/test/jsonSchemaAugmentation.test.ts:29 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: takes a field a schema declares on `discriminator` by augmenting it packages/utils/test/jsonSchemaAugmentation.test.ts:36 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: reads a field typed `any` back as `unknown` packages/utils/test/uiSchemaTypes.test.ts:230 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: rejects an extension reusing one of RJSF's option names, or declaring an index signature packages/utils/test/uiSchemaTypes.test.ts:540 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: rejects a theme's key reusing RJSF's, and a user's key reusing the theme's packages/utils/test/uiSchemaTypes.test.ts:555 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: types the result without the options it strips, even with the index signature of a widget's options packages/mantine/test/utils.test.ts:85 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: rejects a user extension reusing an option name the widgets read packages/mantine/test/utils.test.ts:95 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: rejects a user extension of the global options reusing an option name the widgets read packages/daisyui/test/FieldTemplate.test.tsx:659 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should pass registry prop packages/core/test/ArrayFieldTemplate.test.tsx:280 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: renders without throwing when exactly one child is provided packages/core/test/FieldTemplate.test.tsx:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: is implemented by function Form and exposes only the supported imperative surface packages/core/test/Form.handle.test.tsx:336 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: carries the same members as FormState, with the same types packages/core/test/IChangeEvent.test.ts: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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 6 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×14
  • FileTooLong: schema/getDefaultFormState.ts packages/utils/src/schema/getDefaultFormState.ts — FileTooLong — 1578 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1078 over it, 3.16× 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: fields/SchemaField.tsx packages/core/src/components/fields/SchemaField.tsx — FileTooLong — 1190 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 690 over it, 2.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/formState.ts packages/core/src/components/formState.ts — FileTooLong — 1163 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 663 over it, 2.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: graph/validationTargets.ts packages/utils/src/schema/graph/validationTargets.ts — FileTooLong — 1100 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 600 over it, 2.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/types.ts packages/utils/src/types.ts — FileTooLong — 1074 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 574 over it, 2.15× 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: fields/ArrayField.tsx packages/core/src/components/fields/ArrayField.tsx — FileTooLong — 1063 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 563 over it, 2.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/sanitizeFieldTree.ts packages/core/src/components/sanitizeFieldTree.ts — FileTooLong — 861 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 361 over it, 1.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: graph/mergePlan.ts packages/utils/src/schema/graph/mergePlan.ts — FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 185 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/utils.tsx packages/mantine/src/utils.tsx — FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 169 over it, 1.34× 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: fields/ObjectField.tsx packages/core/src/components/fields/ObjectField.tsx — FileTooLong — 654 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 154 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/formModel.ts packages/core/src/components/formModel.ts — FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: createFormModel (224-1153). The bar is 500 significant lines; this is 135 over it, 1.27× 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: schema/retrieveSchema.ts packages/utils/src/schema/retrieveSchema.ts — FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 106 over it, 1.21× 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: schema/sanitizeDataForNewSchema.ts packages/utils/src/schema/sanitizeDataForNewSchema.ts — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: sanitizeWithFills (480-1004). The bar is 500 significant lines; this is 13 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.
D8 · Code Coverage · Low coverage · ×13
  • Low coverage: packages/chakra-ui/src/ChakraFrameProvider.tsx packages/chakra-ui/src/ChakraFrameProvider.tsx:1 — 22.2% line coverage (2/9).
  • Low coverage: packages/fluentui-rc/src/FluentUIRCFrameProvider.tsx packages/fluentui-rc/src/FluentUIRCFrameProvider.tsx:1 — 28.6% line coverage (2/7).
  • Low coverage: packages/playground/src/components/DemoFrame.tsx packages/playground/src/components/DemoFrame.tsx:1 — 5.0% line coverage (4/80).
  • Low coverage: packages/playground/src/components/GeoPosition.tsx packages/playground/src/components/GeoPosition.tsx:1 — 0.0% line coverage (0/5).
  • Low coverage: packages/playground/src/components/SpecialInput.tsx packages/playground/src/components/SpecialInput.tsx:1 — 14.3% line coverage (1/7).
  • Low coverage: packages/playground/src/components/SubthemeSelector.tsx packages/playground/src/components/SubthemeSelector.tsx:1 — 9.1% line coverage (1/11).
  • Low coverage: packages/playground/src/samples/customArray.tsx packages/playground/src/samples/customArray.tsx:1 — 16.7% line coverage (1/6).
  • Low coverage: packages/playground/src/samples/customFieldAnyOf.tsx packages/playground/src/samples/customFieldAnyOf.tsx:1 — 3.6% line coverage (1/28).
  • Low coverage: packages/playground/src/samples/customObject.tsx packages/playground/src/samples/customObject.tsx:1 — 16.7% line coverage (1/6).
  • Low coverage: packages/playground/src/samples/layoutGrid.tsx packages/playground/src/samples/layoutGrid.tsx:1 — 42.9% line coverage (3/7).
  • Low coverage: packages/playground/src/samples/validation.ts packages/playground/src/samples/validation.ts:1 — 23.1% line coverage (3/13).
  • Low coverage: REDACTED REDACTED:1 — 12.5% line coverage (1/8).
  • Low coverage: packages/shadcn/src/components/ui/dialog.tsx packages/shadcn/src/components/ui/dialog.tsx:1 — 9.1% line coverage (1/11).
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×10
  • Recursive walk over a caller-supplied document has no depth cap packages/validator-cfworker/src/validator.ts:43 — `normalizeFormDataForValidation` is exported and takes `data: unknown` from its caller, and it calls itself at line 43 (`normalizeFormDataForValidation`) with a piece of `data` (and at line 48) — and nowhere in `normalizeFormDataForValidation` 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 `normalizeFormDataForValidation` 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/validator-ajv8/src/dataForValidation.ts:35 — `copyForValidation` is exported and takes `data: unknown` from its caller, and it calls itself at line 35 (`copyForValidation`) with a piece of `data` (and at line 39) — and nowhere in `copyForValidation` 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 `copyForValidation` 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/utils/src/getChangedFields.ts:28 — `getChangedFields` is exported, takes a document from its caller (line 63) and hands it to `getChangedDescendants`, which calls itself at line 28 (`getChangedDescendants`) with a piece of `a` — and nowhere in `getChangedDescendants` 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 `getChangedDescendants` 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/utils/src/hashObject.ts:36 — `sortedJSONStringify` is exported and takes `object: unknown` from its caller, and it calls itself at line 36 (`sortedJSONStringify`) with a piece of `object` (and at line 46) — and nowhere in `sortedJSONStringify` 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 `sortedJSONStringify` 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/utils/src/replaceEqualDeep.ts:67 — `replaceEqualDeep` is exported, takes a document from its caller (line 140) and hands it to `shareUnchanged`, which calls itself at line 67 (`shareUnchanged`) with a piece of `prev` (and at line 82, line 98) — and nowhere in `shareUnchanged` 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 `shareUnchanged` 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/utils/src/toInputValue.ts:14 — `toInputValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 14 (`toInputValue`) with a piece of `value` — and nowhere in `toInputValue` 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 `toInputValue` 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/utils/src/schema/getDefaultFormState.ts:462 — `getDefaultFormState` is exported, takes a document from its caller (line 2559) and hands it to `withNullFills`, which calls itself at line 462 (`withNullFills`) with a piece of `formData` — and nowhere in `withNullFills` 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 `withNullFills` 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/utils/src/schema/omitExtraData.ts:106 — `isValueEmpty` is exported and takes `value: unknown` from its caller, and it calls itself at line 106 (`isValueEmpty`) with a piece of `value` — and nowhere in `isValueEmpty` 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 `isValueEmpty` 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/utils/src/schema/retrieveSchema.ts:813 — `retrieveSchema` is exported, takes a document from its caller (line 97) and hands it to `buildView`, which calls itself at line 813 (`buildView`) with a piece of `data` — and nowhere in `buildView` 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 `buildView` 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/core/src/components/formState.ts:1656 — `freezeFormData` is exported and takes `data: unknown` from its caller, and it calls itself at line 1656 (`freezeFormData`) with a piece of `data` — and nowhere in `freezeFormData` 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 `freezeFormData` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
R11 · Import Boundaries · Boundary violation [package · ×7
  • Boundary violation [package:third-party-deep-import] packages/playground/src/app.tsx:14 — packages/playground/src/app.tsx:14 imports ajv/dist/2019.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/playground/src/app.tsx:15 — packages/playground/src/app.tsx:15 imports ajv/dist/2020.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/utils/src/schema/shallowAllOfMerge.ts:2 — packages/utils/src/schema/shallowAllOfMerge.ts:2 imports @x0k/json-schema-merge/lib/array, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:5 — packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:5 imports ajv/dist/runtime/uri.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:6 — packages/validator-ajv8/src/compileSchemaValidatorsCode.ts:6 imports ajv/dist/standalone/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:relative-cross-package] testing/testSetup.ts:6 — testing/testSetup.ts:6 reaches into another package with a relative path (../packages/utils/src/constants.ts) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] testing/testSetup.ts:7 — testing/testSetup.ts:7 reaches into another package with a relative path (../packages/utils/src/logOnce.ts) — import the package by name instead.
R4 · Test Coverage · No test reaches this file · ×5
  • No test reaches this file packages/playground/src/app.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 tsdown.base.mts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/playground/src/layout/Footer.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/playground/src/layout/Layout.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/playground/src/index.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.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: LayoutMultiSchemaField.tsx ↔ MultiSchemaField.tsx packages/core/src/components/fields/LayoutMultiSchemaField.tsx:1 — `packages/core/src/components/fields/LayoutMultiSchemaField.tsx` and `packages/core/src/components/fields/MultiSchemaField.tsx` change together 65% of the time (11 of the 17 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 `41d54a8e` fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carr…; `fd7f935b` fix 5817, 5818: read the default the fill gives a field when the sche…; `0f64899f` fix 5812: let the tree diff judge the keys an anyOf/oneOf switch disc… — run `git show` on any of them.
  • Change coupling: LayoutMultiSchemaField.tsx ↔ SchemaField.tsx packages/core/src/components/fields/LayoutMultiSchemaField.tsx:1 — `packages/core/src/components/fields/LayoutMultiSchemaField.tsx` and `packages/core/src/components/fields/SchemaField.tsx` change together 59% of the time (10 of the 17 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 10 shared commits counted here, the most recent 3 are `aa17cabf` fix!: stop reading the documented exception keys from ui:options (#5739); `0633dc3e` fix 5419: render a layout grid's discriminated cell through SchemaFie…; `e84af11a` Fix 5359: render a non-object anyOf/oneOf option with its parent's ke… — run `git show` on any of them.
  • Change coupling: BaseInputTemplate.tsx ↔ SelectWidget.tsx packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx:1 — `packages/mui/src/BaseInputTemplate/BaseInputTemplate.tsx` and `packages/mui/src/SelectWidget/SelectWidget.tsx` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `9e7e7477` fix 5600: report chakra's range value on focus, keep the form's props…; `29f4e159` fix(mui)!: put the plan on the control a user focuses, and draw label…; `3508fa8e` feat(mui): add support for MUI-specific props (#5023) — run `git show` on any of them.
  • Change coupling: formDataForNewOption.ts ↔ sanitizeFieldTree.ts packages/core/src/components/fields/formDataForNewOption.ts:1 — `packages/core/src/components/fields/formDataForNewOption.ts` and `packages/core/src/components/sanitizeFieldTree.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 — 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 5 shared commits counted here, the most recent 3 are `41d54a8e` fix 5824: let the tree diff judge the keys an anyOf/oneOf switch carr…; `fd7f935b` fix 5817, 5818: read the default the fill gives a field when the sche…; `0f64899f` fix 5812: let the tree diff judge the keys an anyOf/oneOf switch disc… — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×4
  • Duplicated block (28 lines × 2 locations) packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50 — packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50 · packages/react-bootstrap/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:16 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (28 lines × 2 locations) packages/react-bootstrap/src/CheckboxWidget/CheckboxWidget.tsx:13 — packages/react-bootstrap/src/CheckboxWidget/CheckboxWidget.tsx:13 · packages/shadcn/src/CheckboxWidget/CheckboxWidget.tsx:23 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (28 lines × 2 locations) packages/react-bootstrap/src/IconButton/IconButton.tsx:12 — packages/react-bootstrap/src/IconButton/IconButton.tsx:12 · packages/shadcn/src/IconButton/IconButton.tsx:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (28 lines × 2 locations) packages/validator-ajv8/src/validator.ts:214 — packages/validator-ajv8/src/validator.ts:214 · packages/validator-ata/src/validator.ts:194 — 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) packages/utils/src/getDecimalSeparator.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/utils/src/toDisplayString.ts:52 — 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/utils/src/useFileWidgetProps.ts:95 — 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/utils/src/utcToLocal.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.
D10 · Test Quality · Races the wall clock · ×3
  • Races the wall clock: offers the default years for %s packages/utils/test/getDateElementProps.test.ts:122 — This test reads `new Date()` and compares it against the value the code under test computed from its own clock read, compared exactly in `toEqual([1900, new Date().getFullYear() + 2])`. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
  • Races the wall clock: should render the widgets with the expected options' values packages/core/test/StringField.test.tsx:1964 — This test reads `new Date()` and compares it against the value the code under test computed from its own clock read, compared exactly in `toEqual([ new Date().getFullYear() - 1900 + 3 + 1, 12 + 1, 31 + 1, 24 + 1, 60 + 1, 60 + 1, ])`. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
  • Races the wall clock: should render the widgets with the expected options' values packages/core/test/StringField.test.tsx:2341 — This test reads `new Date()` and compares it against the value the code under test computed from its own clock read, compared exactly in `toEqual([ new Date().getFullYear() - 1900 + 3 + 1, 12 + 1, 31 + 1, ])`. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment packages/validator-ajv8/src/createAjvInstance.ts:14 — // TODO enable this in V6 — 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/utils/src/isCustomWidget.ts:15 — // TODO: Remove the `&& widget !== 'hidden'` once we support hidden widgets for arrays. — 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/utils/src/schema/getClosestMatchingOption.ts:186 — // TODO eventually, deal with enums/arrays — 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.
AC6 · Visual & motion safety · Focus outline removed inline · ×2
  • Focus outline removed inline packages/shadcn/src/components/ui/input.tsx:16 — <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/shadcn/src/components/ui/textarea.tsx:21 — <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).
D1 · Cyclomatic Complexity · omitExtraData.omitExtraData · ×2
  • omitExtraData.omitExtraData::omit (cyclomatic 39) packages/utils/src/schema/omitExtraData.ts:543 — omitExtraData.omitExtraData::omit has cyclomatic complexity 39 (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 (omitExtraData.omitExtraData::handleObject) 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.
  • omitExtraData.omitExtraData::handleObject (cyclomatic 18) packages/utils/src/schema/omitExtraData.ts:191 — omitExtraData.omitExtraData::handleObject has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (omitExtraData.omitExtraData::omit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · CheckboxWidget.CheckboxWidget (cyclomatic 18) · ×2
  • CheckboxWidget.CheckboxWidget (cyclomatic 18) packages/mantine/src/widgets/CheckboxWidget.tsx:22 — CheckboxWidget.CheckboxWidget has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 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.
  • CheckboxWidget.CheckboxWidget (cyclomatic 18) packages/shadcn/src/CheckboxWidget/CheckboxWidget.tsx:23 — CheckboxWidget.CheckboxWidget has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SelectWidget.SelectWidget (cyclomatic 16) · ×2
  • SelectWidget.SelectWidget (cyclomatic 16) packages/mantine/src/widgets/SelectWidget.tsx:33 — SelectWidget.SelectWidget has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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.
  • SelectWidget.SelectWidget (cyclomatic 16) packages/mui/src/SelectWidget/SelectWidget.tsx:100 — SelectWidget.SelectWidget has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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.
D10 · Test Quality · Skipped test · ×2
  • Skipped test: %s widget only references elements that exist when inputWrapperOrder leaves the label out packages/mantine/test/AriaLabelledBy.test.tsx:1122 — Skipped — switched off by test.skip.each
  • Skipped test: does not call onChange when disabled packages/daisyui/test/RatingWidget.test.tsx:243 — Skipped — switched off by test.skip
D2 · Cognitive Complexity · omitExtraData.omitExtraData · ×2
  • omitExtraData.omitExtraData::omit (cognitive 40) packages/utils/src/schema/omitExtraData.ts:543 — omitExtraData.omitExtraData::omit has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 10, loops 2 (5 pts), ternaries 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (omitExtraData.omitExtraData::handleObject) 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.
  • omitExtraData.omitExtraData::handleObject (cognitive 31) packages/utils/src/schema/omitExtraData.ts:191 — omitExtraData.omitExtraData::handleObject has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (omitExtraData.omitExtraData::omit) 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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: @rjsf/utils — @rjsf/utils: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
  • Off the main sequence: @rjsf/core — @rjsf/core: abstractness 0.14, instability 0.15, distance 0.71 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×2
  • Duplicated block (31 lines × 2 locations) packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:78 — packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:78 · packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:77 — 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 (31 lines × 2 locations) packages/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18 — packages/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18 · packages/mui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:47 — 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 (27 lines × 2 locations) · ×2
  • Duplicated block (27 lines × 2 locations) packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:68 — packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:68 · packages/shadcn/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:93 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (27 lines × 2 locations) packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:19 — packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:19 · packages/shadcn/src/SelectWidget/SelectWidget.tsx:61 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×2
  • Duplicated block (26 lines × 2 locations) packages/react-bootstrap/src/BaseInputTemplate/BaseInputTemplate.tsx:54 — packages/react-bootstrap/src/BaseInputTemplate/BaseInputTemplate.tsx:54 · packages/shadcn/src/BaseInputTemplate/BaseInputTemplate.tsx:61 — 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 (26 lines × 2 locations) packages/react-bootstrap/src/TextareaWidget/TextareaWidget.tsx:6 — packages/react-bootstrap/src/TextareaWidget/TextareaWidget.tsx:6 · packages/shadcn/src/TextareaWidget/TextareaWidget.tsx:12 — 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 (25 lines × 2 locations) · ×2
  • Duplicated block (25 lines × 2 locations) packages/antd/src/widgets/index.ts:17 — packages/antd/src/widgets/index.ts:17 · packages/mantine/src/widgets/index.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (25 lines × 2 locations) packages/bootstrap3/src/CyclicSchemaExpandTemplate.tsx:9 — packages/bootstrap3/src/CyclicSchemaExpandTemplate.tsx:9 · packages/core/src/components/templates/CyclicSchemaExpandTemplate.tsx:8 — 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.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark packages/playground/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC4 · Keyboard semantics · Modal dialog does not manage focus · ×1
  • Modal dialog does not manage focus packages/daisyui/src/widgets/DatePickerTrigger.tsx:192 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
D1 · Cyclomatic Complexity · sanitizeFieldTree.walk (cyclomatic 109) · ×1
  • sanitizeFieldTree.walk (cyclomatic 109) packages/core/src/components/sanitizeFieldTree.ts:828 — sanitizeFieldTree.walk has cyclomatic complexity 109 (threshold 15). Of this number, 78 points are the body's own statements and 31 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ObjectField.ObjectField (cyclomatic 79) · ×1
  • ObjectField.ObjectField (cyclomatic 79) packages/core/src/components/fields/ObjectField.tsx:434 — ObjectField.ObjectField has cyclomatic complexity 79 (threshold 15). Most of this is not in the body itself: 12 of the 79 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 712, 868, 638, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · fancy-select.FancySelect (cyclomatic 67) · ×1
  • fancy-select.FancySelect (cyclomatic 67) packages/shadcn/src/components/ui/fancy-select.tsx:177 — fancy-select.FancySelect has cyclomatic complexity 67 (threshold 15). Of this number, 18 points are the body's own statements and 49 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · getDefaultFormState.foldView (cyclomatic 66) · ×1
  • getDefaultFormState.foldView (cyclomatic 66) packages/utils/src/schema/getDefaultFormState.ts:967 — getDefaultFormState.foldView has cyclomatic complexity 66 (threshold 15). Of this number, 64 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SelectWidget.SelectWidget (cyclomatic 65) · ×1
  • SelectWidget.SelectWidget (cyclomatic 65) packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:134 — SelectWidget.SelectWidget has cyclomatic complexity 65 (threshold 15). Of this number, 17 points are the body's own statements and 48 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · getDefaultFormState.objectDefaults (cyclomatic 63) · ×1
  • getDefaultFormState.objectDefaults (cyclomatic 63) packages/utils/src/schema/getDefaultFormState.ts:1569 — getDefaultFormState.objectDefaults has cyclomatic complexity 63 (threshold 15). Of this number, 53 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SchemaField.SchemaFieldRender (cyclomatic 57) · ×1
  • SchemaField.SchemaFieldRender (cyclomatic 57) packages/core/src/components/fields/SchemaField.tsx:1573 — SchemaField.SchemaFieldRender has cyclomatic complexity 57 (threshold 15). Of this number, 35 points are the body's own statements and 22 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · retrieveSchema.buildView (cyclomatic 56) · ×1
  • retrieveSchema.buildView (cyclomatic 56) packages/utils/src/schema/retrieveSchema.ts:715 — retrieveSchema.buildView has cyclomatic complexity 56 (threshold 15). Of this number, 34 points are the body's own statements and 22 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SchemaField.useSchemaFieldPlan (cyclomatic 52) · ×1
  • SchemaField.useSchemaFieldPlan (cyclomatic 52) packages/core/src/components/fields/SchemaField.tsx:1265 — SchemaField.useSchemaFieldPlan has cyclomatic complexity 52 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · getUiRequiredErrorSchema.walk (cyclomatic 50) · ×1
  • getUiRequiredErrorSchema.walk (cyclomatic 50) packages/utils/src/schema/getUiRequiredErrorSchema.ts:244 — getUiRequiredErrorSchema.walk has cyclomatic complexity 50 (threshold 15). Of this number, 42 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sanitizeDataForNewSchema.sanitizeWithFills · ×1
  • sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem (cyclomatic 50) packages/utils/src/schema/sanitizeDataForNewSchema.ts:842 — sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (sanitizeDataForNewSchema.sanitizeWithFills) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · sanitizeFieldTree.judge (cyclomatic 47) · ×1
  • sanitizeFieldTree.judge (cyclomatic 47) packages/core/src/components/sanitizeFieldTree.ts:405 — sanitizeFieldTree.judge has cyclomatic complexity 47 (threshold 15). Of this number, 44 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · fancy-multi-select.FancyMultiSelect (cyclomatic 47) · ×1
  • fancy-multi-select.FancyMultiSelect (cyclomatic 47) packages/shadcn/src/components/ui/fancy-multi-select.tsx:86 — fancy-multi-select.FancyMultiSelect has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 13 of the 47 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 201, handleMouseDown, a function literal at line 185, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SchemaField.getFieldComponent (cyclomatic 43) · ×1
  • SchemaField.getFieldComponent (cyclomatic 43) packages/core/src/components/fields/SchemaField.tsx:682 — SchemaField.getFieldComponent has cyclomatic complexity 43 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · MultiSchemaField.AnyOfField (cyclomatic 43) · ×1
  • MultiSchemaField.AnyOfField (cyclomatic 43) packages/core/src/components/fields/MultiSchemaField.tsx:60 — MultiSchemaField.AnyOfField has cyclomatic complexity 43 (threshold 15). Of this number, 30 points are the body's own statements and 13 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · sanitizeDataForNewSchema.sanitizeWithFills (cyclomatic 42) · ×1
  • sanitizeDataForNewSchema.sanitizeWithFills (cyclomatic 42) packages/utils/src/schema/sanitizeDataForNewSchema.ts:480 — sanitizeDataForNewSchema.sanitizeWithFills has cyclomatic complexity 42 (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 (sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · formDataForNewOption.formDataForNewOption (cyclomatic 36) · ×1
  • formDataForNewOption.formDataForNewOption (cyclomatic 36) packages/core/src/components/fields/formDataForNewOption.ts:353 — formDataForNewOption.formDataForNewOption has cyclomatic complexity 36 (threshold 15). Of this number, 20 points are the body's own statements and 16 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · formModel.createFormModel.change (cyclomatic 36) · ×1
  • formModel.createFormModel.change (cyclomatic 36) packages/core/src/components/formModel.ts:597 — formModel.createFormModel.change has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 653, isForwarded). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · resolveFieldPresentation.resolveFieldPresentation (cyclomatic 35) · ×1
  • resolveFieldPresentation.resolveFieldPresentation (cyclomatic 35) packages/utils/src/resolveFieldPresentation.ts:165 — resolveFieldPresentation.resolveFieldPresentation has cyclomatic complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · validationTargets.walkFrom (cyclomatic 35) · ×1
  • validationTargets.walkFrom (cyclomatic 35) packages/utils/src/schema/graph/validationTargets.ts:1710 — validationTargets.walkFrom has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 6 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (leave, enter, a function literal at line 1777, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ArrayField.ArrayFieldItemInner (cyclomatic 33) · ×1
  • ArrayField.ArrayFieldItemInner (cyclomatic 33) packages/core/src/components/fields/ArrayField.tsx:656 — ArrayField.ArrayFieldItemInner has cyclomatic complexity 33 (threshold 15). Of this number, 28 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.
D1 · Cyclomatic Complexity · RatingWidget.RatingWidget (cyclomatic 33) · ×1
  • RatingWidget.RatingWidget (cyclomatic 33) packages/core/src/components/widgets/RatingWidget.tsx:36 — RatingWidget.RatingWidget has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 149, handleStarKeyDown, a function literal at line 83, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · datePickerHooks.useDatePicker (cyclomatic 32) · ×1
  • datePickerHooks.useDatePicker (cyclomatic 32) packages/daisyui/src/widgets/datePickerHooks.ts:344 — datePickerHooks.useDatePicker has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 553, 656, 599, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ArrayField.ArrayField (cyclomatic 31) · ×1
  • ArrayField.ArrayField (cyclomatic 31) packages/core/src/components/fields/ArrayField.tsx:1253 — ArrayField.ArrayField has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1310, 1386, 1334, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · BaseInputTemplate.BaseInputTemplate (cyclomatic 31) · ×1
  • BaseInputTemplate.BaseInputTemplate (cyclomatic 31) packages/mantine/src/templates/BaseInputTemplate.tsx:34 — BaseInputTemplate.BaseInputTemplate has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · replaceEqualDeep.shareUnchanged (cyclomatic 31) · ×1
  • replaceEqualDeep.shareUnchanged (cyclomatic 31) packages/utils/src/replaceEqualDeep.ts:55 — replaceEqualDeep.shareUnchanged has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · getRenderedOptionSchema.renderOption (cyclomatic 31) · ×1
  • getRenderedOptionSchema.renderOption (cyclomatic 31) packages/utils/src/getRenderedOptionSchema.ts:289 — getRenderedOptionSchema.renderOption has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · getDefaultFormState.formDataMatching (cyclomatic 30) · ×1
  • getDefaultFormState.formDataMatching (cyclomatic 30) packages/utils/src/schema/getDefaultFormState.ts:2441 — getDefaultFormState.formDataMatching has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · getInputProps.getInputProps (cyclomatic 30) · ×1
  • getInputProps.getInputProps (cyclomatic 30) packages/utils/src/getInputProps.ts:56 — getInputProps.getInputProps has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RangeWidget.RangeWidget (cyclomatic 28) · ×1
  • RangeWidget.RangeWidget (cyclomatic 28) packages/mui/src/RangeWidget/RangeWidget.tsx:36 — RangeWidget.RangeWidget has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · getDefaultFormState.arrayDefaults (cyclomatic 28) · ×1
  • getDefaultFormState.arrayDefaults (cyclomatic 28) packages/utils/src/schema/getDefaultFormState.ts:1971 — getDefaultFormState.arrayDefaults has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · compileSchemaValidatorsCode.compileSchemaValidatorsCode (cyclomatic 27) · ×1
  • compileSchemaValidatorsCode.compileSchemaValidatorsCode (cyclomatic 27) REDACTED:567 — compileSchemaValidatorsCode.compileSchemaValidatorsCode has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.BaseInputTemplate (cyclomatic 26) · ×1
  • index.BaseInputTemplate (cyclomatic 26) packages/antd/src/templates/BaseInputTemplate/index.tsx:28 — index.BaseInputTemplate has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useSendOptionSwitch.useSendOptionSwitch (cyclomatic 26) · ×1
  • useSendOptionSwitch.useSendOptionSwitch (cyclomatic 26) packages/core/src/hooks/useSendOptionSwitch.ts:100 — useSendOptionSwitch.useSendOptionSwitch has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 104, 129, 136, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · getRenderedOptionSchema.meetKeyword (cyclomatic 26) · ×1
  • getRenderedOptionSchema.meetKeyword (cyclomatic 26) packages/utils/src/getRenderedOptionSchema.ts:146 — getRenderedOptionSchema.meetKeyword has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validationTargets.branchingNodes (cyclomatic 25) · ×1
  • validationTargets.branchingNodes (cyclomatic 25) packages/utils/src/schema/graph/validationTargets.ts:1425 — validationTargets.branchingNodes has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 1471, partsOf, a function literal at line 1448, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FallbackField.castToNewType (cyclomatic 23) · ×1
  • FallbackField.castToNewType (cyclomatic 23) packages/core/src/components/fields/FallbackField.tsx:425 — FallbackField.castToNewType has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.SelectWidget (cyclomatic 22) · ×1
  • index.SelectWidget (cyclomatic 22) packages/antd/src/widgets/SelectWidget/index.tsx:32 — index.SelectWidget has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SchemaField.warnOfUnshownOptionLabels (cyclomatic 22) · ×1
  • SchemaField.warnOfUnshownOptionLabels (cyclomatic 22) packages/core/src/components/fields/SchemaField.tsx:229 — SchemaField.warnOfUnshownOptionLabels has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LayoutGridField.LayoutGridFieldComponent (cyclomatic 22) · ×1
  • LayoutGridField.LayoutGridFieldComponent (cyclomatic 22) REDACTED:906 — LayoutGridField.LayoutGridFieldComponent has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · validationTargets.derive (cyclomatic 22) · ×1
  • validationTargets.derive (cyclomatic 22) packages/utils/src/schema/graph/validationTargets.ts:724 — validationTargets.derive has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (validationTargets.derive::sub) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · getDefaultFormState.foldOption (cyclomatic 22) · ×1
  • getDefaultFormState.foldOption (cyclomatic 22) packages/utils/src/schema/getDefaultFormState.ts:1342 — getDefaultFormState.foldOption has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.FieldTemplate (cyclomatic 21) · ×1
  • index.FieldTemplate (cyclomatic 21) packages/antd/src/templates/FieldTemplate/index.tsx:26 — index.FieldTemplate 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.
D1 · Cyclomatic Complexity · ArrayField.FixedArray (cyclomatic 21) · ×1
  • ArrayField.FixedArray (cyclomatic 21) packages/core/src/components/fields/ArrayField.tsx:1030 — ArrayField.FixedArray has cyclomatic complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · mergeDefaultsWithFormData.mergeDefaultsWithFormData (cyclomatic 21) · ×1
  • mergeDefaultsWithFormData.mergeDefaultsWithFormData (cyclomatic 21) packages/utils/src/mergeDefaultsWithFormData.ts:33 — mergeDefaultsWithFormData.mergeDefaultsWithFormData has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resolveUiSchema.resolveUiSchema (cyclomatic 21) · ×1
  • resolveUiSchema.resolveUiSchema (cyclomatic 21) packages/utils/src/resolveUiSchema.ts:44 — resolveUiSchema.resolveUiSchema 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.
D1 · Cyclomatic Complexity · getGroupAttributes.getGroupAttributes (cyclomatic 21) · ×1
  • getGroupAttributes.getGroupAttributes (cyclomatic 21) packages/utils/src/getGroupAttributes.ts:42 — getGroupAttributes.getGroupAttributes has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · compileSchemaValidatorsCode.standalone (cyclomatic 21) · ×1
  • compileSchemaValidatorsCode.standalone (cyclomatic 21) REDACTED:370 — compileSchemaValidatorsCode.standalone has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (renamed, rewrite, nameOf, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · formModel.focusForId (cyclomatic 20) · ×1
  • formModel.focusForId (cyclomatic 20) packages/core/src/components/formModel.ts:164 — formModel.focusForId has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 194, a function literal at line 204, isContainer, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · formModel.createFormModel (cyclomatic 19) · ×1
  • formModel.createFormModel (cyclomatic 19) packages/core/src/components/formModel.ts:224 — formModel.createFormModel 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 4 function literals inside it that branch (lines 875, 915, 857, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · formState.applyChangeToData (cyclomatic 19) · ×1
  • formState.applyChangeToData (cyclomatic 19) packages/core/src/components/formState.ts:1768 — formState.applyChangeToData has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DatePickerTrigger.DatePickerTrigger (cyclomatic 19) · ×1
  • DatePickerTrigger.DatePickerTrigger (cyclomatic 19) packages/daisyui/src/widgets/DatePickerTrigger.tsx:69 — DatePickerTrigger.DatePickerTrigger has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NumberField.NumberField (cyclomatic 18) · ×1
  • NumberField.NumberField (cyclomatic 18) packages/core/src/components/fields/NumberField.tsx:26 — NumberField.NumberField has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · formState.settleFormData (cyclomatic 18) · ×1
  • formState.settleFormData (cyclomatic 18) packages/core/src/components/formState.ts:1296 — formState.settleFormData has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LayoutGridField.getSchemaDetailsForField (cyclomatic 18) · ×1
  • LayoutGridField.getSchemaDetailsForField (cyclomatic 18) REDACTED:476 — LayoutGridField.getSchemaDetailsForField has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validationTargets.derive · ×1
  • validationTargets.derive::sub (cyclomatic 18) packages/utils/src/schema/graph/validationTargets.ts:756 — validationTargets.derive::sub has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (validationTargets.derive) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · validationTargets.withSharedCopies (cyclomatic 18) · ×1
  • validationTargets.withSharedCopies (cyclomatic 18) packages/utils/src/schema/graph/validationTargets.ts:916 — validationTargets.withSharedCopies has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (write, writeKeyword, reaches). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · getDefaultFormState.chooseOption (cyclomatic 18) · ×1
  • getDefaultFormState.chooseOption (cyclomatic 18) packages/utils/src/schema/getDefaultFormState.ts:1267 — getDefaultFormState.chooseOption has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · index.ObjectFieldTemplate (cyclomatic 17) · ×1
  • index.ObjectFieldTemplate (cyclomatic 17) packages/antd/src/templates/ObjectFieldTemplate/index.tsx:34 — index.ObjectFieldTemplate 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 one function item inside it that branches (calculateColSpan). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · formModel.createFormModel.applyEdit (cyclomatic 17) · ×1
  • formModel.createFormModel.applyEdit (cyclomatic 17) packages/core/src/components/formModel.ts:502 — formModel.createFormModel.applyEdit has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · sanitizeFieldTree.previousKeys (cyclomatic 17) · ×1
  • sanitizeFieldTree.previousKeys (cyclomatic 17) packages/core/src/components/sanitizeFieldTree.ts:199 — sanitizeFieldTree.previousKeys has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BooleanInput.BooleanInput (cyclomatic 17) · ×1
  • BooleanInput.BooleanInput (cyclomatic 17) packages/daisyui/src/widgets/BooleanInput.tsx:36 — BooleanInput.BooleanInput has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · DemoFrame.AntdPopupPatcher (cyclomatic 17) · ×1
  • DemoFrame.AntdPopupPatcher (cyclomatic 17) packages/playground/src/components/DemoFrame.tsx:68 — DemoFrame.AntdPopupPatcher 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 77, 115, 128, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · validationTargets.readTypesFrom (cyclomatic 17) · ×1
  • validationTargets.readTypesFrom (cyclomatic 17) packages/utils/src/schema/graph/validationTargets.ts:1230 — validationTargets.readTypesFrom has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · getRenderedOptionSchema.meetSchemas (cyclomatic 17) · ×1
  • getRenderedOptionSchema.meetSchemas (cyclomatic 17) packages/utils/src/getRenderedOptionSchema.ts:95 — getRenderedOptionSchema.meetSchemas has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · getDisplayLabel.getDisplayLabel (cyclomatic 17) · ×1
  • getDisplayLabel.getDisplayLabel (cyclomatic 17) packages/utils/src/schema/getDisplayLabel.ts:32 — getDisplayLabel.getDisplayLabel has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · schemaList.schemaList (cyclomatic 17) · ×1
  • schemaList.schemaList (cyclomatic 17) packages/validator-ata/src/schemaList.ts:34 — schemaList.schemaList has cyclomatic complexity 17 (threshold 15). 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 (a function literal at line 55, withDraft04Id, a function literal at line 53). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · CheckboxWidget.CheckboxWidget (cyclomatic 16) · ×1
  • CheckboxWidget.CheckboxWidget (cyclomatic 16) packages/core/src/components/widgets/CheckboxWidget.tsx:21 — CheckboxWidget.CheckboxWidget has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · sanitizeFieldTree.oldFillOutOf (cyclomatic 16) · ×1
  • sanitizeFieldTree.oldFillOutOf (cyclomatic 16) packages/core/src/components/sanitizeFieldTree.ts:693 — sanitizeFieldTree.oldFillOutOf has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LayoutGridField.schemaHolding (cyclomatic 16) · ×1
  • LayoutGridField.schemaHolding (cyclomatic 16) REDACTED:382 — LayoutGridField.schemaHolding has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RangeWidget.RangeWidget (cyclomatic 16) · ×1
  • RangeWidget.RangeWidget (cyclomatic 16) packages/shadcn/src/RangeWidget/RangeWidget.tsx:48 — RangeWidget.RangeWidget 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 9 function items inside it that branch (commitMinimum, a function literal at line 73, a function literal at line 76, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · optionsList.optionsList (cyclomatic 16) · ×1
  • optionsList.optionsList (cyclomatic 16) packages/utils/src/optionsList.ts:58 — optionsList.optionsList has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · findFieldInSchema.findKey (cyclomatic 16) · ×1
  • findFieldInSchema.findKey (cyclomatic 16) packages/utils/src/schema/findFieldInSchema.ts:56 — findFieldInSchema.findKey has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · getDateTimeLocalValue.getDateTimeLocalValue (cyclomatic 16) · ×1
  • getDateTimeLocalValue.getDateTimeLocalValue (cyclomatic 16) packages/utils/src/getDateTimeLocalValue.ts:36 — getDateTimeLocalValue.getDateTimeLocalValue has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · processRawValidationErrors.transformRJSFValidationErrors (cyclomatic 16) · ×1
  • processRawValidationErrors.transformRJSFValidationErrors (cyclomatic 16) packages/validator-ata/src/processRawValidationErrors.ts:67 — processRawValidationErrors.transformRJSFValidationErrors 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 92, 77, 89). 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.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment packages/core/test/StringField.test.tsx:1520 — // XXX import and use conversion helper — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · sanitizeFieldTree.walk (cognitive 145) · ×1
  • sanitizeFieldTree.walk (cognitive 145) packages/core/src/components/sanitizeFieldTree.ts:828 — sanitizeFieldTree.walk has cognitive complexity 145 (threshold 15). Drivers by points: ternaries 29 (69 pts), if/else 25 (48 pts), boolean chains 26, loops 1 (2 pts) (nesting depth added 64). Of this number, 102 points are the body's own statements and 43 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ObjectField.ObjectField (cognitive 97) · ×1
  • ObjectField.ObjectField (cognitive 97) packages/core/src/components/fields/ObjectField.tsx:434 — ObjectField.ObjectField has cognitive complexity 97 (threshold 15). Drivers by points: if/else 31 (41 pts), ternaries 21 (31 pts), boolean chains 18, loops 3 (4 pts), error handling 2 (3 pts) (nesting depth added 22). Most of this is not in the body itself: 13 of the 97 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 868, 712, 516, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · getDefaultFormState.objectDefaults (cognitive 76) · ×1
  • getDefaultFormState.objectDefaults (cognitive 76) packages/utils/src/schema/getDefaultFormState.ts:1569 — getDefaultFormState.objectDefaults has cognitive complexity 76 (threshold 15). Drivers by points: boolean chains 30, if/else 17 (30 pts), ternaries 8 (13 pts), loops 2 (3 pts) (nesting depth added 19). Of this number, 63 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · retrieveSchema.buildView (cognitive 73) · ×1
  • retrieveSchema.buildView (cognitive 73) packages/utils/src/schema/retrieveSchema.ts:715 — retrieveSchema.buildView has cognitive complexity 73 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 20, ternaries 9 (16 pts), loops 2 (nesting depth added 20). Of this number, 35 points are the body's own statements and 38 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SelectWidget.SelectWidget (cognitive 67) · ×1
  • SelectWidget.SelectWidget (cognitive 67) packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:134 — SelectWidget.SelectWidget has cognitive complexity 67 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 26, ternaries 11 (14 pts) (nesting depth added 7). Most of this is not in the body itself: 15 of the 67 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 250, a function literal at line 174, renderOption, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · fancy-select.FancySelect (cognitive 63) · ×1
  • fancy-select.FancySelect (cognitive 63) packages/shadcn/src/components/ui/fancy-select.tsx:177 — fancy-select.FancySelect has cognitive complexity 63 (threshold 15). Drivers by points: boolean chains 34, if/else 17, ternaries 9 (12 pts) (nesting depth added 3). Of this number, 17 points are the body's own statements and 46 belong to 11 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.
D2 · Cognitive Complexity · getDefaultFormState.foldView (cognitive 60) · ×1
  • getDefaultFormState.foldView (cognitive 60) packages/utils/src/schema/getDefaultFormState.ts:967 — getDefaultFormState.foldView has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 25, ternaries 5 (8 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · formDataForNewOption.formDataForNewOption (cognitive 57) · ×1
  • formDataForNewOption.formDataForNewOption (cognitive 57) packages/core/src/components/fields/formDataForNewOption.ts:353 — formDataForNewOption.formDataForNewOption has cognitive complexity 57 (threshold 15). Drivers by points: if/else 15 (36 pts), ternaries 5 (13 pts), boolean chains 8 (nesting depth added 29). Of this number, 27 points are the body's own statements and 30 belong to 7 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · sanitizeDataForNewSchema.sanitizeWithFills (cognitive 50) · ×1
  • sanitizeDataForNewSchema.sanitizeWithFills (cognitive 50) packages/utils/src/schema/sanitizeDataForNewSchema.ts:480 — sanitizeDataForNewSchema.sanitizeWithFills has cognitive complexity 50 (threshold 15). Drivers by points: if/else 47 (105 pts), ternaries 26 (72 pts), boolean chains 61, loops 1 (2 pts) (nesting depth added 105). 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 (sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · sanitizeFieldTree.judge (cognitive 47) · ×1
  • sanitizeFieldTree.judge (cognitive 47) packages/core/src/components/sanitizeFieldTree.ts:405 — sanitizeFieldTree.judge has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 16, ternaries 6 (12 pts) (nesting depth added 11). Of this number, 46 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getUiRequiredErrorSchema.walk (cognitive 47) · ×1
  • getUiRequiredErrorSchema.walk (cognitive 47) packages/utils/src/schema/getUiRequiredErrorSchema.ts:244 — getUiRequiredErrorSchema.walk has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 16, if/else 13 (16 pts), ternaries 8 (15 pts) (nesting depth added 10). Of this number, 38 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaField.SchemaFieldRender (cognitive 46) · ×1
  • SchemaField.SchemaFieldRender (cognitive 46) packages/core/src/components/fields/SchemaField.tsx:1573 — SchemaField.SchemaFieldRender has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 18, ternaries 17 (18 pts), if/else 8 (9 pts), loops 1 (nesting depth added 2). Of this number, 27 points are the body's own statements and 19 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · validationTargets.readTypesFrom (cognitive 44) · ×1
  • validationTargets.readTypesFrom (cognitive 44) packages/utils/src/schema/graph/validationTargets.ts:1230 — validationTargets.readTypesFrom has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 8 (25 pts), if/else 5 (13 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 27). Of this number, 38 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getRenderedOptionSchema.renderOption (cognitive 43) · ×1
  • getRenderedOptionSchema.renderOption (cognitive 43) packages/utils/src/getRenderedOptionSchema.ts:289 — getRenderedOptionSchema.renderOption has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 7, loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 14). Of this number, 41 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sanitizeDataForNewSchema.sanitizeWithFills · ×1
  • sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem (cognitive 43) packages/utils/src/schema/sanitizeDataForNewSchema.ts:842 — sanitizeDataForNewSchema.sanitizeWithFills::sanitizeItem has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 22, if/else 12 (15 pts), ternaries 4 (6 pts) (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (sanitizeDataForNewSchema.sanitizeWithFills) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SchemaField.useSchemaFieldPlan (cognitive 42) · ×1
  • SchemaField.useSchemaFieldPlan (cognitive 42) packages/core/src/components/fields/SchemaField.tsx:1265 — SchemaField.useSchemaFieldPlan has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 23, ternaries 18, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · MultiSchemaField.AnyOfField (cognitive 42) · ×1
  • MultiSchemaField.AnyOfField (cognitive 42) packages/core/src/components/fields/MultiSchemaField.tsx:60 — MultiSchemaField.AnyOfField has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 18, ternaries 14 (15 pts), if/else 7 (9 pts) (nesting depth added 3). Of this number, 28 points are the body's own statements and 14 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · replaceEqualDeep.shareUnchanged (cognitive 42) · ×1
  • replaceEqualDeep.shareUnchanged (cognitive 42) packages/utils/src/replaceEqualDeep.ts:55 — replaceEqualDeep.shareUnchanged has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 4 (9 pts), boolean chains 8, loops 2 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fancy-multi-select.FancyMultiSelect (cognitive 40) · ×1
  • fancy-multi-select.FancyMultiSelect (cognitive 40) packages/shadcn/src/components/ui/fancy-multi-select.tsx:86 — fancy-multi-select.FancyMultiSelect has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 22, if/else 12, ternaries 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 10 of the 40 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 201, handleMouseDown, a function literal at line 185, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · resolveUiSchema.resolveUiSchema (cognitive 39) · ×1
  • resolveUiSchema.resolveUiSchema (cognitive 39) packages/utils/src/resolveUiSchema.ts:44 — resolveUiSchema.resolveUiSchema has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 6, loops 2 (6 pts), ternaries 3 (6 pts), error handling 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDefaultFormState.formDataMatching (cognitive 39) · ×1
  • getDefaultFormState.formDataMatching (cognitive 39) packages/utils/src/schema/getDefaultFormState.ts:2441 — getDefaultFormState.formDataMatching has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 13, ternaries 3 (5 pts), loops 1 (2 pts) (nesting depth added 12). Of this number, 35 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveFieldPresentation.resolveFieldPresentation (cognitive 36) · ×1
  • resolveFieldPresentation.resolveFieldPresentation (cognitive 36) packages/utils/src/resolveFieldPresentation.ts:165 — resolveFieldPresentation.resolveFieldPresentation has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 15, if/else 7 (12 pts), ternaries 8, loops 1 (nesting depth added 5). Of this number, 32 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BaseInputTemplate.BaseInputTemplate (cognitive 34) · ×1
  • BaseInputTemplate.BaseInputTemplate (cognitive 34) packages/mantine/src/templates/BaseInputTemplate.tsx:34 — BaseInputTemplate.BaseInputTemplate has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 15 (21 pts), boolean chains 11, if/else 2 (nesting depth added 6). Of this number, 29 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.BaseInputTemplate (cognitive 32) · ×1
  • index.BaseInputTemplate (cognitive 32) packages/antd/src/templates/BaseInputTemplate/index.tsx:28 — index.BaseInputTemplate has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 15 (26 pts), boolean chains 6 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · formModel.createFormModel.change (cognitive 32) · ×1
  • formModel.createFormModel.change (cognitive 32) packages/core/src/components/formModel.ts:597 — formModel.createFormModel.change has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 14, ternaries 2, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 10 of the 32 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 653, isForwarded). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · processRawValidationErrors.transformRJSFValidationErrors (cognitive 32) · ×1
  • processRawValidationErrors.transformRJSFValidationErrors (cognitive 32) packages/validator-ata/src/processRawValidationErrors.ts:67 — processRawValidationErrors.transformRJSFValidationErrors has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 1 (4 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 15). None of this is in the body itself: all 32 points belong to 3 function literals inside it that branch (lines 92, 77, 89). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · getRenderedOptionSchema.meetKeyword (cognitive 31) · ×1
  • getRenderedOptionSchema.meetKeyword (cognitive 31) packages/utils/src/getRenderedOptionSchema.ts:146 — getRenderedOptionSchema.meetKeyword has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 7, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processRawValidationErrors.transformRJSFValidationErrors (cognitive 31) · ×1
  • processRawValidationErrors.transformRJSFValidationErrors (cognitive 31) packages/validator-ajv8/src/processRawValidationErrors.ts:76 — processRawValidationErrors.transformRJSFValidationErrors has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 1 (4 pts), ternaries 2 (3 pts) (nesting depth added 15). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 99, 86). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · compileSchemaValidatorsCode.compileSchemaValidatorsCode (cognitive 31) · ×1
  • compileSchemaValidatorsCode.compileSchemaValidatorsCode (cognitive 31) REDACTED:567 — compileSchemaValidatorsCode.compileSchemaValidatorsCode has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 7 (8 pts), boolean chains 6, loops 5 (6 pts) (nesting depth added 6). Of this number, 25 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · datePickerHooks.useDatePicker (cognitive 30) · ×1
  • datePickerHooks.useDatePicker (cognitive 30) packages/daisyui/src/widgets/datePickerHooks.ts:344 — datePickerHooks.useDatePicker has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 8, ternaries 4 (nesting depth added 4). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 553, 656, 473, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · SchemaField.getFieldComponent (cognitive 29) · ×1
  • SchemaField.getFieldComponent (cognitive 29) packages/core/src/components/fields/SchemaField.tsx:682 — SchemaField.getFieldComponent has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 22, ternaries 4, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ArrayField.ArrayField (cognitive 29) · ×1
  • ArrayField.ArrayField (cognitive 29) packages/core/src/components/fields/ArrayField.tsx:1253 — ArrayField.ArrayField has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (18 pts), ternaries 6, boolean chains 4, match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1310, 1386, 1354, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · SchemaField.warnOfUnshownOptionLabels (cognitive 28) · ×1
  • SchemaField.warnOfUnshownOptionLabels (cognitive 28) packages/core/src/components/fields/SchemaField.tsx:229 — SchemaField.warnOfUnshownOptionLabels has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 9, if/else 7 (9 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArrayField.ArrayFieldItemInner (cognitive 28) · ×1
  • ArrayField.ArrayFieldItemInner (cognitive 28) packages/core/src/components/fields/ArrayField.tsx:656 — ArrayField.ArrayFieldItemInner has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 22, if/else 4, ternaries 2. Of this number, 23 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.
D2 · Cognitive Complexity · RatingWidget.RatingWidget (cognitive 28) · ×1
  • RatingWidget.RatingWidget (cognitive 28) packages/core/src/components/widgets/RatingWidget.tsx:36 — RatingWidget.RatingWidget has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, ternaries 9 (11 pts), if/else 6 (nesting depth added 2). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 149, a function literal at line 83, getSymbol, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · getInputProps.getInputProps (cognitive 28) · ×1
  • getInputProps.getInputProps (cognitive 28) packages/utils/src/getInputProps.ts:56 — getInputProps.getInputProps has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 8, ternaries 3 (5 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mergeDefaultsWithFormData.mergeDefaultsWithFormData (cognitive 27) · ×1
  • mergeDefaultsWithFormData.mergeDefaultsWithFormData (cognitive 27) packages/utils/src/mergeDefaultsWithFormData.ts:33 — mergeDefaultsWithFormData.mergeDefaultsWithFormData has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 10, ternaries 5 (10 pts), if/else 5 (7 pts) (nesting depth added 7). Of this number, 21 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDefaultFormState.arrayDefaults (cognitive 27) · ×1
  • getDefaultFormState.arrayDefaults (cognitive 27) packages/utils/src/schema/getDefaultFormState.ts:1971 — getDefaultFormState.arrayDefaults has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (11 pts), ternaries 4 (5 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · RangeWidget.RangeWidget (cognitive 26) · ×1
  • RangeWidget.RangeWidget (cognitive 26) packages/mui/src/RangeWidget/RangeWidget.tsx:36 — RangeWidget.RangeWidget has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 10, if/else 3 (nesting depth added 1). Of this number, 16 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · validationTargets.derive (cognitive 26) · ×1
  • validationTargets.derive (cognitive 26) packages/utils/src/schema/graph/validationTargets.ts:724 — validationTargets.derive has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20 (28 pts), ternaries 14 (19 pts), boolean chains 14, loops 4 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (validationTargets.derive::sub) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · LayoutGridField.LayoutGridFieldComponent (cognitive 25) · ×1
  • LayoutGridField.LayoutGridFieldComponent (cognitive 25) REDACTED:906 — LayoutGridField.LayoutGridFieldComponent has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 8 (9 pts), boolean chains 6 (nesting depth added 4). Of this number, 16 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · getDefaultFormState.foldOption (cognitive 25) · ×1
  • getDefaultFormState.foldOption (cognitive 25) packages/utils/src/schema/getDefaultFormState.ts:1342 — getDefaultFormState.foldOption has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 8, if/else 2 (nesting depth added 6). Of this number, 21 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.SelectWidget (cognitive 24) · ×1
  • index.SelectWidget (cognitive 24) packages/antd/src/widgets/SelectWidget/index.tsx:32 — index.SelectWidget has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 7, if/else 4 (5 pts) (nesting depth added 3). Of this number, 13 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · getUiOptions.getUiOptions (cognitive 24) · ×1
  • getUiOptions.getUiOptions (cognitive 24) packages/utils/src/getUiOptions.ts:45 — getUiOptions.getUiOptions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (8 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validationTargets.branchingNodes (cognitive 24) · ×1
  • validationTargets.branchingNodes (cognitive 24) packages/utils/src/schema/graph/validationTargets.ts:1425 — validationTargets.branchingNodes has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), ternaries 4, loops 1 (nesting depth added 3). None of this is in the body itself: all 24 points belong to 8 function items inside it that branch (partsOf, a function literal at line 1471, a function literal at line 1448, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · withIdRefPrefix.withIdRefPrefixObject (cognitive 23) · ×1
  • withIdRefPrefix.withIdRefPrefixObject (cognitive 23) packages/utils/src/withIdRefPrefix.ts:124 — withIdRefPrefix.withIdRefPrefixObject has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, ternaries 2, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · pathUtils.setByPath (cognitive 22) · ×1
  • pathUtils.setByPath (cognitive 22) packages/utils/src/pathUtils.ts:117 — pathUtils.setByPath has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (7 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validationTargets.walkFrom · ×1
  • validationTargets.walkFrom::leave (cognitive 22) packages/utils/src/schema/graph/validationTargets.ts:1754 — validationTargets.walkFrom::leave has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, loops 2 (5 pts), ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getFilledDefault.writtenKeys (cognitive 22) · ×1
  • getFilledDefault.writtenKeys (cognitive 22) packages/utils/src/schema/getFilledDefault.ts:153 — getFilledDefault.writtenKeys has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LayoutGridField.getSchemaDetailsForField (cognitive 21) · ×1
  • LayoutGridField.getSchemaDetailsForField (cognitive 21) REDACTED:476 — LayoutGridField.getSchemaDetailsForField has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 8, ternaries 2 (nesting depth added 4). Of this number, 19 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compileSchemaValidatorsCode.standalone (cognitive 21) · ×1
  • compileSchemaValidatorsCode.standalone (cognitive 21) REDACTED:370 — compileSchemaValidatorsCode.standalone has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8, ternaries 7 (8 pts), boolean chains 4, loops 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (renamed, rewrite, nameOf, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.FieldTemplate (cognitive 20) · ×1
  • index.FieldTemplate (cognitive 20) packages/antd/src/templates/FieldTemplate/index.tsx:26 — index.FieldTemplate has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 8, if/else 2 (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.
D2 · Cognitive Complexity · FallbackField.castToNewType (cognitive 20) · ×1
  • FallbackField.castToNewType (cognitive 20) packages/core/src/components/fields/FallbackField.tsx:425 — FallbackField.castToNewType has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 3 (6 pts), boolean chains 4, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · sanitizeFieldTree.previousKeys (cognitive 20) · ×1
  • sanitizeFieldTree.previousKeys (cognitive 20) packages/core/src/components/sanitizeFieldTree.ts:199 — sanitizeFieldTree.previousKeys has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 1 (3 pts), ternaries 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · formState.settleFormData (cognitive 20) · ×1
  • formState.settleFormData (cognitive 20) packages/core/src/components/formState.ts:1296 — formState.settleFormData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 6, ternaries 5, loops 1 (2 pts) (nesting depth added 5). Of this number, 18 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validationTargets.derive · ×1
  • validationTargets.derive::sub (cognitive 20) packages/utils/src/schema/graph/validationTargets.ts:756 — validationTargets.derive::sub has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (validationTargets.derive) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ArrayField.FixedArray (cognitive 19) · ×1
  • ArrayField.FixedArray (cognitive 19) packages/core/src/components/fields/ArrayField.tsx:1030 — ArrayField.FixedArray has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 4. Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1096, 1068). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · useSendOptionSwitch.useSendOptionSwitch (cognitive 19) · ×1
  • useSendOptionSwitch.useSendOptionSwitch (cognitive 19) packages/core/src/hooks/useSendOptionSwitch.ts:100 — useSendOptionSwitch.useSendOptionSwitch has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, ternaries 5. None of this is in the body itself: all 19 points belong to 6 function literals inside it that branch (lines 104, 129, 136, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · formModel.createFormModel (cognitive 19) · ×1
  • formModel.createFormModel (cognitive 19) packages/core/src/components/formModel.ts:224 — formModel.createFormModel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 875, 857, 915, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · formState.applyChangeToData (cognitive 19) · ×1
  • formState.applyChangeToData (cognitive 19) packages/core/src/components/formState.ts:1768 — formState.applyChangeToData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 1 (3 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validationTargets.withSharedCopies (cognitive 19) · ×1
  • validationTargets.withSharedCopies (cognitive 19) packages/utils/src/schema/graph/validationTargets.ts:916 — validationTargets.withSharedCopies has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 5, if/else 5, loops 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 3 function items inside it that branch (writeKeyword, write, reaches). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · getRenderedOptionSchema.meetSchemas (cognitive 19) · ×1
  • getRenderedOptionSchema.meetSchemas (cognitive 19) packages/utils/src/getRenderedOptionSchema.ts:95 — getRenderedOptionSchema.meetSchemas has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDefaultFormState.nullSourceOf (cognitive 19) · ×1
  • getDefaultFormState.nullSourceOf (cognitive 19) packages/utils/src/schema/getDefaultFormState.ts:364 — getDefaultFormState.nullSourceOf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createCfworkerInstance.indexDependencies (cognitive 19) · ×1
  • createCfworkerInstance.indexDependencies (cognitive 19) REDACTED:70 — createCfworkerInstance.indexDependencies has cognitive complexity 19 (threshold 15). Drivers by points: if/else 2 (6 pts), ternaries 3 (6 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processRawValidationErrors.transformRJSFValidationErrors (cognitive 19) · ×1
  • processRawValidationErrors.transformRJSFValidationErrors (cognitive 19) packages/validator-cfworker/src/processRawValidationErrors.ts:103 — processRawValidationErrors.transformRJSFValidationErrors has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (5 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 113). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · DatePickerTrigger.DatePickerTrigger (cognitive 18) · ×1
  • DatePickerTrigger.DatePickerTrigger (cognitive 18) packages/daisyui/src/widgets/DatePickerTrigger.tsx:69 — DatePickerTrigger.DatePickerTrigger has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 5. Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DemoFrame.AntdPopupPatcher (cognitive 18) · ×1
  • DemoFrame.AntdPopupPatcher (cognitive 18) packages/playground/src/components/DemoFrame.tsx:68 — DemoFrame.AntdPopupPatcher has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 5 function literals inside it that branch (lines 77, 115, 128, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · getClosestMatchingOption.scopeScore (cognitive 18) · ×1
  • getClosestMatchingOption.scopeScore (cognitive 18) packages/utils/src/schema/getClosestMatchingOption.ts:297 — getClosestMatchingOption.scopeScore has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 5). Of this number, 9 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDisplayLabel.getDisplayLabel (cognitive 18) · ×1
  • getDisplayLabel.getDisplayLabel (cognitive 18) packages/utils/src/schema/getDisplayLabel.ts:32 — getDisplayLabel.getDisplayLabel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pickGlobalUiOptions.pickGlobalUiOptions (cognitive 18) · ×1
  • pickGlobalUiOptions.pickGlobalUiOptions (cognitive 18) packages/utils/src/pickGlobalUiOptions.ts:23 — pickGlobalUiOptions.pickGlobalUiOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (6 pts), loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NumberField.NumberField (cognitive 17) · ×1
  • NumberField.NumberField (cognitive 17) packages/core/src/components/fields/NumberField.tsx:26 — NumberField.NumberField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 3 (4 pts) (nesting depth added 3). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Graph.contentKey (cognitive 17) · ×1
  • Graph.contentKey (cognitive 17) packages/utils/src/schema/graph/parseSchemaGraph.ts:391 — Graph.contentKey has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 5 (6 pts), boolean chains 3, loops 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PlanBuilder.mergeSeeds (cognitive 17) · ×1
  • PlanBuilder.mergeSeeds (cognitive 17) packages/utils/src/schema/graph/mergePlan.ts:666 — PlanBuilder.mergeSeeds has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 4 (5 pts), loops 3, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getClosestMatchingOption.propertyScore (cognitive 17) · ×1
  • getClosestMatchingOption.propertyScore (cognitive 17) packages/utils/src/schema/getClosestMatchingOption.ts:138 — getClosestMatchingOption.propertyScore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ObjectFieldTemplate (cognitive 16) · ×1
  • index.ObjectFieldTemplate (cognitive 16) packages/antd/src/templates/ObjectFieldTemplate/index.tsx:34 — index.ObjectFieldTemplate has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (5 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (calculateColSpan). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · formModel.focusForId (cognitive 16) · ×1
  • formModel.focusForId (cognitive 16) packages/core/src/components/formModel.ts:164 — formModel.focusForId has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), ternaries 1 (nesting depth added 1). Of this number, 8 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · sanitizeFieldTree.oldFillOutOf (cognitive 16) · ×1
  • sanitizeFieldTree.oldFillOutOf (cognitive 16) packages/core/src/components/sanitizeFieldTree.ts:693 — sanitizeFieldTree.oldFillOutOf has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 4, boolean chains 3 (nesting depth added 1). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · optionsList.optionsList (cognitive 16) · ×1
  • optionsList.optionsList (cognitive 16) packages/utils/src/optionsList.ts:58 — optionsList.optionsList has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4, ternaries 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 71, a function literal at line 95, readsSelector). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · validationTargets.walkCycles (cognitive 16) · ×1
  • validationTargets.walkCycles (cognitive 16) packages/utils/src/schema/graph/validationTargets.ts:1580 — validationTargets.walkCycles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fieldPath.fieldPathToList (cognitive 16) · ×1
  • fieldPath.fieldPathToList (cognitive 16) packages/utils/src/fieldPath.ts:48 — fieldPath.fieldPathToList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDateTimeLocalValue.getDateTimeLocalValue (cognitive 16) · ×1
  • getDateTimeLocalValue.getDateTimeLocalValue (cognitive 16) packages/utils/src/getDateTimeLocalValue.ts:36 — getDateTimeLocalValue.getDateTimeLocalValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D22 · Internal API Consistency · `SchemaUtilsType.getUiRequiredErrorSchema` types `uiSchema` as `UiSchema<T, S, F> | undefined` where 3 sibling members type it `UiSchema<T, S, F>` · ×1
  • `SchemaUtilsType.getUiRequiredErrorSchema` types `uiSchema` as `UiSchema<T, S, F> | undefined` where 3 sibling members type it `UiSchema<T, S, F>` packages/utils/src/types.ts:2856 — 3 of 4 members of `SchemaUtilsType` that take `uiSchema` type it `UiSchema<T, S, F>` (3 of 4). Siblings: SchemaUtilsType.canExpand (packages/utils/src/types.ts:2668); SchemaUtilsType.getDefaultFormState (packages/utils/src/types.ts:2732); SchemaUtilsType.isFilesArray (packages/utils/src/types.ts:2806). Type `uiSchema` as `UiSchema<T, S, F>`. [rule A8]
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: Graph packages/utils/src/schema/graph/parseSchemaGraph.ts:273 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: .size-limit.js → formDataForNewOption.ts, formState.ts, sanitizeFieldTree.ts .github/size-limit/.size-limit.js — `.github/size-limit/.size-limit.js` changes together with 3 other files — `packages/core/src/components/fields/formDataForNewOption.ts`, `packages/core/src/components/formState.ts`, `packages/core/src/components/sanitizeFieldTree.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to packages/core/src/components/fields/fieldWidgetUtils.ts:445 — The guard above `return uiSchema;` also returns `uiSchema`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
IC1 · Incompleteness & stubs · Hollow method · ×1
  • Hollow method — returns a constant without doing the work packages/playground/src/components/Editors.tsx:52 — `anyJson` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 905 JavaScript/TypeScript production file(s) this check read across 18 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.
R10 · Code Duplication · Duplication concentrated across 15 sibling directories (213 clone groups) · ×1
  • Duplication concentrated across 15 sibling directories (213 clone groups) packages/validator-ajv8/src/processRawValidationErrors.ts:1 — 213 duplicated blocks under packages/ have copies in at least two of the sibling directories antd, bootstrap3, chakra-ui, core, daisyui, fluentui-rc (+9 more sibling(s) not listed) — 157 of them are reported below, and 56 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 213 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 213 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 213 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 13 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 13 sibling directories (9 clone groups) packages/mui/src/CheckboxesWidget/CheckboxesWidget.tsx:27 — 9 duplicated blocks under packages/mui/src/ have copies in at least two of the sibling directories AddButton, ArrayFieldItemTemplate, ArrayFieldTemplate, CheckboxWidget, CheckboxesWidget, ErrorList (+7 more sibling(s) not listed) — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (6 clone groups) packages/chakra-ui/src/BaseInputTemplate/BaseInputTemplate.tsx:22 — 6 duplicated blocks under packages/chakra-ui/src/ have copies in at least two of the sibling directories BaseInputTemplate, CheckboxesWidget, NativeSelectWidget, RadioWidget, RangeWidget, TextareaWidget (+1 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (6 clone groups) packages/core/src/components/templates/index.ts:54 — 6 duplicated blocks under packages/core/src/components/ have copies in at least two of the sibling directories fields, templates, widgets — 2 of them are reported below, and 4 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (5 clone groups) packages/antd/src/widgets/RadioWidget/index.tsx:23 — 5 duplicated blocks under packages/antd/src/widgets/ have copies in at least two of the sibling directories CheckboxesWidget, DateWidget, PasswordWidget, RadioWidget, TextareaWidget — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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 · Wholesale file copy (124 identical lines × 2 files) · ×1
  • Wholesale file copy (124 identical lines × 2 files) packages/validator-ajv8/src/processRawValidationErrors.ts:1 — packages/validator-ajv8/src/processRawValidationErrors.ts:1 · packages/validator-ata/src/processRawValidationErrors.ts:1 — these 2 files are line-for-line copies of one another — 124 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (66 identical lines × 2 files) · ×1
  • Wholesale file copy (66 identical lines × 2 files) packages/validator-ajv8/src/precompiledValidator.ts:1 — packages/validator-ajv8/src/precompiledValidator.ts:1 · packages/validator-ata/src/precompiledValidator.ts:1 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (61 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (61 matched lines × 2 locations) packages/validator-ata/src/validator.ts:168 — packages/validator-ata/src/validator.ts:168 · packages/validator-cfworker/src/validator.ts:147 — the two spans are one implementation copied and then locally edited — 422 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 (54 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (54 matched lines × 2 locations) packages/mui/src/CheckboxesWidget/CheckboxesWidget.tsx:27 — packages/mui/src/CheckboxesWidget/CheckboxesWidget.tsx:27 · packages/mui/src/RadioWidget/RadioWidget.tsx:25 — the two spans are one implementation copied and then locally edited — 317 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 (51 lines × 2 locations) · ×1
  • Duplicated block (51 lines × 2 locations) packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19 — packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19 · packages/react-bootstrap/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (48 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (48 matched lines × 2 locations) packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx:75 — packages/daisyui/src/widgets/DateTimeWidget/DateTimeWidget.tsx:75 · packages/daisyui/src/widgets/DateWidget/DateWidget.tsx:21 — the two spans are one implementation copied and then locally edited — 285 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 (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) packages/chakra-ui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12 — packages/chakra-ui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12 · packages/react-bootstrap/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:12 — 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 (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) packages/core/src/components/widgets/SelectWidget.tsx:64 — packages/core/src/components/widgets/SelectWidget.tsx:64 · packages/react-bootstrap/src/SelectWidget/SelectWidget.tsx:44 — the two spans are one implementation copied and then locally edited — 320 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 (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:18 — packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:18 · packages/mui/src/FieldTemplate/FieldTemplate.tsx:40 — 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 (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) packages/chakra-ui/src/FieldTemplate/FieldTemplate.tsx:60 — packages/chakra-ui/src/FieldTemplate/FieldTemplate.tsx:60 · packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:42 — the two spans are one implementation copied and then locally edited — 226 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) packages/core/src/components/fields/ArrayField.tsx:340 — packages/core/src/components/fields/ArrayField.tsx:340 · packages/core/src/components/fields/ArrayField.tsx:398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (36 lines × 3 locations) · ×1
  • Duplicated block (36 lines × 3 locations) packages/antd/src/templates/index.ts:21 — packages/antd/src/templates/index.ts:21 · packages/mui/src/Templates/Templates.ts:22 · packages/react-bootstrap/src/Templates/Templates.ts:22 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (36 lines × 4 locations) · ×1
  • Duplicated block (36 lines × 4 locations) packages/chakra-ui/src/Templates/Templates.ts:22 — packages/chakra-ui/src/Templates/Templates.ts:22 · packages/fluentui-rc/src/Templates/Templates.ts:22 · packages/mui/src/Templates/Templates.ts:22 · packages/react-bootstrap/src/Templates/Templates.ts:22 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) packages/mantine/src/widgets/PasswordWidget.tsx:29 — packages/mantine/src/widgets/PasswordWidget.tsx:29 · packages/mantine/src/widgets/TextareaWidget.tsx:28 — 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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) packages/bootstrap3/src/OptionalDataControlsTemplate.tsx:15 — packages/bootstrap3/src/OptionalDataControlsTemplate.tsx:15 · packages/core/src/components/templates/OptionalDataControlsTemplate.tsx:14 — 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 (33 lines × 3 locations) · ×1
  • Duplicated block (33 lines × 3 locations) packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22 — packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22 · packages/chakra-ui/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:18 · packages/fluentui-rc/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:50 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) packages/mui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 — packages/mui/src/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 · packages/mui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:24 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (32 lines × 3 locations) · ×1
  • Duplicated block (32 lines × 3 locations) packages/validator-ajv8/src/processRawValidationErrors.ts:180 — packages/validator-ajv8/src/processRawValidationErrors.ts:180 · packages/validator-ata/src/processRawValidationErrors.ts:170 · packages/validator-cfworker/src/processRawValidationErrors.ts:178 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) packages/chakra-ui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13 — packages/chakra-ui/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:13 · packages/fluentui-rc/src/ObjectFieldTemplate/ObjectFieldTemplate.tsx:19 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) packages/daisyui/src/templates/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 — packages/daisyui/src/templates/ArrayFieldTemplate/ArrayFieldTemplate.tsx:26 · packages/mantine/src/templates/ArrayFieldTemplate.tsx:16 — 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 (27 lines × 4 locations) · ×1
  • Duplicated block (27 lines × 4 locations) packages/antd/src/templates/WrapIfAdditionalTemplate/index.tsx:28 — packages/antd/src/templates/WrapIfAdditionalTemplate/index.tsx:28 · packages/bootstrap3/src/WrapIfAdditionalTemplate.tsx:22 · packages/core/src/components/templates/WrapIfAdditionalTemplate.tsx:24 · packages/shadcn/src/WrapIfAdditionalTemplate/WrapIfAdditionalTemplate.tsx:37 — the 4 copies are spread across 4 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 (25 lines × 3 locations) · ×1
  • Duplicated block (25 lines × 3 locations) packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:59 — packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx:59 · packages/mui/src/FieldTemplate/FieldTemplate.tsx:85 · packages/react-bootstrap/src/FieldTemplate/FieldTemplate.tsx:51 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (25 lines × 4 locations) · ×1
  • Duplicated block (25 lines × 4 locations) packages/mantine/src/widgets/ColorWidget.tsx:38 — packages/mantine/src/widgets/ColorWidget.tsx:38 · packages/mantine/src/widgets/DateTime/TimeWidget.tsx:47 · packages/mantine/src/widgets/PasswordWidget.tsx:29 · packages/mantine/src/widgets/TextareaWidget.tsx:28 — the 4 copies are spread across 4 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.
R2 · Cyclomatic Complexity · Complex function walk (cyclomatic 81, cognitive 139) · ×1
  • Complex function walk (cyclomatic 81, cognitive 139) packages/core/src/components/sanitizeFieldTree.ts:828 — walk has cyclomatic complexity 81 and cognitive complexity 139; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function foldView (cyclomatic 68, cognitive 68) · ×1
  • Complex function foldView (cyclomatic 68, cognitive 68) packages/utils/src/schema/getDefaultFormState.ts:967 — foldView has cyclomatic complexity 68 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function useSchemaFieldPlan (cyclomatic 60, cognitive 49) · ×1
  • Complex function useSchemaFieldPlan (cyclomatic 60, cognitive 49) packages/core/src/components/fields/SchemaField.tsx:1265 — useSchemaFieldPlan has cyclomatic complexity 60 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function objectDefaults (cyclomatic 54, cognitive 66) · ×1
  • Complex function objectDefaults (cyclomatic 54, cognitive 66) packages/utils/src/schema/getDefaultFormState.ts:1569 — objectDefaults has cyclomatic complexity 54 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 53, cognitive 66) · ×1
  • Complex function (anonymous) (cyclomatic 53, cognitive 66) packages/utils/src/schema/sanitizeDataForNewSchema.ts:842 — (anonymous) has cyclomatic complexity 53 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function walk (cyclomatic 52, cognitive 53) · ×1
  • Complex function walk (cyclomatic 52, cognitive 53) packages/utils/src/schema/getUiRequiredErrorSchema.ts:244 — walk has cyclomatic complexity 52 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 47, cognitive 81) · ×1
  • Complex function (anonymous) (cyclomatic 47, cognitive 81) packages/utils/src/schema/sanitizeDataForNewSchema.ts:526 — (anonymous) has cyclomatic complexity 47 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getFieldComponent (cyclomatic 45, cognitive 35) · ×1
  • Complex function getFieldComponent (cyclomatic 45, cognitive 35) packages/core/src/components/fields/SchemaField.tsx:682 — getFieldComponent has cyclomatic complexity 45 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function sanitizeWithFills (cyclomatic 44, cognitive 58) · ×1
  • Complex function sanitizeWithFills (cyclomatic 44, cognitive 58) packages/utils/src/schema/sanitizeDataForNewSchema.ts:480 — sanitizeWithFills has cyclomatic complexity 44 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function judge (cyclomatic 44, cognitive 49) · ×1
  • Complex function judge (cyclomatic 44, cognitive 49) packages/core/src/components/sanitizeFieldTree.ts:405 — judge has cyclomatic complexity 44 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function omit (cyclomatic 42, cognitive 53) · ×1
  • Complex function omit (cyclomatic 42, cognitive 53) packages/utils/src/schema/omitExtraData.ts:543 — omit has cyclomatic complexity 42 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function SchemaFieldRender (cyclomatic 39, cognitive 36) · ×1
  • Complex function SchemaFieldRender (cyclomatic 39, cognitive 36) packages/core/src/components/fields/SchemaField.tsx:1573 — SchemaFieldRender has cyclomatic complexity 39 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildView (cyclomatic 35, cognitive 36) · ×1
  • Complex function buildView (cyclomatic 35, cognitive 36) packages/utils/src/schema/retrieveSchema.ts:715 — buildView has cyclomatic complexity 35 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AnyOfField (cyclomatic 35, cognitive 35) · ×1
  • Complex function AnyOfField (cyclomatic 35, cognitive 35) packages/core/src/components/fields/MultiSchemaField.tsx:60 — AnyOfField has cyclomatic complexity 35 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveFieldPresentation (cyclomatic 34, cognitive 37) · ×1
  • Complex function resolveFieldPresentation (cyclomatic 34, cognitive 37) packages/utils/src/resolveFieldPresentation.ts:165 — resolveFieldPresentation has cyclomatic complexity 34 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function shareUnchanged (cyclomatic 32, cognitive 44) · ×1
  • Complex function shareUnchanged (cyclomatic 32, cognitive 44) packages/utils/src/replaceEqualDeep.ts:55 — shareUnchanged has cyclomatic complexity 32 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function arrayDefaults (cyclomatic 31, cognitive 38) · ×1
  • Complex function arrayDefaults (cyclomatic 31, cognitive 38) packages/utils/src/schema/getDefaultFormState.ts:1971 — arrayDefaults has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function renderOption (cyclomatic 30, cognitive 44) · ×1
  • Complex function renderOption (cyclomatic 30, cognitive 44) packages/utils/src/getRenderedOptionSchema.ts:289 — renderOption has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getInputProps (cyclomatic 30, cognitive 34) · ×1
  • Complex function getInputProps (cyclomatic 30, cognitive 34) packages/utils/src/getInputProps.ts:56 — getInputProps has cyclomatic complexity 30 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function BaseInputTemplate (cyclomatic 29, cognitive 25) · ×1
  • Complex function BaseInputTemplate (cyclomatic 29, cognitive 25) packages/mantine/src/templates/BaseInputTemplate.tsx:34 — BaseInputTemplate has cyclomatic complexity 29 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.
R2 · Cyclomatic Complexity · Complex function ArrayFieldItemInner (cyclomatic 28, cognitive 23) · ×1
  • Complex function ArrayFieldItemInner (cyclomatic 28, cognitive 23) packages/core/src/components/fields/ArrayField.tsx:656 — ArrayFieldItemInner has cyclomatic complexity 28 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 28, cognitive 23) · ×1
  • Complex function (anonymous) (cyclomatic 28, cognitive 23) packages/shadcn/src/components/ui/fancy-select.tsx:350 — (anonymous) has cyclomatic complexity 28 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.
R2 · Cyclomatic Complexity · Complex function formDataMatching (cyclomatic 26, cognitive 37) · ×1
  • Complex function formDataMatching (cyclomatic 26, cognitive 37) packages/utils/src/schema/getDefaultFormState.ts:2441 — formDataMatching has cyclomatic complexity 26 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function meetKeyword (cyclomatic 26, cognitive 32) · ×1
  • Complex function meetKeyword (cyclomatic 26, cognitive 32) packages/utils/src/getRenderedOptionSchema.ts:146 — meetKeyword has cyclomatic complexity 26 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function BaseInputTemplate (cyclomatic 26, cognitive 22) · ×1
  • Complex function BaseInputTemplate (cyclomatic 26, cognitive 22) packages/antd/src/templates/BaseInputTemplate/index.tsx:28 — BaseInputTemplate has cyclomatic complexity 26 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 26) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 26) packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:250 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function check (cyclomatic 24, cognitive 21) · ×1
  • Complex function check (cyclomatic 24, cognitive 21) packages/utils/test/schema/graph/miniValidator.ts:44 — check has cyclomatic complexity 24 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 16) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 16) packages/core/src/components/sanitizeFieldTree.ts:1120 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveUiSchema (cyclomatic 23, cognitive 42) · ×1
  • Complex function resolveUiSchema (cyclomatic 23, cognitive 42) packages/utils/src/resolveUiSchema.ts:44 — resolveUiSchema has cyclomatic complexity 23 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function warnOfUnshownOptionLabels (cyclomatic 23, cognitive 29) · ×1
  • Complex function warnOfUnshownOptionLabels (cyclomatic 23, cognitive 29) packages/core/src/components/fields/SchemaField.tsx:229 — warnOfUnshownOptionLabels has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function castToNewType (cyclomatic 23, cognitive 23) · ×1
  • Complex function castToNewType (cyclomatic 23, cognitive 23) packages/core/src/components/fields/FallbackField.tsx:425 — castToNewType has cyclomatic complexity 23 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 22) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 22) packages/core/src/components/formModel.ts:653 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function derive (cyclomatic 22, cognitive 25) · ×1
  • Complex function derive (cyclomatic 22, cognitive 25) packages/utils/src/schema/graph/validationTargets.ts:724 — derive has cyclomatic complexity 22 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function FieldTemplate (cyclomatic 22, cognitive 21) · ×1
  • Complex function FieldTemplate (cyclomatic 22, cognitive 21) packages/antd/src/templates/FieldTemplate/index.tsx:26 — FieldTemplate has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function applyChangeToData (cyclomatic 21, cognitive 27) · ×1
  • Complex function applyChangeToData (cyclomatic 21, cognitive 27) packages/core/src/components/formState.ts:1768 — applyChangeToData has cyclomatic complexity 21 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function settleFormData (cyclomatic 21, cognitive 23) · ×1
  • Complex function settleFormData (cyclomatic 21, cognitive 23) packages/core/src/components/formState.ts:1296 — settleFormData has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getGroupAttributes (cyclomatic 21, cognitive 18) · ×1
  • Complex function getGroupAttributes (cyclomatic 21, cognitive 18) packages/utils/src/getGroupAttributes.ts:42 — getGroupAttributes has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function formDataForNewOption (cyclomatic 20, cognitive 30) · ×1
  • Complex function formDataForNewOption (cyclomatic 20, cognitive 30) packages/core/src/components/fields/formDataForNewOption.ts:353 — formDataForNewOption has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function compileSchemaValidatorsCode (cyclomatic 20, cognitive 27) · ×1
  • Complex function compileSchemaValidatorsCode (cyclomatic 20, cognitive 27) REDACTED:567 — compileSchemaValidatorsCode has cyclomatic complexity 20 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function foldOption (cyclomatic 20, cognitive 22) · ×1
  • Complex function foldOption (cyclomatic 20, cognitive 22) packages/utils/src/schema/getDefaultFormState.ts:1342 — foldOption has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/utils/src/types.ts · ×1
  • packages/utils/src/types.ts: 2730 lines of code packages/utils/src/types.ts:1 — packages/utils/src/types.ts has 2730 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/utils/src/schema/getDefaultFormState.ts · ×1
  • packages/utils/src/schema/getDefaultFormState.ts: 2513 lines of code packages/utils/src/schema/getDefaultFormState.ts:1 — packages/utils/src/schema/getDefaultFormState.ts has 2513 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/formState.ts · ×1
  • packages/core/src/components/formState.ts: 2087 lines of code packages/core/src/components/formState.ts:1 — packages/core/src/components/formState.ts has 2087 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/fields/SchemaField.tsx · ×1
  • packages/core/src/components/fields/SchemaField.tsx: 1926 lines of code packages/core/src/components/fields/SchemaField.tsx:1 — packages/core/src/components/fields/SchemaField.tsx has 1926 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/utils/src/schema/graph/validationTargets.ts · ×1
  • packages/utils/src/schema/graph/validationTargets.ts: 1849 lines of code packages/utils/src/schema/graph/validationTargets.ts:1 — packages/utils/src/schema/graph/validationTargets.ts has 1849 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/snapshot-tests/src/formTests.tsx · ×1
  • packages/snapshot-tests/src/formTests.tsx: 1542 lines of code packages/snapshot-tests/src/formTests.tsx:1 — packages/snapshot-tests/src/formTests.tsx has 1542 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/fields/ArrayField.tsx · ×1
  • packages/core/src/components/fields/ArrayField.tsx: 1473 lines of code packages/core/src/components/fields/ArrayField.tsx:1 — packages/core/src/components/fields/ArrayField.tsx has 1473 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/sanitizeFieldTree.ts · ×1
  • packages/core/src/components/sanitizeFieldTree.ts: 1357 lines of code packages/core/src/components/sanitizeFieldTree.ts:1 — packages/core/src/components/sanitizeFieldTree.ts has 1357 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 · REDACTED · ×1
  • REDACTED: 1328 lines of code REDACTED:1 — REDACTED has 1328 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/utils/src/schema/retrieveSchema.ts · ×1
  • packages/utils/src/schema/retrieveSchema.ts: 1175 lines of code packages/utils/src/schema/retrieveSchema.ts:1 — packages/utils/src/schema/retrieveSchema.ts has 1175 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/utils/src/schema/graph/mergePlan.ts · ×1
  • packages/utils/src/schema/graph/mergePlan.ts: 1121 lines of code packages/utils/src/schema/graph/mergePlan.ts:1 — packages/utils/src/schema/graph/mergePlan.ts has 1121 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/formModel.ts · ×1
  • packages/core/src/components/formModel.ts: 1118 lines of code packages/core/src/components/formModel.ts:1 — packages/core/src/components/formModel.ts has 1118 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/mantine/src/utils.tsx · ×1
  • packages/mantine/src/utils.tsx: 1058 lines of code packages/mantine/src/utils.tsx:1 — packages/mantine/src/utils.tsx has 1058 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/fields/ObjectField.tsx · ×1
  • packages/core/src/components/fields/ObjectField.tsx: 1048 lines of code packages/core/src/components/fields/ObjectField.tsx:1 — packages/core/src/components/fields/ObjectField.tsx has 1048 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/utils/src/schema/sanitizeDataForNewSchema.ts · ×1
  • packages/utils/src/schema/sanitizeDataForNewSchema.ts: 973 lines of code packages/utils/src/schema/sanitizeDataForNewSchema.ts:1 — packages/utils/src/schema/sanitizeDataForNewSchema.ts has 973 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/utils/src/schema/graph/parseSchemaGraph.ts · ×1
  • packages/utils/src/schema/graph/parseSchemaGraph.ts: 782 lines of code packages/utils/src/schema/graph/parseSchemaGraph.ts:1 — packages/utils/src/schema/graph/parseSchemaGraph.ts has 782 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/daisyui/src/widgets/datePickerHooks.ts · ×1
  • packages/daisyui/src/widgets/datePickerHooks.ts: 723 lines of code packages/daisyui/src/widgets/datePickerHooks.ts:1 — packages/daisyui/src/widgets/datePickerHooks.ts has 723 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/fields/FallbackField.tsx · ×1
  • packages/core/src/components/fields/FallbackField.tsx: 686 lines of code packages/core/src/components/fields/FallbackField.tsx:1 — packages/core/src/components/fields/FallbackField.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 · REDACTED · ×1
  • REDACTED: 686 lines of code REDACTED:1 — REDACTED 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/utils/src/schema/getClosestMatchingOption.ts · ×1
  • packages/utils/src/schema/getClosestMatchingOption.ts: 657 lines of code packages/utils/src/schema/getClosestMatchingOption.ts:1 — packages/utils/src/schema/getClosestMatchingOption.ts has 657 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/uiState.ts · ×1
  • packages/core/src/components/uiState.ts: 650 lines of code packages/core/src/components/uiState.ts:1 — packages/core/src/components/uiState.ts has 650 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/fields/fieldWidgetUtils.ts · ×1
  • packages/core/src/components/fields/fieldWidgetUtils.ts: 639 lines of code packages/core/src/components/fields/fieldWidgetUtils.ts:1 — packages/core/src/components/fields/fieldWidgetUtils.ts has 639 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/Form.tsx · ×1
  • packages/core/src/components/Form.tsx: 638 lines of code packages/core/src/components/Form.tsx:1 — packages/core/src/components/Form.tsx has 638 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/utils/src/schema/omitExtraData.ts · ×1
  • packages/utils/src/schema/omitExtraData.ts: 638 lines of code packages/utils/src/schema/omitExtraData.ts:1 — packages/utils/src/schema/omitExtraData.ts has 638 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/snapshot-tests/src/arrayTests.tsx · ×1
  • packages/snapshot-tests/src/arrayTests.tsx: 579 lines of code packages/snapshot-tests/src/arrayTests.tsx:1 — packages/snapshot-tests/src/arrayTests.tsx has 579 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/fields/formDataForNewOption.ts · ×1
  • packages/core/src/components/fields/formDataForNewOption.ts: 543 lines of code packages/core/src/components/fields/formDataForNewOption.ts:1 — packages/core/src/components/fields/formDataForNewOption.ts has 543 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/snapshot-tests/src/gridTests.tsx · ×1
  • packages/snapshot-tests/src/gridTests.tsx: 530 lines of code packages/snapshot-tests/src/gridTests.tsx:1 — packages/snapshot-tests/src/gridTests.tsx has 530 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/utils/src/schema/getUiRequiredErrorSchema.ts · ×1
  • packages/utils/src/schema/getUiRequiredErrorSchema.ts: 528 lines of code packages/utils/src/schema/getUiRequiredErrorSchema.ts:1 — packages/utils/src/schema/getUiRequiredErrorSchema.ts has 528 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/fields/useSchemaFieldPresentation.ts · ×1
  • packages/core/src/components/fields/useSchemaFieldPresentation.ts: 513 lines of code packages/core/src/components/fields/useSchemaFieldPresentation.ts:1 — packages/core/src/components/fields/useSchemaFieldPresentation.ts has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/snapshot-tests/src/objectTests.tsx · ×1
  • packages/snapshot-tests/src/objectTests.tsx: 496 lines of code packages/snapshot-tests/src/objectTests.tsx:1 — packages/snapshot-tests/src/objectTests.tsx has 496 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/daisyui/src/widgets/SelectWidget/SelectWidget.tsx · ×1
  • packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx: 475 lines of code packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx:1 — packages/daisyui/src/widgets/SelectWidget/SelectWidget.tsx has 475 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/utils/src/createSchemaUtils.ts · ×1
  • packages/utils/src/createSchemaUtils.ts: 457 lines of code packages/utils/src/createSchemaUtils.ts:1 — packages/utils/src/createSchemaUtils.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/utils/src/getWidget.tsx · ×1
  • packages/utils/src/getWidget.tsx: 424 lines of code packages/utils/src/getWidget.tsx:1 — packages/utils/src/getWidget.tsx has 424 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/shadcn/src/components/ui/fancy-select.tsx · ×1
  • packages/shadcn/src/components/ui/fancy-select.tsx: 407 lines of code packages/shadcn/src/components/ui/fancy-select.tsx:1 — packages/shadcn/src/components/ui/fancy-select.tsx has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~14 LoC) · ×1
  • Dead file (~14 LoC) scripts/get-version-tag.cjs — no import path from any entry point (100 application, 40 tooling, 599 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
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) packages/daisyui/src/theme/storedTheme.ts:32 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Minor — 75 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×26
  • Duplicated predicate packages/antd/src/widgets/SelectWidget/index.tsx:87 — `!multiple && schema.default === undefined` appears character-identically in 5 files — packages/antd/src/widgets/SelectWidget/index.tsx, packages/chakra-ui/src/NativeSelectWidget/NativeSelectWidget.tsx, packages/core/src/components/widgets/SelectWidget.tsx, packages/fluentui-rc/src/SelectWidget/SelectWidget.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/templates/BaseInputTemplate/index.tsx:80 — `!plainInput && (inputProps.type === 'number' || inputProps.type === 'integer')` appears character-identically in 2 files — packages/antd/src/templates/BaseInputTemplate/index.tsx, packages/mantine/src/templates/BaseInputTemplate.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/templates/FieldTemplate/index.tsx:67 — `!presentation && uiOptions.widget === 'checkbox'` appears character-identically in 5 files — packages/antd/src/templates/FieldTemplate/index.tsx, packages/core/src/components/templates/FieldTemplate/FieldTemplate.tsx, packages/fluentui-rc/src/FieldTemplate/FieldTemplate.tsx, packages/mui/src/FieldTemplate/FieldTemplate.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/templates/ObjectFieldTemplate/index.tsx:110 — `!showOptionalDataControlInTitle && optionalDataControl` appears character-identically in 2 files — packages/antd/src/templates/ObjectFieldTemplate/index.tsx, packages/chakra-ui/src/ObjectFieldTemplate/ObjectFieldTemplate.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/widgets/CheckboxWidget/index.tsx:64 — `(marksRequired && !trueValueRequired) || undefined` appears character-identically in 7 files — packages/antd/src/widgets/CheckboxWidget/index.tsx, packages/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx, packages/core/src/components/widgets/CheckboxWidget.tsx, packages/fluentui-rc/src/CheckboxWidget/CheckboxWidget.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/core/src/components/sanitizeFieldTree.ts:353 — `Array.isArray(enumValues) && enumValues.length > 0` appears character-identically in 2 files — packages/core/src/components/sanitizeFieldTree.ts, packages/utils/src/getSchemaOwnTypes.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/utils/src/isWholeValueSelect.ts:27 — `Array.isArray(schema.enum) && schema.enum.length > 0` appears character-identically in 2 files — packages/utils/src/isWholeValueSelect.ts, packages/utils/src/schema/sanitizeDataForNewSchema.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/antd/src/widgets/CheckboxesWidget/index.tsx:81 — `control.disabled || enumOptionsIsDisabled(option.value, enumDisabled) || undefined` appears character-identically in 2 files — packages/antd/src/widgets/CheckboxesWidget/index.tsx, packages/antd/src/widgets/RadioWidget/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/shadcn/src/components/ui/fancy-multi-select.tsx:289 — `disabled && 'opacity-50 cursor-not-allowed'` appears character-identically in 2 files — packages/shadcn/src/components/ui/fancy-multi-select.tsx, packages/shadcn/src/components/ui/fancy-select.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/validator-ajv8/src/processRawValidationErrors.ts:59 — `e.message === message && e.schemaPath?.startsWith(schemaPrefix)` appears character-identically in 2 files — packages/validator-ajv8/src/processRawValidationErrors.ts, packages/validator-ata/src/processRawValidationErrors.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/mantine/src/widgets/CheckboxesWidget.tsx:83 — `fieldDisabled || enumOptionsIsDisabled(option.value, enumDisabled)` appears character-identically in 2 files — packages/mantine/src/widgets/CheckboxesWidget.tsx, packages/mantine/src/widgets/RadioWidget.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/core/src/components/formState.ts:1795 — `isObject(formData) || Array.isArray(formData)` appears character-identically in 2 files — packages/core/src/components/formState.ts, packages/utils/src/schema/getDefaultFormState.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/utils/src/schema/resolveConstantOptions.ts:25 — `isSchemaObject<S>(option) && typeof option[REF_KEY] === 'string'` appears character-identically in 2 files — packages/utils/src/schema/resolveConstantOptions.ts, packages/utils/src/schema/retrieveSchema.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/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx:94 — `marksRequired && templateMarksRequired<T` appears character-identically in 4 files — packages/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx, packages/fluentui-rc/src/CheckboxWidget/CheckboxWidget.tsx, packages/mantine/src/widgets/CheckboxWidget.tsx, packages/mui/src/CheckboxWidget/CheckboxWidget.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/utils/src/schema/graph/mergePlan.ts:499 — `node.kind === 'schema' && node.ref !== undefined` appears character-identically in 3 files — packages/utils/src/schema/graph/mergePlan.ts, packages/utils/src/schema/graph/validationTargets.ts, packages/utils/src/schema/retrieveSchema.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/mantine/src/utils.tsx:664 — `presentation && isLabelledByTemplate(presentation)` appears character-identically in 2 files — packages/mantine/src/utils.tsx, packages/utils/src/listboxAriaProps.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/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx:48 — `presentation || getUiOptions(uiSchema).widget !== 'checkbox'` appears character-identically in 3 files — packages/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx, packages/core/src/components/widgets/CheckboxWidget.tsx, packages/shadcn/src/CheckboxWidget/CheckboxWidget.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/widgets/CheckboxWidget/index.tsx:37 — `schemaRequiresTrueValue(schema) && required` appears character-identically in 5 files — packages/antd/src/widgets/CheckboxWidget/index.tsx, packages/chakra-ui/src/CheckboxWidget/CheckboxWidget.tsx, packages/daisyui/src/widgets/BooleanInput.tsx, packages/fluentui-rc/src/CheckboxWidget/CheckboxWidget.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/core/src/components/widgets/CheckboxWidget.tsx:52 — `schemaRequiresTrueValue<S>(schema) && required` appears character-identically in 4 files — packages/core/src/components/widgets/CheckboxWidget.tsx, packages/mui/src/CheckboxWidget/CheckboxWidget.tsx, packages/react-bootstrap/src/CheckboxWidget/CheckboxWidget.tsx, packages/shadcn/src/CheckboxWidget/CheckboxWidget.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/validator-ata/src/validator.ts:241 — `this.lastSeenRootSchema === rootSchema && this.hasRegisteredRootSchema` appears character-identically in 2 files — packages/validator-ata/src/validator.ts, packages/validator-cfworker/src/validator.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/validator-ajv8/src/precompiledValidator.ts:40 — `typeof containedId === 'string' && containedId !== ''` appears character-identically in 2 files — packages/validator-ajv8/src/precompiledValidator.ts, packages/validator-ata/src/precompiledValidator.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/core/src/components/formModel.ts:279 — `typeof data === 'object' && data !== null` appears character-identically in 4 files — packages/core/src/components/formModel.ts, packages/utils/src/schema/getClosestMatchingOption.ts, packages/utils/src/schema/graph/mergePlan.ts, packages/validator-ajv8/src/dataForValidation.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/fluentui-rc/src/TextareaWidget/TextareaWidget.tsx:60 — `typeof options.rows === 'string' || typeof options.rows === 'number'` appears character-identically in 2 files — packages/fluentui-rc/src/TextareaWidget/TextareaWidget.tsx, packages/mui/src/TextareaWidget/TextareaWidget.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/utils/src/isObject.ts:10 — `typeof thing !== 'object' || thing === null` appears character-identically in 2 files — packages/utils/src/isObject.ts, packages/utils/src/isPlainObject.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/utils/src/schema/graph/parseSchemaGraph.ts:392 — `typeof value !== 'object' || value === null` appears character-identically in 2 files — packages/utils/src/schema/graph/parseSchemaGraph.ts, packages/utils/src/schema/graph/provenance.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.
  • + 1 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×18
  • redundant comment packages/core/src/components/fields/ArrayField.tsx:1107 — "For additional items, use additionalItems uiSchema" repeats the code it sits on: 4 of its 5 words (additional, items, ui, schema) are already in `itemUiSchema = uiSchema.additionalItems as UiSchema<T[], S, F>;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:540 — "When we have both a schema and a leafPath..." repeats the code it sits on: 3 of its 3 words (schema, leaf, path) are already in `schema = holding(schema, leafPath, innerData, fieldPath);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:831 — "Keyed as `LayoutGridFieldChildren` keys a cell" repeats the code it sits on: 6 of its 7 words (keyed, layout, grid, field, children, keys) are already in `return children.map((child, i) => (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core/test/Form.rendering.test.tsx:204 — "click the add button" repeats the code it sits on: 3 of its 3 words (click, add, button) are already in `await user.click(addButton!);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core/test/Form.rendering.test.tsx:217 — "click the add button" repeats the code it sits on: 3 of its 3 words (click, add, button) are already in `await user.click(addButton!);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core/test/StringField.test.tsx:3169 — "Click the delete button" repeats the code it sits on: 3 of its 3 words (click, delete, button) are already in `await user.click(deleteButton!);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/mui/test/MuiProps.test.tsx:316 — "A select takes its slots from `rjsfSlotProps`, a text input from `slotProps`" repeats the code it sits on: 7 of its 8 words (select, slots, rjsf, slot, props, text, input) are already in `it.each<[string, RJSFSchema, string, string]>([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/src/dataURItoBlob.ts:8 — "check if is dataURI" repeats the code it sits on: 3 of its 3 words (check, data, uri) are already in `if (!dataURILike.includes('data:'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/src/mergeDefaultsWithFormData.ts:62 — "Merge any extra defaults when mergeExtraArrayDefaults is true Or when overrideFormDataWithDefaults is true and the default array is shorter than the formData ar …" repeats the code it sits on: 8 of its 10 words (merge, extra, defaults, array, override, form, data, default) are already in `if ((mergeExtraArrayDefaults || overrideFormDataWithDefaults) && mapped.length < overrideOppositeArray.length)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/src/schema/getDefaultFormState.ts:1128 — "if shouldMergeDefaultsIntoFormData is true, then merge the defaults into the formData." repeats the code it sits on: 5 of its 6 words (should, merge, defaults, form, data) are already in `if (shouldMergeDefaultsIntoFormData)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/src/schema/sanitizeDataForNewSchema.ts:585 — "Check if the old option has the same key with the same type" repeats the code it sits on: 4 of its 5 words (check, old, key, type) are already in `if (!oldSchemaTypeForKey || isSameType(oldSchemaTypeForKey, newSchemaTypeForKey))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/test/schema/getDefaultFormStateTest.ts:1338 — "Reset the testValidator" repeats the code it sits on: 3 of its 3 words (reset, test, validator) are already in `if (typeof testValidator.reset === 'function')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/test/schema/getDefaultFormStateTest.ts:2014 — "Reset the testValidator" repeats the code it sits on: 3 of its 3 words (reset, test, validator) are already in `if (typeof testValidator.reset === 'function')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/test/schema/getDefaultFormStateTest.ts:7471 — "Reset the testValidator" repeats the code it sits on: 3 of its 3 words (reset, test, validator) are already in `if (typeof testValidator.reset === 'function')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/utils/test/schema/getDefaultFormStateTest.ts:7779 — "Reset the testValidator" repeats the code it sits on: 3 of its 3 words (reset, test, validator) are already in `if (typeof testValidator.reset === 'function')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/validator-ajv8/test/validator.test.ts:708 — "Call validateFormData twice with the same schema" repeats the code it sits on: 5 of its 6 words (call, validate, form, data, schema) are already in `validator.validateFormData({ string: 'a' }, schema);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/validator-ajv8/test/validator.test.ts:1231 — "Call validateFormData twice with the same schema" repeats the code it sits on: 5 of its 6 words (call, validate, form, data, schema) are already in `validator.validateFormData({ string: 'a' }, schema);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/validator-ajv8/test/validator.test.ts:2419 — "Call validateFormData twice with the same schema" repeats the code it sits on: 5 of its 6 words (call, validate, form, data, schema) are already in `validator.validateFormData({ string: 'a' }, schema);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D10 · Test Quality · Mock-dominated test · ×5
  • Mock-dominated test: takes no focus, and so reports no blur, on a click on a selected item of a readonly select packages/shadcn/test/SelectWidget.test.tsx:2213 — This test sets up 3 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: PasswordWidget keeps the form's handlers when ui:options gives its own packages/mantine/test/Form.test.tsx:924 — 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: RangeWidget keeps the form's handlers when ui:options gives its own packages/mantine/test/Form.test.tsx:950 — 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: Done on a field holding a cleared one's "" reports the blur and focus with the empty value stored packages/daisyui/test/DatePicker.closeBlur.test.tsx:589 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: a blur and a focus a widget reports from its Effect cleanup as the form unmounts are dropped packages/core/test/Form.store.test.tsx:372 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion packages/utils/package.json:1 — `packages/utils` (25425 LoC, 307 module-visible types across 4 directories) overshoots its size bounds. 2 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 7.6/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/core/package.json:1 — `packages/core` (20472 LoC, 149 module-visible types across 8 directories) overshoots its size bounds. 2 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 7.6/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
IC1 · Incompleteness & stubs · Disabled test · ×2
  • Disabled test packages/daisyui/test/RatingWidget.test.tsx:243 — 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/mantine/test/AriaLabelledBy.test.tsx:1122 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: SchemaUtilsType (23 required operations) packages/utils/src/types.ts:2624 — `SchemaUtilsType` declares 23 required operations: `getRootSchema`, `getValidator`, `doesSchemaUtilsDiffer`, `allowsAdditionalProperties`, `canExpand`, `constrainsAlike`, `findFieldInSchema`, `findSelectedOptionInXxxOf`, `getDefaultFormState`, `getDisplayLabel`, `getFilledDefault`, `getClosestMatchingOption`, `getFirstMatchingOption`, `getFromSchema`, `getFromSchema`, `getFromSchema`, `isFilesArray`, `isMultiSelect`, `isSelect`, `omitExtraData`, `retrieveSchema`, `getUiRequiredErrorSchema`, `sanitizeDataForNewSchema`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: packages/daisyui/src/widgets/BooleanInput.tsx, packages/chakra-ui/src/components/ui/field.tsx, packages/chakra-ui/src/components/ui/slider.tsx, packages/utils/src/getItemUiSchemaForItem.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 (7 single-owned of 289 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; 289 of the 865 production source files in this repository met that bar). They are anonymized user #2 (2 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/core/src/components/IChangeEvent.ts, packages/core/src/components/FormRef.ts, packages/utils/src/utcToLocal.ts.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example README.md:1 — the repository is runnable (a `start` script in `package.json`) and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found package.json:19 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `package.json` makes this repository a deployable product (line 19).
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 289 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 289 of the 865 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/mantine/src/templates/icons.tsx. 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.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file packages/mantine/src/templates/icons.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift packages/docs/versioned_docs/version-5.24.10/usage/validation.md:624 — packages/docs/versioned_docs/version-5.24.10/usage/validation.md names Ajv 6, but the manifest declares `ajv` ^8.20.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
R7 · Dead Code · Unused export 'SelectContent' · ×1
  • Unused export 'SelectContent' packages/chakra-ui/src/components/ui/select.tsx:84 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SelectItem' · ×1
  • Unused export 'SelectItem' packages/chakra-ui/src/components/ui/select.tsx:100 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SelectItemGroup' · ×1
  • Unused export 'SelectItemGroup' packages/chakra-ui/src/components/ui/select.tsx:186 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SelectLabel' · ×1
  • Unused export 'SelectLabel' packages/chakra-ui/src/components/ui/select.tsx:193 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SelectItemText' · ×1
  • Unused export 'SelectItemText' packages/chakra-ui/src/components/ui/select.tsx:194 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'TextareaProps' · ×1
  • Unused export 'TextareaProps' packages/shadcn/src/components/ui/textarea.tsx:9 — Nothing imports this binding — it is safe to review for removal.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected netlify.toml:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 4/5 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.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.1 `!` null assertions per 1k TypeScript source lines — 6 assertion(s) across the 79291 source line(s) of the 840 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/core/src/components/fields/layoutMultiSchemaFieldSelector.ts (1), packages/playground/src/index.tsx (1), packages/utils/src/createErrorHandler.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch packages/utils/src/schema/graph/validationTargets.ts:1080 — `compiledPattern` 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.
Minor — 9 finding(s)
D24 · Comment Value · doc comments repeat the names · ×8
  • doc comments repeat the names packages/antd/src/templates/headingLabelColClassName.ts:27 — 1 of 32 documented parameters and 0 of 60 summaries in `@rjsf/antd` only repeat the member or parameter name (e.g. "The `formContext` of the form" for `formContext`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/core/src/components/IChangeEvent.ts:43 — 40 of 644 documented parameters and 6 of 1029 summaries in `@rjsf/core` only repeat the member or parameter name (e.g. "An object of `NestedBooleanValue`s" for `NestedBooleanObject`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/daisyui/src/theme/storedTheme.ts:12 — 2 of 73 documented parameters and 1 of 164 summaries in `@rjsf/daisyui` only repeat the member or parameter name (e.g. "Reads the stored theme" for `readStoredTheme`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/mantine/src/utils.tsx:228 — 2 of 68 documented parameters and 0 of 101 summaries in `@rjsf/mantine` only repeat the member or parameter name (e.g. "The part" for `part`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/shadcn/src/components/ui/fancy-select.tsx:89 — 1 of 117 documented parameters and 0 of 125 summaries in `@rjsf/shadcn` only repeat the member or parameter name (e.g. "The item" for `item`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/utils/src/fieldPath.ts:164 — 36 of 1169 documented parameters and 5 of 1868 summaries in `@rjsf/utils` only repeat the member or parameter name (e.g. "The `FieldPath` of the field" for `fieldPath`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/validator-ajv8/src/ajvRootSchemaId.ts:11 — 1 of 80 documented parameters and 0 of 85 summaries in `@rjsf/validator-ajv8` only repeat the member or parameter name (e.g. "The root schema" for `rootSchema`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/validator-ata/test/utilsTests/getTestValidator.ts:11 — 0 of 41 documented parameters and 0 of 100 summaries in `@rjsf/validator-ata` only repeat the member or parameter name (e.g. "" for `options`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
D10 · Test Quality · Skipped (documented) · ×1
  • Skipped (documented): (unnamed test) packages/utils/test/testUtils/nestedResourceTests.ts:164 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-dbb03e108efb4a96a57933430923a730/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-dbb03e108efb4a96a57933430923a730/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1751" --report-format json --report-path /tmp/watchdog-gitleaks-dbb03e108efb4a96a57933430923a730/history-2.json --exit-code 0 --source .1artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dbb03e108efb4a96a57933430923a730/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .47artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 19 file(s) — `packages/antd/src/globalUiOptions.ts`, `packages/chakra-ui/src/utils.ts`, `packages/core/src/components/fields/ObjectField.tsx`, `packages/core/src/components/fields/SchemaField.tsx`, `packages/daisyui/src/utils.ts`, … (+14 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e7b3-405e-77ac-a17d-863c5cf75997 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md