Public report of shadcn-ui/ui, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 12:04 UTC · Survey ID cd_2543f395ef28475e85a616ad61d79940
shadcn-ui/ui
Measured 26 October 2026, 11:42 UTC, at code version 8f04138
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt riskDown 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 416,632 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 3.0 person-years · Weakest lens: Production Readiness, 39
Findings by how serious they are
139 critical850 serious201 minor
9 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 11:42 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
82of 82 dimensions measured by tools.
1064of 1190 findings point to an exact file and line, so you can open each one in the code. The other 126 concern the repository as a whole, such as missing documentation.
82dimensions across 7 lenses, read from 416,632 lines of product code in 6 projects.
shadcn-ui/ui is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 45 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step is updating the outdated dependencies, worth about 4 points. Tidying the declared packages would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 50.
Sixty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Forty known security holes in the packages the code depends on can be used by attackers, and six weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the five automatic dependency updates that take new releases at once, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The nine images with no text description need a text description.
The product code is 416,632 lines, about €430,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 45 to about 50.
Code composition: what the lines of code are
Product code 85%Tests 15%
New since the last survey: 148 findings
These 148 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Incompleteness & stubs · Guard cannot change the result — returns what the code already falls through to apps/v4/components/message-parts.tsx
Incompleteness & stubs · Guard cannot change the result — returns what the code already falls through to packages/registry/src/registry/resolve-file-imports.ts
Visual & motion safety · Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 2453 findings
These 2453 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€140,000 to €720,000, for 2,394 to 7,594 hours of work, about 3.0 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 416,632 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 4 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (4).
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €430,000 to build again, about 3.0 person-years of work. Its weakest lens is Production Readiness, at 39 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 4 Outdated (npm) finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 4 Dependency Hygiene 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 5.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 140,056 lines over the last 90 days, which is about 568,005 lines a year. At that pace, the extra work comes to an estimated 91.2 to 547.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
423 modules, with 50 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 383 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.
apps.v4.app.(app).(create).components uses apps.v4.app.(app).(create).components.menu-picker, so a change to apps.v4.app.(app).(create).components.menu-picker can break apps.v4.app.(app).(create).components, while a change to apps.v4.app.(app).(create).components can't break apps.v4.app.(app).(create).components.menu-picker.
Position
Below the diagonal: apps.v4.app.(app).(create).components uses a module listed above it, which is the healthy direction.
apps.v4.app.(app).(create).components uses apps.v4.app.(app).(create).components.preview-override, so a change to apps.v4.app.(app).(create).components.preview-override can break apps.v4.app.(app).(create).components, while a change to apps.v4.app.(app).(create).components can't break apps.v4.app.(app).(create).components.preview-override.
Position
Below the diagonal: apps.v4.app.(app).(create).components uses a module listed above it, which is the healthy direction.
apps.v4.app.(app).(typeset).components uses apps.v4.app.(app).(create).components.preview-override, so a change to apps.v4.app.(app).(create).components.preview-override can break apps.v4.app.(app).(typeset).components, while a change to apps.v4.app.(app).(typeset).components can't break apps.v4.app.(app).(create).components.preview-override.
Position
Below the diagonal: apps.v4.app.(app).(typeset).components uses a module listed above it, which is the healthy direction.
apps.v4.app.(app).charts.[type] uses apps.v4.app.(app).charts.[type].page, so a change to apps.v4.app.(app).charts.[type].page can break apps.v4.app.(app).charts.[type], while a change to apps.v4.app.(app).charts.[type] can't break apps.v4.app.(app).charts.[type].page.
Position
Below the diagonal: apps.v4.app.(app).charts.[type] uses a module listed above it, which is the healthy direction.
apps.v4.components uses apps.v4.components.language-selector, so a change to apps.v4.components.language-selector can break apps.v4.components, while a change to apps.v4.components can't break apps.v4.components.language-selector.
Position
Below the diagonal: apps.v4.components uses a module listed above it, which is the healthy direction.
apps.v4.components uses apps.v4.components.message-parts, so a change to apps.v4.components.message-parts can break apps.v4.components, while a change to apps.v4.components can't break apps.v4.components.message-parts.
Position
Below the diagonal: apps.v4.components uses a module listed above it, which is the healthy direction.
apps.v4.hooks uses apps.v4.hooks.use-layout, so a change to apps.v4.hooks.use-layout can break apps.v4.hooks, while a change to apps.v4.hooks can't break apps.v4.hooks.use-layout.
Position
Below the diagonal: apps.v4.hooks uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.v4.lib uses a type in apps.v4.lib.rehype.
The types involved
apps.v4.lib.rehype → apps.v4.lib.rehype.UnistNode
Direction
apps.v4.lib uses apps.v4.lib.rehype, so a change to apps.v4.lib.rehype can break apps.v4.lib, while a change to apps.v4.lib can't break apps.v4.lib.rehype.
Position
Below the diagonal: apps.v4.lib uses a module listed above it, which is the healthy direction.
apps.v4.lib.registry-health uses apps.v4.lib.registry-health.network, so a change to apps.v4.lib.registry-health.network can break apps.v4.lib.registry-health, while a change to apps.v4.lib.registry-health can't break apps.v4.lib.registry-health.network.
Position
Below the diagonal: apps.v4.lib.registry-health uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in apps.v4.registry.bases.aria.blocks.preview.cards uses a type in apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
apps.v4.registry.bases.aria.blocks.preview.cards uses apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer, so a change to apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer can break apps.v4.registry.bases.aria.blocks.preview.cards, while a change to apps.v4.registry.bases.aria.blocks.preview.cards can't break apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
Position
Below the diagonal: apps.v4.registry.bases.aria.blocks.preview.cards uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in apps.v4.registry.bases.base.blocks.preview.cards uses a type in apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
apps.v4.registry.bases.base.blocks.preview.cards uses apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer, so a change to apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer can break apps.v4.registry.bases.base.blocks.preview.cards, while a change to apps.v4.registry.bases.base.blocks.preview.cards can't break apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
Position
Below the diagonal: apps.v4.registry.bases.base.blocks.preview.cards uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.v4.registry.bases.base.blocks.preview.cards.bar-visualizer uses a type in apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
apps.v4.registry.bases.base.blocks.preview.cards.bar-visualizer uses apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer, so a change to apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer can break apps.v4.registry.bases.base.blocks.preview.cards.bar-visualizer, while a change to apps.v4.registry.bases.base.blocks.preview.cards.bar-visualizer can't break apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
Position
Below the diagonal: apps.v4.registry.bases.base.blocks.preview.cards.bar-visualizer uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in apps.v4.registry.bases.radix.blocks.preview.cards uses a type in apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
apps.v4.registry.bases.radix.blocks.preview.cards uses apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer, so a change to apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer can break apps.v4.registry.bases.radix.blocks.preview.cards, while a change to apps.v4.registry.bases.radix.blocks.preview.cards can't break apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
Position
Below the diagonal: apps.v4.registry.bases.radix.blocks.preview.cards uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.v4.registry.bases.radix.blocks.preview.cards.bar-visualizer uses a type in apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
apps.v4.registry.bases.radix.blocks.preview.cards.bar-visualizer uses apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer, so a change to apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer can break apps.v4.registry.bases.radix.blocks.preview.cards.bar-visualizer, while a change to apps.v4.registry.bases.radix.blocks.preview.cards.bar-visualizer can't break apps.v4.registry.bases.aria.blocks.preview.cards.bar-visualizer.
Position
Below the diagonal: apps.v4.registry.bases.radix.blocks.preview.cards.bar-visualizer uses a module listed above it, which is the healthy direction.
packages.helpers.src.core uses apps.v4.registry.bases.radix.blocks.preview-03.cards.group-chat, so a change to apps.v4.registry.bases.radix.blocks.preview-03.cards.group-chat can break packages.helpers.src.core, while a change to packages.helpers.src.core can't break apps.v4.registry.bases.radix.blocks.preview-03.cards.group-chat.
Position
Below the diagonal: packages.helpers.src.core uses a module listed above it, which is the healthy direction.
packages.helpers.src.core uses packages.helpers.src.core.types, so a change to packages.helpers.src.core.types can break packages.helpers.src.core, while a change to packages.helpers.src.core can't break packages.helpers.src.core.types.
Position
Below the diagonal: packages.helpers.src.core uses a module listed above it, which is the healthy direction.
packages.react.src.questionnaire uses packages.react.src.questionnaire.types, so a change to packages.react.src.questionnaire.types can break packages.react.src.questionnaire, while a change to packages.react.src.questionnaire can't break packages.react.src.questionnaire.types.
Position
Below the diagonal: packages.react.src.questionnaire uses a module listed above it, which is the healthy direction.
packages.registry.src uses packages.registry.src.add-components, so a change to packages.registry.src.add-components can break packages.registry.src, while a change to packages.registry.src can't break packages.registry.src.add-components.
Position
Below the diagonal: packages.registry.src uses a module listed above it, which is the healthy direction.
packages.registry.src uses packages.registry.src.get-project-info, so a change to packages.registry.src.get-project-info can break packages.registry.src, while a change to packages.registry.src can't break packages.registry.src.get-project-info.
Position
Below the diagonal: packages.registry.src uses a module listed above it, which is the healthy direction.
packages.registry.src.codemod uses packages.registry.src.codemod.edits, so a change to packages.registry.src.codemod.edits can break packages.registry.src.codemod, while a change to packages.registry.src.codemod can't break packages.registry.src.codemod.edits.
Position
Below the diagonal: packages.registry.src.codemod uses a module listed above it, which is the healthy direction.
packages.registry.src.codemod uses packages.registry.src.codemod.parse, so a change to packages.registry.src.codemod.parse can break packages.registry.src.codemod, while a change to packages.registry.src.codemod can't break packages.registry.src.codemod.parse.
Position
Below the diagonal: packages.registry.src.codemod uses a module listed above it, which is the healthy direction.
packages.registry.src.codemod uses packages.registry.src.codemod.string-literals, so a change to packages.registry.src.codemod.string-literals can break packages.registry.src.codemod, while a change to packages.registry.src.codemod can't break packages.registry.src.codemod.string-literals.
Position
Below the diagonal: packages.registry.src.codemod uses a module listed above it, which is the healthy direction.
packages.registry.src.transformers uses packages.registry.src.codemod.string-literals, so a change to packages.registry.src.codemod.string-literals can break packages.registry.src.transformers, while a change to packages.registry.src.transformers can't break packages.registry.src.codemod.string-literals.
Position
Below the diagonal: packages.registry.src.transformers uses a module listed above it, which is the healthy direction.
packages.registry.src.transformers uses packages.registry.src.get-project-info, so a change to packages.registry.src.get-project-info can break packages.registry.src.transformers, while a change to packages.registry.src.transformers can't break packages.registry.src.get-project-info.
Position
Below the diagonal: packages.registry.src.transformers uses a module listed above it, which is the healthy direction.
packages.registry.src.updaters.update-fonts uses packages.registry.src.codemod.edits, so a change to packages.registry.src.codemod.edits can break packages.registry.src.updaters.update-fonts, while a change to packages.registry.src.updaters.update-fonts can't break packages.registry.src.codemod.edits.
Position
Below the diagonal: packages.registry.src.updaters.update-fonts uses a module listed above it, which is the healthy direction.
packages.shadcn.src.migrations uses packages.registry.src.get-project-info, so a change to packages.registry.src.get-project-info can break packages.shadcn.src.migrations, while a change to packages.shadcn.src.migrations can't break packages.registry.src.get-project-info.
Position
Below the diagonal: packages.shadcn.src.migrations uses a module listed above it, which is the healthy direction.
packages.shadcn.src.migrations uses packages.shadcn.src.icons.templates, so a change to packages.shadcn.src.icons.templates can break packages.shadcn.src.migrations, while a change to packages.shadcn.src.migrations can't break packages.shadcn.src.icons.templates.
Position
Below the diagonal: packages.shadcn.src.migrations uses a module listed above it, which is the healthy direction.
packages.registry.src.updaters uses packages.registry.src.codemod.edits, so a change to packages.registry.src.codemod.edits can break packages.registry.src.updaters, while a change to packages.registry.src.updaters can't break packages.registry.src.codemod.edits.
Position
Below the diagonal: packages.registry.src.updaters uses a module listed above it, which is the healthy direction.
packages.registry.src.updaters uses packages.registry.src.codemod.parse, so a change to packages.registry.src.codemod.parse can break packages.registry.src.updaters, while a change to packages.registry.src.updaters can't break packages.registry.src.codemod.parse.
Position
Below the diagonal: packages.registry.src.updaters uses a module listed above it, which is the healthy direction.
packages.registry.src.updaters uses packages.registry.src.updaters.update-fonts, so a change to packages.registry.src.updaters.update-fonts can break packages.registry.src.updaters, while a change to packages.registry.src.updaters can't break packages.registry.src.updaters.update-fonts.
Position
Below the diagonal: packages.registry.src.updaters uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
103
High / Critical
A03:2025 — Software Supply Chain Failures
73
High / Critical
A02:2025 — Security Misconfiguration
10
High / Critical
Roadmap
First, address dependency hygiene by updating four outdated packages, removing unused dependencies, and resolving three deprecated ones. Next, improve test coverage by adding tests for the twelve unreached production modules to ensure broader code validation. Finally, integrate a static analysis security step into the CI pipeline to automatically block security regressions before they are merged.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (4).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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 — 139
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 — 850
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 — 201
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 82 of 82 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 82 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1064 of 1190 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the JavaScript/TypeScript suite (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/v4/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/helpers/ (132 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/react/ (138 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/registry/ (3820 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/shadcn/ (491 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/tests/ (0 tests)) did not finish re-running within its budget: too large to re-run within its budget.
D19 Documentation Quality — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/shadcn/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/v4/app/(app)/(create)/lib/fonts.ts`, `REDACTED`, `apps/v4/app/(app)/(styles)/sera/audience-analytics/components/traffic-overview.tsx`, `apps/v4/app/(app)/blocks/[...categories]/page.tsx`, `apps/v4/app/(app)/charts/[type]/page.tsx`, … (+142 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 715 further occurrence(s) are not listed individually; the score already reflects all 755.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1667 further occurrence(s) are not listed individually; the score already reflects all 1707.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 1548 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 84 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
94 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was chat.createChatRuntime at 79. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being format.createAiSdkFormat at 27 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/helpers/src/ai-sdk/format.ts (format.createAiSdkFormat at 27), packages/registry/src/codemod/rename.ts (rename.isReference at 27), packages/helpers/src/tanstack-ai/format.ts (format.createRunEncoder at 23), packages/helpers/src/core/lower.ts (lower.lowerEvents at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 84 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 17 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with chat.createChatRuntime (cyclomatic 79), live-waveform.LiveWaveform (cyclomatic 75), live-waveform.LiveWaveform (cyclomatic 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 17 together lifts Cyclomatic Complexity from 6.3 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 123 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 10 bodies over 60 down to 60 or less in Cognitive Complexity — start with update-css.updateCssPlugin.Once (cognitive 183), live-waveform.LiveWaveform (cognitive 136), live-waveform.LiveWaveform (cognitive 136). — 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 10 together lifts Cognitive Complexity from 4.6 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.4 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 127 FunctionTooLong finding(s) in God Classes — start with nav-user.tsx (21), data-table.tsx (8), chart-area-interactive.tsx (5). — One of this dimension's main actionable groups (127 warning-level).
Resolve the 22 FileTooLong finding(s) in God Classes — start with data-table.tsx (4), sidebar.tsx (4), build-registry.mts. — One of this dimension's main actionable groups (22 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling5.2 / 10Adequate✓ 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.
5 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
Off the main sequence: @shadcn/helpers · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2875 test methods: 2873 unit, 0 integration, 0 BDD, 2 e2e. The JavaScript/TypeScript suite contributes 2875 `it`/`test` case(s) across 157 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 6 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
4 skipped (3 with a documented reason), 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2875 tests.
No assertions: should allow you to register and login · ×4packages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.ts:8
Skipped test: should override existing components.json when using --forcepackages/tests/src/tests/init.test.ts:730
Test project verifies nothing: packages/registry/test/fixtures/frameworks/remix-indie-stackpackages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.ts:8
Mock-dominated test: should throw error if project path already exists · ×23packages/shadcn/src/utils/create-project.test.ts:149
Resolve the 4 No assertions finding(s) in Test Quality — start with smoke.cy.ts (2), chat.test.ts (2). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Skipped test finding(s) in Test Quality — start with init.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with smoke.cy.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
103 outdated direct production npm dependency(ies) of 152 graded, 1 pinning defect(s), across 57 REDACTED (6 of them the product) and 22 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: eslint · ×3apps/v4/package.json:119
One package at two majors across the workspace: zod
Resolve the 4 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 152 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 152 production dependency(ies) this repository's committed lockfile resolves, across 6 product REDACTED manifest(s). Its 447 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with init.ts, add-components.ts, chat.ts. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.6 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
114 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is apps/v4/scripts/build-registry.mts. Counted over 801 of the 1573 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)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
18 deducted task-comment markers across 416268 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 18 TodoComment finding(s) in Explicit Debt — start with get-config.ts (2), update-files.ts (2), init.test.ts. — One of this dimension's main actionable groups (18 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
1 domain type(s) cross context boundaries across 5 contexts.
Cross-context type TailwindVersion (registry → shadcn)packages/shadcn/src/migrations/migrate-base-color.ts:200
What to do
Resolve the 1 Cross-context type TailwindVersion (registry → shadcn) finding(s) in Boundary Type-Coupling — start with migrate-base-color.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
3 of 6 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
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).
103 finding(s): 0 critical, 78 high, 23 medium, 2 low. 64 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 216 file(s) — `apps/v4/app/(app)/(create)/lib/fonts.ts` (line 31), `REDACTED` (line 568), `apps/v4/app/(app)/(styles)/sera/audience-analytics/components/traffic-overview.tsx` (lines 43–58), `apps/v4/app/(app)/blocks/[...categories]/page.tsx` (line 31), `apps/v4/app/(app)/charts/[type]/page.tsx` (line 55), … (+211 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
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 64 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 (64 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 35 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (34), REDACTED. — One of this dimension's main actionable groups (35 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 801 of the 1573 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
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.
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 29 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.
End-of-life runtime: Node.js 20.nvmrc:1
What to do
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.3 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby. (×9) — apps/v4/components/cards/create-account.tsx:41, apps/v4/registry/styles.tsx:7, apps/v4/registry/styles.tsx:29, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.5 / 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 UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×7) — REDACTED:612, apps/v4/app/(app)/(styles)/sera/edit-article/components/editor-workspace.tsx:271, apps/v4/app/(app)/(typeset)/components/docs-panel.tsx:210, …
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×8) — apps/v4/app/(app)/(root)/cards/ui-elements.tsx:80, apps/v4/app/(app)/(styles)/sera/edit-article/components/editor-workspace.tsx:318, apps/v4/app/(app)/(styles)/sera/media-library-table/components/filter-library.tsx:192, …
This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×23) — apps/v4/app/(app)/(styles)/sera/media-library-table/components/filter-library.tsx:182, apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:104, apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:129, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — apps/v4/components/block-viewer.tsx:246
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×7) — templates/astro-monorepo/apps/web/src/pages/index.astro:6, templates/next-app/app/layout.tsx:22, templates/next-monorepo/apps/web/app/layout.tsx:22, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. (×2) — templates/next-app/app/layout.tsx:22, templates/next-monorepo/apps/web/app/layout.tsx:22
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<button> 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). (×2) — apps/v4/app/(app)/(styles)/sera/media-library/components/asset-grid.tsx:119, apps/v4/registry/bases/aria/ui/attachment.tsx:185
<pre> 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). (×3) — apps/v4/registry/bases/aria/ui/code-block.tsx:161, apps/v4/registry/bases/base/ui/code-block.tsx:161, apps/v4/registry/bases/radix/ui/code-block.tsx:161
<select> 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). (×4) — apps/v4/registry/bases/aria/ui/native-select.tsx:24, apps/v4/registry/bases/base/ui/native-select.tsx:24, apps/v4/registry/bases/radix/ui/native-select.tsx:24, …
<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). (×3) — apps/v4/registry/bases/base/ui/textarea.tsx:6, apps/v4/registry/bases/radix/ui/textarea.tsx:6, apps/v4/registry/new-york-v4/ui/textarea.tsx:6
<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). (×2) — apps/v4/registry/bases/radix/ui/input.tsx:6, apps/v4/registry/new-york-v4/ui/input.tsx:6
`.style-luma .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:360
`.style-luma .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:634
`.style-luma .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:1003
`.style-luma .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:1031
`.style-luma .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:1460
`.style-luma .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-luma.css:1569
`.style-lyra .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:361
`.style-lyra .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:666
`.style-lyra .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:843
`.style-lyra .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:871
`.style-lyra .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:1439
`.style-lyra .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-lyra.css:1548
`.style-maia .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:382
`.style-maia .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:692
`.style-maia .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:869
`.style-maia .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:897
`.style-maia .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:1461
`.style-maia .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-maia.css:1570
`.style-mira .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:382
`.style-mira .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:691
`.style-mira .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:868
`.style-mira .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:896
`.style-mira .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:1466
`.style-mira .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-mira.css:1575
`.style-nova .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-nova.css:382
`.style-nova .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/v4/registry/styles/style-nova.css:691
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 1220 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C2 · Access Controls3.3 / 10Weak✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Only 2 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`generateStaticParams` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — apps/v4/app/(app)/llm/[[...slug]]/route.ts:59
The guard above `return "custom";` also returns `"custom"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — apps/v4/components/message-parts.tsx:544
The guard above `return "registry:component";` also returns `"registry:component"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — packages/registry/src/registry/resolve-file-imports.ts:247
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/shadcn/src/index.ts:23
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/tests/src/tests/init.test.ts:730
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 58 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
2124 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 10 of 27 project(s) that lack one — worth up to 0.7 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/v4`.
`packages/registry/src/logger.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:5
`packages/registry/src/logger.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:8
`packages/registry/src/logger.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:11
`packages/registry/src/logger.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:14
`packages/registry/src/logger.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:17
`packages/registry/src/logger.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/logger.ts:20
`packages/registry/src/updaters/update-css.ts` reports through `console.*` at line 480 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/updaters/update-css.ts:480
`packages/registry/src/updaters/update-css.ts` reports through `console.*` at line 577 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/registry/src/updaters/update-css.ts:577
`packages/shadcn/src/utils/file-helper.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/utils/file-helper.ts:40
`packages/shadcn/src/commands/docs.ts` reports through `console.*` at line 83 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/docs.ts:83
`packages/shadcn/src/commands/info.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/info.ts:44
`packages/shadcn/src/commands/info.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/info.ts:70
`packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 90 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/preset.ts:90
`packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/preset.ts:171
`packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 193 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/preset.ts:193
`packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 205 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/preset.ts:205
`packages/shadcn/src/commands/search.ts` reports through `console.*` at line 219 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/search.ts:219
`packages/shadcn/src/commands/view.ts` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/view.ts:71
`packages/shadcn/src/commands/registry/build.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/shadcn/src/commands/registry/build.ts:143
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 44136 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`readFileSync` in `GET` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:9
`fs.readFileSync` in `callback to nodesToProcess.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/v4/lib/rehype.ts:169
`existsSync` in `loadEnvFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/env-loader.ts:24
`fs.existsSync` in `isMonorepoRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/registry/src/get-monorepo-info.ts:21, packages/registry/src/get-monorepo-info.ts:27, packages/registry/src/get-monorepo-info.ts:39, …
`fs.existsSync` in `getMonorepoTargets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/registry/src/get-monorepo-info.ts:72, packages/registry/src/get-monorepo-info.ts:76
`fs.existsSync` in `getWorkspacePatterns` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/registry/src/get-monorepo-info.ts:132, packages/registry/src/get-monorepo-info.ts:138
`fs.existsSync` in `getProjectComponents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/get-project-info.ts:667
`existsSync` in `getRegistriesConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/registry/api.ts:224
`existsSync` in `getPackageJsonRegistries` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/registry/api.ts:250
`existsSync` in `updateEnvVars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/updaters/update-env-vars.ts:48
`existsSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/registry/src/updaters/update-files.ts:139, packages/registry/src/updaters/update-files.ts:146, packages/registry/src/updaters/update-files.ts:262
`statSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/updaters/update-files.ts:159
`existsSync` in `resolveImports` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/updaters/update-files.ts:396
`existsSync` in `findLayoutFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:255
`fs.existsSync` in `findGitRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/registry/src/workspace.ts:204
`existsSync` in `callback to action` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/shadcn/src/commands/diff.ts:60, packages/shadcn/src/commands/info.ts:38, packages/shadcn/src/commands/preset.ts:165
`existsSync` in `callback to registryIndex.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/commands/diff.ts:101
`existsSync` in `diffComponent` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/commands/diff.ts:198
`fsExtra.existsSync` in `runEject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/commands/eject.ts:56
`fsExtra.existsSync` in `callback to action` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/shadcn/src/commands/init.ts:231, packages/shadcn/src/commands/init.ts:330, packages/shadcn/src/commands/search.ts:102, …
`fsExtra.existsSync` in `runInit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/shadcn/src/commands/init.ts:635, packages/shadcn/src/commands/init.ts:749, packages/shadcn/src/commands/init.ts:817
`fs.existsSync` in `callback to find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/commands/registry/add.ts:82
`fsExtra.existsSync` in `migrateCn` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/migrations/cn/index.ts:26
`fsExtra.existsSync` in `updateConfigBaseColor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/migrations/migrate-base-color.ts:304
`fsExtra.existsSync` in `updateConfigIconLibrary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/migrations/migrate-icons.ts:265
`fs.existsSync` in `preFlightAdd` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/shadcn/src/preflights/preflight-add.ts:22
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
apps/v4/registry/bases/radix/blocks/sidebar-10/ and apps/v4/registry/bases/radix/blocks/sidebar-15/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~408 lines; the trees hold 8 and 11 files). That is one structural fact, not 5 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — apps/v4/registry/bases/radix/blocks/sidebar-10/components/nav-favorites.tsx:1
apps/v4/registry/new-york-v4/blocks/sidebar-10/ and apps/v4/registry/new-york-v4/blocks/sidebar-15/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~340 lines; the trees hold 8 and 11 files). That is one structural fact, not 5 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — apps/v4/registry/new-york-v4/blocks/sidebar-10/components/nav-favorites.tsx:1
244 duplicated blocks under apps/v4/registry/bases/ have copies in at least two of the sibling directories aria, base, radix — 230 of them are reported below, and 14 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 244 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 244 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 244 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. — apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3
152 duplicated blocks under apps/v4/registry/ have copies in at least two of the sibling directories bases, new-york-v4 — 128 of them are reported below, and 24 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 152 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 152 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 152 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. — apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3
69 duplicated blocks under apps/v4/ have copies in at least two of the sibling directories app, components, hooks, registry — 51 of them are reported below, and 18 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 69 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 69 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 69 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. — apps/v4/app/(app)/(root)/cards/transfer-funds.tsx:32
38 duplicated blocks under apps/v4/registry/new-york-v4/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+16 more sibling(s) not listed) — 30 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3
33 duplicated blocks under apps/v4/registry/bases/base/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+18 more sibling(s) not listed) — 29 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 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 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 33 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. — apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20
28 duplicated blocks under apps/v4/registry/bases/radix/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+18 more sibling(s) not listed) — 22 of them are reported below, and 6 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 28 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 28 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 28 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. — apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20
22 duplicated blocks under apps/v4/registry/bases/aria/blocks/ have copies in at least two of the sibling directories dashboard-01, login-05, sidebar-01, sidebar-02, sidebar-03, sidebar-04 (+11 more sibling(s) not listed) — 20 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20
20 duplicated blocks under apps/v4/app/(app)/ have copies in at least two of the sibling directories (create), (root), (styles), (typeset), blocks, charts (+1 more sibling(s) not listed) — 17 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/v4/app/(app)/(create)/components/picker.tsx:13
9 duplicated blocks under apps/v4/app/(app)/(styles)/sera/ have copies in at least two of the sibling directories article-directory, audience-analytics, edit-article, empty-state, media-library, media-library-table — 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. — apps/v4/app/(app)/(styles)/sera/media-library-table/components/preview-header.tsx:12
5 duplicated blocks under packages/ have copies in at least two of the sibling directories registry, shadcn — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/registry/src/updaters/update-files.ts:109
apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 583 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. — apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3
apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3 · apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 525 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. — apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3
apps/v4/registry/bases/base/ui/_registry.ts:1 · apps/v4/registry/bases/radix/ui/_registry.ts:1 — these 2 files are line-for-line copies of one another — 471 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. — apps/v4/registry/bases/base/ui/_registry.ts:1
apps/v4/registry/bases/aria/blocks/_registry.ts:1 · apps/v4/registry/bases/base/blocks/_registry.ts:1 · apps/v4/registry/bases/radix/blocks/_registry.ts:1 — these 3 files are line-for-line copies of one another — 450 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. — apps/v4/registry/bases/aria/blocks/_registry.ts:1
apps/v4/registry/bases/aria/ui/_registry.ts:1 · apps/v4/registry/bases/radix/ui/_registry.ts:1 — these 2 files are line-for-line copies of one another — 449 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. — apps/v4/registry/bases/aria/ui/_registry.ts:1
apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:3 — these 3 files are line-for-line copies of one another — 391 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. — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:3
packages/registry/src/registry/loader.ts:77 · packages/registry/src/registry/source.ts:87 — the two spans are one implementation copied and then locally edited — 1664 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/registry/src/registry/loader.ts:77
apps/v4/registry/bases/radix/ui/sidebar.tsx:3 · apps/v4/registry/new-york-v4/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 307 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. — apps/v4/registry/bases/radix/ui/sidebar.tsx:3
apps/v4/registry/bases/aria/ui/sidebar.tsx:3 · apps/v4/registry/bases/radix/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 302 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. — apps/v4/registry/bases/aria/ui/sidebar.tsx:3
apps/v4/registry/bases/base/ui/sidebar.tsx:3 · apps/v4/registry/bases/radix/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 291 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. — apps/v4/registry/bases/base/ui/sidebar.tsx:3
apps/v4/registry/bases/aria/blocks/preview/cards/bar-visualizer.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/bar-visualizer.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/bar-visualizer.tsx:3 — these 3 files are line-for-line copies of one another — 244 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. — apps/v4/registry/bases/aria/blocks/preview/cards/bar-visualizer.tsx:3
apps/v4/registry/bases/aria/blocks/preview/cards/codespaces-card.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/codespaces-card.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/codespaces-card.tsx:3 — these 3 files are line-for-line copies of one another — 236 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. — apps/v4/registry/bases/aria/blocks/preview/cards/codespaces-card.tsx:3
apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/radix/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20
apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/aria/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20
apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/base/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20
apps/v4/registry/bases/aria/blocks/preview-02/cards/sidebar-nav.tsx:16 · apps/v4/registry/bases/base/blocks/preview-02/cards/sidebar-nav.tsx:16 · apps/v4/registry/bases/radix/blocks/preview-02/cards/sidebar-nav.tsx:16 — these 3 files are line-for-line copies of one another — 230 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. — apps/v4/registry/bases/aria/blocks/preview-02/cards/sidebar-nav.tsx:16
apps/v4/registry/bases/aria/blocks/sidebar-07/components/app-sidebar.tsx:19 · apps/v4/registry/bases/base/blocks/sidebar-07/components/app-sidebar.tsx:19 · apps/v4/registry/bases/radix/blocks/sidebar-07/components/app-sidebar.tsx:19 — 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. — apps/v4/registry/bases/aria/blocks/sidebar-07/components/app-sidebar.tsx:19
apps/v4/registry/bases/aria/blocks/preview-02/cards/recent-transactions.tsx:3 · apps/v4/registry/bases/base/blocks/preview-02/cards/recent-transactions.tsx:3 · apps/v4/registry/bases/radix/blocks/preview-02/cards/recent-transactions.tsx:3 — these 3 files are line-for-line copies of one another — 208 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. — apps/v4/registry/bases/aria/blocks/preview-02/cards/recent-transactions.tsx:3
apps/v4/registry/bases/aria/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/bases/aria/blocks/sidebar-15/components/sidebar-left.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-15/components/sidebar-left.tsx:3 · +2 more site(s) not listed — these 6 files are line-for-line copies of one another — 208 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. — apps/v4/registry/bases/aria/blocks/sidebar-10/components/app-sidebar.tsx:3
REDACTED:3 · REDACTED:3 · REDACTED:3 · REDACTED:3 — these 4 files are line-for-line copies of one another — 189 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. — REDACTED:3
apps/v4/registry/bases/aria/blocks/sidebar-09/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-09/components/app-sidebar.tsx:3 · apps/v4/registry/bases/radix/blocks/sidebar-09/components/app-sidebar.tsx:3 — these 3 files are line-for-line copies of one another — 187 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. — apps/v4/registry/bases/aria/blocks/sidebar-09/components/app-sidebar.tsx:3
apps/v4/registry/bases/aria/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/bases/base/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/new-york-v4/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · +1 more site(s) not listed — these 5 files are line-for-line copies of one another — 180 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. — apps/v4/registry/bases/aria/blocks/dashboard-01/components/chart-area-interactive.tsx:3
apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:625 · apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:663 — 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. — apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:625
apps/v4/registry/bases/aria/blocks/dashboard-01/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/dashboard-01/components/app-sidebar.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/app-sidebar.tsx:3 — these 3 files are line-for-line copies of one another — 165 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. — apps/v4/registry/bases/aria/blocks/dashboard-01/components/app-sidebar.tsx:3
apps/v4/registry/bases/base/ui/combobox.tsx:3 · apps/v4/registry/bases/radix/ui/combobox.tsx:3 — these 2 files are line-for-line copies of one another — 165 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. — apps/v4/registry/bases/base/ui/combobox.tsx:3
apps/v4/registry/new-york-v4/charts/chart-bar-interactive.tsx:3 · apps/v4/registry/new-york-v4/charts/chart-line-interactive.tsx:3 — these 2 files are line-for-line copies of one another — 160 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. — apps/v4/registry/new-york-v4/charts/chart-bar-interactive.tsx:3
apps/v4/registry/bases/aria/ui/questionnaire.tsx:3 · apps/v4/registry/bases/base/ui/questionnaire.tsx:3 · apps/v4/registry/bases/radix/ui/questionnaire.tsx:3 — these 3 files are line-for-line copies of one another — 152 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. — apps/v4/registry/bases/aria/ui/questionnaire.tsx:3
apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/new-york-v4/blocks/sidebar-15/components/sidebar-left.tsx:3 — these 2 files are line-for-line copies of one another — 149 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. — apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/registry/src/updaters/update-css-vars.ts:12 imports postcss/lib/at-rule, 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/registry/src/updaters/update-css-vars.ts:12
packages/registry/src/updaters/update-css-vars.ts:13 imports postcss/lib/root, 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/registry/src/updaters/update-css-vars.ts:13
packages/registry/src/updaters/update-css-vars.ts:14 imports postcss/lib/rule, 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/registry/src/updaters/update-css-vars.ts:14
packages/registry/src/updaters/update-css.ts:15 imports postcss/lib/at-rule, 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/registry/src/updaters/update-css.ts:15
packages/registry/src/updaters/update-css.ts:16 imports postcss/lib/declaration, 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/registry/src/updaters/update-css.ts:16
packages/registry/src/updaters/update-css.ts:17 imports postcss/lib/root, 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/registry/src/updaters/update-css.ts:17
packages/registry/src/updaters/update-css.ts:18 imports postcss/lib/rule, 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/registry/src/updaters/update-css.ts:18
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 82 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/shadcn/src/commands/init.ts:170
updateFiles has cyclomatic complexity 59 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/registry/src/updaters/update-files.ts:50
Once has cyclomatic complexity 49 and cognitive complexity 161; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/registry/src/updaters/update-css.ts:112
convertNode has cyclomatic complexity 49 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/registry/src/codemod/indentation.ts:809
(anonymous) has cyclomatic complexity 45 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/shadcn/src/commands/add.ts:77
runInit has cyclomatic complexity 41 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/shadcn/src/commands/init.ts:610
isForbiddenIpv4 has cyclomatic complexity 37 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/v4/lib/registry-health/network.ts:102
handleKeyDown has cyclomatic complexity 36 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/react/src/questionnaire/use-questionnaire-root.ts:361
stripJsonCommentsAndTrailingCommas has cyclomatic complexity 34 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/registry/src/get-project-info.ts:408
addWorkspaceComponents 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/registry/src/add-components.ts:148
(anonymous) has cyclomatic complexity 30 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/registry/src/transformers/transform-rtl.ts:131
migrateIcons has cyclomatic complexity 30 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/shadcn/src/migrations/migrate-icons.ts:56
handleCallTool has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/shadcn/src/mcp/index.ts:197
rafId has cyclomatic complexity 29 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. (×3) — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:310, apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:310, apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:310
eventsFromParts has cyclomatic complexity 28 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/helpers/src/ai-sdk/parts.ts:273
migrateBaseColor has cyclomatic complexity 28 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/shadcn/src/migrations/migrate-base-color.ts:33
getMessagePartComponent has cyclomatic complexity 28 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/v4/components/message-parts.tsx:301
updateImportAliases has cyclomatic complexity 27 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/registry/src/transformers/transform-import.ts:193
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
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.
apps/v4/registry/bases/base/ui/_registry.ts has 1150 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/base/ui/_registry.ts:1
apps/v4/registry/bases/radix/ui/_registry.ts has 1128 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/radix/ui/_registry.ts:1
packages/registry/src/codemod/indentation.ts has 1122 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/registry/src/codemod/indentation.ts:1
packages/shadcn/src/commands/init.ts has 955 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/commands/init.ts:1
apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx has 947 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:1
apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx has 883 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:1
apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx has 871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:1
apps/v4/registry/config.ts has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/config.ts:1
apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx:1
apps/v4/registry/new-york-v4/ui/_registry.ts has 758 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/new-york-v4/ui/_registry.ts:1
packages/registry/src/updaters/update-files.ts has 744 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/registry/src/updaters/update-files.ts:1
apps/v4/components/theme-customizer.tsx has 730 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/components/theme-customizer.tsx:1
packages/helpers/src/core/chat.ts has 707 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/helpers/src/core/chat.ts:1
REDACTED has 697 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/registry/src/registry/resolver.ts has 696 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/registry/src/registry/resolver.ts:1
packages/registry/src/updaters/update-css-vars.ts has 696 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/registry/src/updaters/update-css-vars.ts:1
REDACTED has 692 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/shadcn/src/preset/resolve.ts has 684 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/preset/resolve.ts:1
apps/v4/registry/bases/base/ui/sidebar.tsx has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/base/ui/sidebar.tsx:1
packages/shadcn/src/migrations/migrate-icons.ts has 675 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/migrations/migrate-icons.ts:1
packages/react/src/message-scroller/use-message-scroller-controller.ts has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/message-scroller/use-message-scroller-controller.ts:1
apps/v4/registry/new-york-v4/ui/sidebar.tsx has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/new-york-v4/ui/sidebar.tsx:1
packages/registry/src/updaters/update-tailwind-config.ts has 666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/registry/src/updaters/update-tailwind-config.ts:1
packages/shadcn/src/utils/dry-run-formatter.ts has 665 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/utils/dry-run-formatter.ts:1
apps/v4/registry/bases/aria/ui/sidebar.tsx has 663 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/aria/ui/sidebar.tsx:1
apps/v4/registry/bases/radix/ui/sidebar.tsx has 654 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/radix/ui/sidebar.tsx:1
packages/registry/src/registry/validate.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/registry/src/registry/validate.ts:1
apps/v4/lib/registry-health/monitor.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/lib/registry-health/monitor.ts:1
apps/v4/components/command-menu.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/components/command-menu.tsx:1
packages/registry/src/registry/source.ts has 581 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/registry/src/registry/source.ts:1
packages/registry/src/registry/loader.ts has 577 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/registry/src/registry/loader.ts:1
packages/registry/src/get-project-info.ts has 569 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/registry/src/get-project-info.ts:1
packages/shadcn/src/styles/transform-style-map.ts has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/shadcn/src/styles/transform-style-map.ts:1
REDACTED has 547 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
apps/v4/components/message-parts.tsx has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/components/message-parts.tsx:1
apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:1
apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:1
apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:1
packages/shadcn/src/mcp/index.ts has 540 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/mcp/index.ts:1
packages/registry/src/updaters/update-css.ts 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/registry/src/updaters/update-css.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage1.2 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — apps/v4/registry/_legacy-colors.ts:1, apps/v4/registry/bases/radix/examples/item-example.tsx:1, apps/v4/registry/bases/aria/examples/item-example.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code8.2 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 890 application, 25 tooling and 164 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 (890 application, 25 tooling, 164 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 (×20) — apps/v4/mdx-components.tsx, apps/v4/components/docs-sidebar.tsx, packages/shadcn/src/commands/registry/build.ts, …
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/mdx-components.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — apps/v4/components/directory-list.tsx, apps/v4/components/code-block-command.tsx, apps/v4/components/components-list.tsx, …
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×9) — apps/v4/components/cards/chat.tsx, apps/v4/components/cards/team-members.tsx, apps/v4/components/cards/forms.tsx, …
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/directory-list.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — apps/v4/components/directory-add-button.tsx, apps/v4/hooks/use-search-registry.ts, apps/v4/components/directory-search.tsx
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/site-config.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/v4/hooks/use-layout.tsx
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/message-animated.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/v4/lib/message-animations.ts
no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/shadcn/src/commands/registry/build.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/shadcn/src/preflights/preflight-registry.ts
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in apps/v4/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream4.3 / 10Weak✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
`spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `proc.stdout`, while `proc.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`proc.stdout.on('data', …)`, or `proc.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — apps/v4/scripts/build-registry.mts:1435
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 2/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`StarsCount` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — apps/v4/components/github-link.tsx:22
`getRegistryItemFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:571
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.6 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`currentBase.meta.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(app)/(create)/components/base-picker.tsx:56
``
(function() {
// Forward O key.
document.addEventListener('keydown', functi…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(app)/(create)/components/open-preset.tsx:175
`item.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:631
`item.meta?.logo??""` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:711
``
(function() {
// Forward r key (shuffle) and Shift+R (reset).
document.addE…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(app)/(create)/components/random-button.tsx:42
`JSON.stringify(websiteJsonLd).replace(/</g,"\\u003c")` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(app)/(root)/page.tsx:78
`FIXTURES[name as keyof typeof FIXTURES]` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(view)/preview/typeset/[name]/page.tsx:30
`PARAMS_STYLE` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/(view)/preview/typeset/layout.tsx:43
`DOCS_SIDEBAR_SCROLL_RESTORE_SCRIPT` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/layout.tsx:88
``
try {
if (localStorage.theme === 'dark' || ((!('theme' in localStorage) || localStora…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/app/layout.tsx:93
`file?.highlightedContent??""` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/components/block-viewer.tsx:359
`chart.highlightedCode` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:73
`highlightedCode` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:113
`registry.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/components/directory-list.tsx:237
`activeBase.meta.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/v4/components/docs-base-switcher.tsx:43
`Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — REDACTED:95, REDACTED:95, REDACTED:95, …
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×12) — packages/shadcn/src/templates/create-template.ts:316, packages/shadcn/src/commands/mcp.ts:250, packages/shadcn/src/commands/search.ts:119, …
`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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — packages/registry/src/get-project-info.ts:392, packages/registry/src/registry/resolve-file-imports.ts:146
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×6) — apps/v4/registry/bases/radix/ui/code-block.tsx:118, apps/v4/registry/bases/radix/hooks/use-highlighted-code.ts:23, apps/v4/registry/bases/base/ui/code-block.tsx:118, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
50/70 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.2 `!` null assertions per 1k TypeScript source lines — 252 assertion(s) across the 209700 source line(s) of the 1545 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/registry/src/codemod/indentation.ts (59), packages/registry/src/updaters/update-tailwind-config.ts (15), packages/registry/src/codemod/array-literals.ts (14). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 7 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 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 — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not included
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 reads .NET projects as units only; 6 folder(s) declared by REDACTED were not judged for an overview, an example or the map.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .mts, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 147 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.mts, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 27 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (25 with fewer than two methods, 1 stateless, 1 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
S1 Web-Security Posture — Not assessed: 1548 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC1 · Text alternatives· <svg role="img"> without an accessible name · ×9
<svg role="img"> without an accessible name apps/v4/components/cards/create-account.tsx:41— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:7— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:29— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:52— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:77— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:99— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:122— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:145— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
<svg role="img"> without an accessible name apps/v4/registry/styles.tsx:170— An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby.
AC3 · Page structure· Document without a <title> · ×2
Document without a <title> templates/next-app/app/layout.tsx:22— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
Document without a <title> templates/next-monorepo/apps/web/app/layout.tsx:22— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title apps/v4/components/block-viewer.tsx:246— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
FunctionTooLong: use-message-scroller-controller.useMessageScrollerController packages/react/src/message-scroller/use-message-scroller-controller.ts:57— FunctionTooLong — useMessageScrollerController runs 451 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 351 over it, 4.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: chat.createChatRuntime packages/helpers/src/core/chat.ts:139— FunctionTooLong — createChatRuntime runs 436 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 336 over it, 4.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: project-form.ProjectForm REDACTED:121— FunctionTooLong — ProjectForm runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: theme-customizer.CustomizerCode apps/v4/components/theme-customizer.tsx:166— FunctionTooLong — CustomizerCode runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: live-waveform.LiveWaveform apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:17— FunctionTooLong — LiveWaveform runs 392 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 292 over it, 3.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: live-waveform.LiveWaveform apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:17— FunctionTooLong — LiveWaveform runs 392 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 292 over it, 3.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: live-waveform.LiveWaveform apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:17— FunctionTooLong — LiveWaveform runs 392 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 292 over it, 3.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: use-questionnaire-item.useQuestionnaireItem packages/react/src/questionnaire/use-questionnaire-item.ts:35— FunctionTooLong — useQuestionnaireItem runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.86× 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: command-menu.CommandMenu apps/v4/components/command-menu.tsx:42— FunctionTooLong — CommandMenu runs 342 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 242 over it, 3.42× 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: codespaces-card.CodespacesCard apps/v4/registry/bases/base/blocks/preview/cards/codespaces-card.tsx:56— FunctionTooLong — CodespacesCard runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: codespaces-card.CodespacesCard apps/v4/registry/bases/radix/blocks/preview/cards/codespaces-card.tsx:56— FunctionTooLong — CodespacesCard runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: codespaces-card.CodespacesCard apps/v4/registry/bases/aria/blocks/preview/cards/codespaces-card.tsx:51— FunctionTooLong — CodespacesCard runs 325 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 225 over it, 3.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: data-table.DataTable apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:305— FunctionTooLong — DataTable runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: use-questionnaire-root.useQuestionnaireRoot packages/react/src/questionnaire/use-questionnaire-root.ts:38— FunctionTooLong — useQuestionnaireRoot runs 319 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 219 over it, 3.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: data-table.DataTable apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:375— FunctionTooLong — DataTable runs 308 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 208 over it, 3.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: data-table.DataTable apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:374— FunctionTooLong — DataTable runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.98× 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: recent-transactions.RecentTransactions apps/v4/registry/bases/base/blocks/preview-02/cards/recent-transactions.tsx:29— FunctionTooLong — RecentTransactions runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× 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: recent-transactions.RecentTransactions apps/v4/registry/bases/radix/blocks/preview-02/cards/recent-transactions.tsx:29— FunctionTooLong — RecentTransactions runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× 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: recent-transactions.RecentTransactions apps/v4/registry/bases/aria/blocks/preview-02/cards/recent-transactions.tsx:30— FunctionTooLong — RecentTransactions runs 274 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× 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: sidebar-nav.SidebarNav apps/v4/registry/bases/aria/blocks/preview-02/cards/sidebar-nav.tsx:18— FunctionTooLong — SidebarNav runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sidebar-nav.SidebarNav apps/v4/registry/bases/base/blocks/preview-02/cards/sidebar-nav.tsx:18— FunctionTooLong — SidebarNav runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sidebar-nav.SidebarNav apps/v4/registry/bases/radix/blocks/preview-02/cards/sidebar-nav.tsx:18— FunctionTooLong — SidebarNav runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: data-table.DataTable apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx:358— FunctionTooLong — DataTable runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.handleCallTool packages/shadcn/src/mcp/index.ts:197— FunctionTooLong — handleCallTool runs 236 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 136 over it, 2.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: editor-workspace.EditorWorkspace apps/v4/app/(app)/(styles)/sera/edit-article/components/editor-workspace.tsx:103— FunctionTooLong — EditorWorkspace runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Sync-over-async blocking REDACTED:9— `readFileSync` in `GET` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking apps/v4/lib/rehype.ts:169— `fs.readFileSync` in `callback to nodesToProcess.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/env-loader.ts:24— `existsSync` in `loadEnvFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:21— `fs.existsSync` in `isMonorepoRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:27— `fs.existsSync` in `isMonorepoRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:39— `fs.existsSync` in `isMonorepoRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:44— `fs.existsSync` in `isMonorepoRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:72— `fs.existsSync` in `getMonorepoTargets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:76— `fs.existsSync` in `getMonorepoTargets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:132— `fs.existsSync` in `getWorkspacePatterns` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-monorepo-info.ts:138— `fs.existsSync` in `getWorkspacePatterns` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/get-project-info.ts:667— `fs.existsSync` in `getProjectComponents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/registry/api.ts:224— `existsSync` in `getRegistriesConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/registry/api.ts:250— `existsSync` in `getPackageJsonRegistries` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-env-vars.ts:48— `existsSync` in `updateEnvVars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-files.ts:139— `existsSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-files.ts:146— `existsSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-files.ts:159— `statSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-files.ts:262— `existsSync` in `updateFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/updaters/update-files.ts:396— `existsSync` in `resolveImports` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:255— `existsSync` in `findLayoutFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/registry/src/workspace.ts:204— `fs.existsSync` in `findGitRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/shadcn/src/commands/diff.ts:60— `existsSync` in `callback to action` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/shadcn/src/commands/diff.ts:101— `existsSync` in `callback to registryIndex.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/shadcn/src/commands/diff.ts:198— `existsSync` in `diffComponent` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file apps/v4/registry/_legacy-colors.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/v4/registry/bases/radix/examples/item-example.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 apps/v4/registry/bases/aria/examples/item-example.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 apps/v4/registry/bases/base/examples/item-example.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 apps/v4/scripts/build-registry.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 apps/v4/registry/_legacy-base-colors.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/v4/registry/bases/aria/examples/attachment-example.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 apps/v4/registry/bases/base/examples/attachment-example.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 apps/v4/registry/bases/radix/examples/attachment-example.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 apps/v4/registry/bases/base/examples/trace-example.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 apps/v4/registry/bases/radix/examples/trace-example.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 apps/v4/registry/bases/aria/examples/trace-example.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 apps/v4/registry/bases/base/examples/combobox-example.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 apps/v4/registry/bases/base/examples/code-block-example.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 apps/v4/registry/bases/radix/examples/code-block-example.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 apps/v4/registry/bases/aria/examples/code-block-example.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 apps/v4/registry/bases/aria/examples/combobox-example.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 apps/v4/registry/bases/radix/examples/combobox-example.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 apps/v4/registry/bases/base/examples/field-example.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 apps/v4/registry/bases/base/examples/button-example.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 apps/v4/registry/bases/aria/examples/button-example.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 apps/v4/registry/bases/radix/examples/button-example.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 apps/v4/registry/bases/aria/examples/field-example.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 apps/v4/registry/bases/base/examples/dropdown-menu-example.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 apps/v4/registry/bases/radix/examples/dropdown-menu-example.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.
+ 15 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×26
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:360— `.style-luma .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:634— `.style-luma .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:1003— `.style-luma .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:1031— `.style-luma .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:1460— `.style-luma .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-luma.css:1569— `.style-luma .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:361— `.style-lyra .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:666— `.style-lyra .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:843— `.style-lyra .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:871— `.style-lyra .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:1439— `.style-lyra .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-lyra.css:1548— `.style-lyra .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:382— `.style-maia .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:692— `.style-maia .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:869— `.style-maia .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:897— `.style-maia .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:1461— `.style-maia .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-maia.css:1570— `.style-maia .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:382— `.style-mira .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:691— `.style-mira .cn-input-otp-slot` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:868— `.style-mira .cn-navigation-menu-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:896— `.style-mira .cn-navigation-menu-popup` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:1466— `.style-mira .cn-bubble-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-mira.css:1575— `.style-mira .cn-attachment-trigger` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/v4/registry/styles/style-nova.css:382— `.style-nova .cn-command-list` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
FileTooLong: scripts/build-registry.mts apps/v4/scripts/build-registry.mts— FileTooLong — 1128 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 628 over it, 2.26× 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: codemod/indentation.ts packages/registry/src/codemod/indentation.ts— FileTooLong — 859 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 359 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: components/data-table.tsx apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx— FileTooLong — 852 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 352 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/data-table.tsx apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx— FileTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 298 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/data-table.tsx apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx— FileTooLong — 792 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 292 over it, 1.58× 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: registry/config.ts apps/v4/registry/config.ts— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× 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/data-table.tsx apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx— FileTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 222 over it, 1.44× 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: commands/init.ts packages/shadcn/src/commands/init.ts— FileTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 210 over it, 1.42× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/theme-customizer.tsx apps/v4/components/theme-customizer.tsx— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: CustomizerCode (166-630). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: ProjectForm (121-587). The bar is 500 significant lines; this is 121 over it, 1.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/sidebar.tsx apps/v4/registry/new-york-v4/ui/sidebar.tsx— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: updaters/update-files.ts packages/registry/src/updaters/update-files.ts— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ui/sidebar.tsx apps/v4/registry/bases/aria/ui/sidebar.tsx— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ui/sidebar.tsx apps/v4/registry/bases/base/ui/sidebar.tsx— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 51 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ui/sidebar.tsx apps/v4/registry/bases/radix/ui/sidebar.tsx— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× 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: preset/resolve.ts packages/shadcn/src/preset/resolve.ts— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: core/chat.ts packages/helpers/src/core/chat.ts— FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: registry/resolver.ts packages/registry/src/registry/resolver.ts— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: registry-health/monitor.ts apps/v4/lib/registry-health/monitor.ts— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× 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: updaters/update-css-vars.ts packages/registry/src/updaters/update-css-vars.ts— FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4 over it, 1.01× 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: registry/validate.ts packages/registry/src/registry/validate.ts— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 over it, 1.00× 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×19
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×19
Untrusted text written into markup unescaped apps/v4/app/(app)/(create)/components/base-picker.tsx:56— `currentBase.meta.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/(app)/(create)/components/open-preset.tsx:175— ``
(function() {
// Forward O key.
document.addEventListener('keydown', functi…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:631— `item.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:711— `item.meta?.logo??""` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/(app)/(create)/components/random-button.tsx:42— ``
(function() {
// Forward r key (shuffle) and Shift+R (reset).
document.addE…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/(app)/(root)/page.tsx:78— `JSON.stringify(websiteJsonLd).replace(/</g,"\\u003c")` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/(view)/preview/typeset/[name]/page.tsx:30— `FIXTURES[name as keyof typeof FIXTURES]` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/(view)/preview/typeset/layout.tsx:43— `PARAMS_STYLE` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/layout.tsx:88— `DOCS_SIDEBAR_SCROLL_RESTORE_SCRIPT` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/app/layout.tsx:93— ``
try {
if (localStorage.theme === 'dark' || ((!('theme' in localStorage) || localStora…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/components/block-viewer.tsx:359— `file?.highlightedContent??""` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:73— `chart.highlightedCode` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:113— `highlightedCode` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/components/directory-list.tsx:237— `registry.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/v4/components/docs-base-switcher.tsx:43— `activeBase.meta.logo` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:95— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:95— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:95— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:95— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
TodoComment packages/tests/src/tests/init.test.ts:728— // TODO: Revisit --force behavior. Currently it only skips backup merge, — 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/shadcn/src/utils/updaters/update-tailwind-content.ts:55— // TODO: maybe we do need to traverse the default export? — 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/registry/src/updaters/update-tailwind-config.ts:217— // TODO: maybe we do need to traverse the default export? — 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/shadcn/src/styles/transform-style-map.ts:18— // TODO: all cn-* classes to be allowedlisted. — 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/shadcn/src/commands/init.ts:775— // TODO: fix this in ensureRegistriesInConfig. — 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/shadcn/src/commands/search.ts:32— // TODO: We're duplicating logic for shadowConfig here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/registry/src/env-helpers.ts:9— // TODO: abstract this to a more generic function. — 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/registry/src/get-config.ts:105— // TODO: Make this configurable. — 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/registry/src/get-config.ts:311— // TODO: Cache this call. — 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/registry/src/updaters/update-css-vars.ts:160— // TODO: Fix typecheck. — 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/registry/src/updaters/update-files.ts:148— // TODO: revisit this when we implement utils transform instead of override. — 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/registry/src/updaters/update-files.ts:216— // TODO: figure out if we always want this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/registry/src/registry/builder.ts:48— // TODO: I don't like this here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/registry/src/registry/resolve-file-imports.ts:171— // TODO (shadcn): fix this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/registry/src/registry/resolver.ts:559— // TODO: Move this to the registry i.e registry:theme. — 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/registry/src/registry/schema.ts:96— // TODO: type the key. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/use-render/index.ts:3— // TODO: Replace if base-ui useRender is published as a package. — 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 apps/v4/lib/registry.ts:165— // TODO: remove when we migrate to new registry. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Swallowed exception (empty catch) packages/shadcn/src/templates/create-template.ts:316— 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/shadcn/src/commands/mcp.ts:250— 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/shadcn/src/commands/search.ts:119— 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/shadcn/src/commands/view.ts:54— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/shadcn/scripts/check-registry-published.mjs:22— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/registry/src/get-monorepo-info.ts:33— 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/registry/src/get-monorepo-info.ts:147— 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/registry/src/registry/resolver.ts:512— 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) apps/v4/registry/bases/radix/ui/code-block.tsx:118— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/registry/bases/radix/hooks/use-highlighted-code.ts:23— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/registry/bases/base/ui/code-block.tsx:118— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/registry/bases/base/hooks/use-highlighted-code.ts:23— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/registry/bases/aria/ui/code-block.tsx:118— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/registry/bases/aria/hooks/use-highlighted-code.ts:23— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/v4/lib/changelog.ts:30— 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) apps/v4/hooks/use-layout.tsx:30— 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) apps/v4/components/docs-sidebar.tsx:87— 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) apps/v4/app/(app)/(typeset)/lib/search-params.ts:102— 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.
AC2 · Forms & labels· <Slider> field component without a label · ×16
<Slider> field component without a label apps/v4/app/(app)/(styles)/sera/media-library-table/components/filter-library.tsx:182— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:104— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:129— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:153— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/aria/blocks/preview-02/cards/kitchen-island.tsx:177— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/aria/blocks/preview-02/cards/roller-shades.tsx:42— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/base/blocks/preview-02/cards/kitchen-island.tsx:102— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/base/blocks/preview-02/cards/kitchen-island.tsx:127— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/base/blocks/preview-02/cards/kitchen-island.tsx:151— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/base/blocks/preview-02/cards/kitchen-island.tsx:175— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/base/blocks/preview-02/cards/roller-shades.tsx:42— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/radix/blocks/preview-02/cards/kitchen-island.tsx:103— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/radix/blocks/preview-02/cards/kitchen-island.tsx:126— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/radix/blocks/preview-02/cards/kitchen-island.tsx:148— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/radix/blocks/preview-02/cards/kitchen-island.tsx:170— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label apps/v4/registry/bases/radix/blocks/preview-02/cards/roller-shades.tsx:42— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Focus outline removed inline apps/v4/app/(app)/(styles)/sera/media-library/components/asset-grid.tsx:119— <button> 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 apps/v4/registry/bases/aria/ui/attachment.tsx:185— <button> 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 apps/v4/registry/bases/aria/ui/code-block.tsx:161— <pre> 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 apps/v4/registry/bases/aria/ui/native-select.tsx:24— <select> 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 apps/v4/registry/bases/base/ui/code-block.tsx:161— <pre> 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 apps/v4/registry/bases/base/ui/native-select.tsx:24— <select> 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 apps/v4/registry/bases/base/ui/textarea.tsx:6— <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).
Focus outline removed inline apps/v4/registry/bases/radix/ui/code-block.tsx:161— <pre> 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 apps/v4/registry/bases/radix/ui/input.tsx:6— <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 apps/v4/registry/bases/radix/ui/native-select.tsx:24— <select> 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 apps/v4/registry/bases/radix/ui/textarea.tsx:6— <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).
Focus outline removed inline apps/v4/registry/new-york-v4/ui/input.tsx:6— <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 apps/v4/registry/new-york-v4/ui/native-select.tsx:15— <select> 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 apps/v4/registry/new-york-v4/ui/textarea.tsx:6— <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).
Hotspot: packages/shadcn/src/commands/init.ts packages/shadcn/src/commands/init.ts:610— packages/shadcn/src/commands/init.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in init.runInit at line 610. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/shadcn/src/commands/init.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/registry/src/add-components.ts packages/registry/src/add-components.ts:148— packages/registry/src/add-components.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in add-components.addWorkspaceComponents at line 148. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/registry/src/add-components.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/helpers/src/core/chat.ts packages/helpers/src/core/chat.ts:139— packages/helpers/src/core/chat.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in chat.createChatRuntime at line 139. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/helpers/src/core/chat.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:263— REDACTED changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in update-fonts.transformLayoutFonts at line 263. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04: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/registry/src/registry/search.ts packages/registry/src/registry/search.ts:93— packages/registry/src/registry/search.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in search.searchRegistriesWithContext at line 93. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/registry/src/registry/search.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/mcp/index.ts packages/shadcn/src/mcp/index.ts:197— packages/shadcn/src/mcp/index.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in index.handleCallTool at line 197. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/shadcn/src/mcp/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/v4/lib/registry-health/monitor.ts apps/v4/lib/registry-health/monitor.ts:476— apps/v4/lib/registry-health/monitor.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in monitor.runRegistryMonitor at line 476. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- apps/v4/lib/registry-health/monitor.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/registry/src/transformers/transform-menu.ts packages/registry/src/transformers/transform-menu.ts:18— packages/registry/src/transformers/transform-menu.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in transform-menu.transformMenu at line 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/registry/src/transformers/transform-menu.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/shadcn/src/migrations/migrate-radix.ts packages/shadcn/src/migrations/migrate-radix.ts:101— packages/shadcn/src/migrations/migrate-radix.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in migrate-radix.migrateRadix at line 101. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/shadcn/src/migrations/migrate-radix.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/migrations/migrate-rtl.ts packages/shadcn/src/migrations/migrate-rtl.ts:21— packages/shadcn/src/migrations/migrate-rtl.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in migrate-rtl.migrateRtl at line 21. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/shadcn/src/migrations/migrate-rtl.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/registry/src/transformers/transform-icons.ts packages/registry/src/transformers/transform-icons.ts:36— packages/registry/src/transformers/transform-icons.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in transform-icons.transformIcons 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/registry/src/transformers/transform-icons.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/helpers/src/ai-sdk/format.ts packages/helpers/src/ai-sdk/format.ts:26— packages/helpers/src/ai-sdk/format.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in format.createAiSdkFormat at line 26. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/helpers/src/ai-sdk/format.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/helpers/src/ai-sdk/parts.ts packages/helpers/src/ai-sdk/parts.ts:117— packages/helpers/src/ai-sdk/parts.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in parts.materializeParts at line 117. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/helpers/src/ai-sdk/parts.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/helpers/src/core/lower.ts packages/helpers/src/core/lower.ts:81— packages/helpers/src/core/lower.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in lower.lowerEvents at line 81. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:29:27 +04:00' --until='2026-10-26 12:29:27 +04:00' --full-history --no-merges -- packages/helpers/src/core/lower.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.
AC3 · Page structure· Page without a main landmark · ×7
Page without a main landmark templates/astro-monorepo/apps/web/src/pages/index.astro:6— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/next-app/app/layout.tsx:22— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/next-monorepo/apps/web/app/layout.tsx:22— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/react-router-app/app/root.tsx:15— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/react-router-monorepo/apps/web/app/root.tsx:15— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/start-app/src/routes/__root.tsx:39— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark templates/start-monorepo/apps/web/src/routes/__root.tsx:37— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Boundary violation [package:third-party-deep-import] packages/registry/src/updaters/update-css-vars.ts:12— packages/registry/src/updaters/update-css-vars.ts:12 imports postcss/lib/at-rule, 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/registry/src/updaters/update-css-vars.ts:13— packages/registry/src/updaters/update-css-vars.ts:13 imports postcss/lib/root, 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/registry/src/updaters/update-css-vars.ts:14— packages/registry/src/updaters/update-css-vars.ts:14 imports postcss/lib/rule, 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/registry/src/updaters/update-css.ts:15— packages/registry/src/updaters/update-css.ts:15 imports postcss/lib/at-rule, 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/registry/src/updaters/update-css.ts:16— packages/registry/src/updaters/update-css.ts:16 imports postcss/lib/declaration, 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/registry/src/updaters/update-css.ts:17— packages/registry/src/updaters/update-css.ts:17 imports postcss/lib/root, 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/registry/src/updaters/update-css.ts:18— packages/registry/src/updaters/update-css.ts:18 imports postcss/lib/rule, 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.
AC2 · Forms & labels· <Select> field component without a label · ×6
<Select> field component without a label apps/v4/app/(app)/(styles)/sera/edit-article/components/editor-workspace.tsx:271— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label apps/v4/app/(app)/(typeset)/components/docs-panel.tsx:210— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label apps/v4/components/color-format-selector.tsx:31— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label apps/v4/components/language-selector.tsx:96— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label apps/v4/registry/bases/base/blocks/preview/cards/invite-team.tsx:46— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label apps/v4/registry/bases/radix/blocks/preview/cards/invite-team.tsx:46— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <Textarea> field component without a label · ×5
<Textarea> field component without a label apps/v4/app/(app)/(root)/cards/ui-elements.tsx:80— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label apps/v4/app/(app)/(styles)/sera/edit-article/components/editor-workspace.tsx:318— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label apps/v4/registry/bases/aria/blocks/preview/cards/ui-elements.tsx:115— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label apps/v4/registry/bases/base/blocks/preview/cards/ui-elements.tsx:117— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label apps/v4/registry/bases/radix/blocks/preview/cards/ui-elements.tsx:117— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
P12 · CI test-gate honesty· Workspace package's tests never run by CI · ×5
Workspace package's tests never run by CI apps/v4/package.json:1— `apps/v4` is a workspace package with 138 test(s) in 17 file(s) (e.g. `apps/v4/registry/calendar.test.ts`, `apps/v4/registry/config.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/registry/package.json:64— `packages/registry` is a workspace package with 1715 test(s) in 76 file(s) (e.g. `packages/registry/src/add-components.test.ts`, `packages/registry/src/add-components.workspace.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/registry/test/fixtures/frameworks/remix-indie-stack/package.json:15— `packages/registry/test/fixtures/frameworks/remix-indie-stack` is a workspace package with 2 test(s) in 1 file(s) (e.g. `packages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/shadcn/package.json:84— `packages/shadcn` is a workspace package with 482 test(s) in 35 file(s) (e.g. `packages/shadcn/src/commands/add.test.ts`, `packages/shadcn/src/commands/apply.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/tests/package.json:8— `packages/tests` is a workspace package with 207 test(s) in 8 file(s) (e.g. `packages/tests/src/tests/add-project-config.test.ts`, `packages/tests/src/tests/add.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
AC2 · Forms & labels· <RadioGroup> field component without a label · ×4
<RadioGroup> field component without a label REDACTED:612— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<RadioGroup> field component without a label apps/v4/registry/bases/aria/blocks/preview/cards/ui-elements.tsx:124— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<RadioGroup> field component without a label apps/v4/registry/bases/base/blocks/preview/cards/ui-elements.tsx:126— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<RadioGroup> field component without a label apps/v4/registry/bases/radix/blocks/preview/cards/ui-elements.tsx:126— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <DatePicker> field component without a label · ×4
<DatePicker> field component without a label apps/v4/registry/bases/aria/blocks/sidebar-12/components/app-sidebar.tsx:51— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<DatePicker> field component without a label apps/v4/registry/bases/base/blocks/sidebar-12/components/app-sidebar.tsx:51— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<DatePicker> field component without a label apps/v4/registry/bases/radix/blocks/sidebar-12/components/app-sidebar.tsx:51— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<DatePicker> field component without a label apps/v4/registry/new-york-v4/blocks/sidebar-12/components/app-sidebar.tsx:49— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
chart.ChartTooltipContent (cyclomatic 22) REDACTED:118— chart.ChartTooltipContent has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cyclomatic 22) REDACTED:118— chart.ChartTooltipContent has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cyclomatic 22) REDACTED:118— chart.ChartTooltipContent has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cyclomatic 22) REDACTED:118— chart.ChartTooltipContent has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 201, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
No assertions: should allow you to register and login packages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.ts:8— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should allow you to make a note packages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: narrows the continuation toolCall by name packages/helpers/src/ai-sdk/chat.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: preserves the native message type through get and next packages/helpers/src/ai-sdk/chat.test.ts:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
chart.ChartTooltipContent (cognitive 22) REDACTED:118— chart.ChartTooltipContent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 22) REDACTED:118— chart.ChartTooltipContent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 22) REDACTED:118— chart.ChartTooltipContent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 22) REDACTED:118— chart.ChartTooltipContent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 201, 148). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AC2 · Forms & labels· <Combobox> field component without a label · ×3
<Combobox> field component without a label apps/v4/app/(app)/(styles)/sera/media-library-table/components/filter-library.tsx:192— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Combobox> field component without a label apps/v4/registry/bases/base/blocks/preview/cards/assign-issue.tsx:76— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Combobox> field component without a label apps/v4/registry/bases/radix/blocks/preview/cards/assign-issue.tsx:76— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
live-waveform.LiveWaveform (cyclomatic 75) apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cyclomatic complexity 75 (threshold 15). Most of this is not in the body itself: 6 of the 75 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). 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.
live-waveform.LiveWaveform (cyclomatic 75) apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cyclomatic complexity 75 (threshold 15). Most of this is not in the body itself: 6 of the 75 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). 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.
live-waveform.LiveWaveform (cyclomatic 75) apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cyclomatic complexity 75 (threshold 15). Most of this is not in the body itself: 6 of the 75 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Deprecated: eslint apps/v4/package.json:119— eslint 9.26.0, declared in apps/v4/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:65— eslint 9.26.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: puppeteer REDACTED:74— puppeteer 23.11.1, declared in REDACTED, is marked deprecated by its publisher: "< 24.15.0 is no longer supported". Replace it with the package or version that message names, or record why this one must stay.
live-waveform.LiveWaveform (cognitive 136) apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cognitive complexity 136 (threshold 15). Drivers by points: if/else 42 (74 pts), boolean chains 23, loops 7 (22 pts), ternaries 8 (16 pts), error handling 1 (nesting depth added 55). Most of this is not in the body itself: 5 of the 136 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). 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.
live-waveform.LiveWaveform (cognitive 136) apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cognitive complexity 136 (threshold 15). Drivers by points: if/else 42 (74 pts), boolean chains 23, loops 7 (22 pts), ternaries 8 (16 pts), error handling 1 (nesting depth added 55). Most of this is not in the body itself: 5 of the 136 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). 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.
live-waveform.LiveWaveform (cognitive 136) apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:17— live-waveform.LiveWaveform has cognitive complexity 136 (threshold 15). Drivers by points: if/else 42 (74 pts), boolean chains 23, loops 7 (22 pts), ternaries 8 (16 pts), error handling 1 (nesting depth added 55). Most of this is not in the body itself: 5 of the 136 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 310, 107, 103, …). 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.
bar-visualizer.BarVisualizerComponent (cognitive 22) apps/v4/registry/bases/aria/blocks/preview/cards/bar-visualizer.tsx:308— bar-visualizer.BarVisualizerComponent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 353, 337, 386, …). 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.
bar-visualizer.BarVisualizerComponent (cognitive 22) apps/v4/registry/bases/base/blocks/preview/cards/bar-visualizer.tsx:308— bar-visualizer.BarVisualizerComponent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 353, 337, 386, …). 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.
bar-visualizer.BarVisualizerComponent (cognitive 22) apps/v4/registry/bases/radix/blocks/preview/cards/bar-visualizer.tsx:280— bar-visualizer.BarVisualizerComponent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 323, 307, 356, …). 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.
Off the main sequence: @shadcn/helpers — @shadcn/helpers: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @shadcn/react — @shadcn/react: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @shadcn/registry — @shadcn/registry: abstractness 0.01, instability 0.00, distance 0.99 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Complex function rafId (cyclomatic 29, cognitive 56) apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:310— rafId has cyclomatic complexity 29 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function rafId (cyclomatic 29, cognitive 56) apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:310— rafId has cyclomatic complexity 29 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function rafId (cyclomatic 29, cognitive 56) apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:310— rafId has cyclomatic complexity 29 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Dead file (~66 LoC) apps/v4/app/(app)/(create)/components/share-button.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~66 LoC) apps/v4/hooks/use-search-registry.ts— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/directory-list.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~66 LoC) packages/shadcn/src/preflights/preflight-registry.ts— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/shadcn/src/commands/registry/build.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
IC1 · Incompleteness & stubs· Guard cannot change the result · ×2
Guard cannot change the result — returns what the code already falls through to apps/v4/components/message-parts.tsx:544— The guard above `return "custom";` also returns `"custom"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to packages/registry/src/registry/resolve-file-imports.ts:247— The guard above `return "registry:component";` also returns `"registry:component"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Duplicated block (231 lines × 2 locations) apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20— apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/aria/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (231 lines × 2 locations) apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20— apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/base/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Dead file (~132 LoC) apps/v4/components/cards/activity-goal.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~132 LoC) apps/v4/components/cards/stats.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~65 LoC) apps/v4/components/component-wrapper.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~65 LoC) apps/v4/components/docs-breadcrumb.tsx— no import path from any entry point (890 application, 25 tooling, 164 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
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: StarsCount apps/v4/components/github-link.tsx:22— `StarsCount` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getRegistryItemFile REDACTED:571— `getRegistryItemFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Swallowed exception (caught, then discarded) packages/registry/src/get-project-info.ts:392— `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/registry/src/registry/resolve-file-imports.ts:146— `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 1220 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
chat.createChatRuntime (cyclomatic 79) packages/helpers/src/core/chat.ts:139— chat.createChatRuntime has cyclomatic complexity 79 (threshold 15). Of this number, 25 points are the body's own statements and 54 belong to 16 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.
init.init (cyclomatic 75) packages/shadcn/src/commands/init.ts:170— init.init has cyclomatic complexity 75 (threshold 15). Of this number, 73 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.
update-css.updateCssPlugin.Once (cyclomatic 73) packages/registry/src/updaters/update-css.ts:112— update-css.updateCssPlugin.Once has cyclomatic complexity 73 (threshold 15). Of this number, 49 points are the body's own statements and 24 belong to 13 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.
update-files.updateFiles (cyclomatic 59) packages/registry/src/updaters/update-files.ts:50— update-files.updateFiles has cyclomatic complexity 59 (threshold 15). Of this number, 58 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.
indentation.convertNode (cyclomatic 49) packages/registry/src/codemod/indentation.ts:809— indentation.convertNode has cyclomatic complexity 49 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
command-menu.CommandMenu (cyclomatic 45) apps/v4/components/command-menu.tsx:42— command-menu.CommandMenu has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 10 of the 45 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 379, 395, 271, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
add.add (cyclomatic 40) packages/shadcn/src/commands/add.ts:77— add.add has cyclomatic complexity 40 (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.
init.runInit (cyclomatic 38) packages/shadcn/src/commands/init.ts:610— init.runInit has cyclomatic complexity 38 (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.
network.isForbiddenIpv4 (cyclomatic 37) apps/v4/lib/registry-health/network.ts:102— network.isForbiddenIpv4 has cyclomatic complexity 37 (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.
use-questionnaire-root.useQuestionnaireRoot.handleKeyDown (cyclomatic 36) packages/react/src/questionnaire/use-questionnaire-root.ts:361— use-questionnaire-root.useQuestionnaireRoot.handleKeyDown has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
design-system-provider.DesignSystemProvider (cyclomatic 35) apps/v4/app/(app)/(create)/components/design-system-provider.tsx:67— design-system-provider.DesignSystemProvider has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 155, 143, 194, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
get-project-info.stripJsonCommentsAndTrailingCommas (cyclomatic 33) packages/registry/src/get-project-info.ts:408— get-project-info.stripJsonCommentsAndTrailingCommas has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolver.resolveRegistryTree (cyclomatic 32) packages/registry/src/registry/resolver.ts:147— resolver.resolveRegistryTree has cyclomatic complexity 32 (threshold 15). Of this number, 25 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
add-components.addWorkspaceComponents (cyclomatic 31) packages/registry/src/add-components.ts:148— add-components.addWorkspaceComponents has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-questionnaire-item.useQuestionnaireItem (cyclomatic 30) packages/react/src/questionnaire/use-questionnaire-item.ts:35— use-questionnaire-item.useQuestionnaireItem has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
transform-rtl.applyRtlMapping (cyclomatic 30) packages/registry/src/transformers/transform-rtl.ts:128— transform-rtl.applyRtlMapping has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to one function literal inside it that branches (line 131). 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.
migrate-icons.migrateIcons (cyclomatic 29) packages/shadcn/src/migrations/migrate-icons.ts:56— migrate-icons.migrateIcons has cyclomatic complexity 29 (threshold 15). Of this number, 27 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.
parts.eventsFromParts (cyclomatic 28) packages/helpers/src/ai-sdk/parts.ts:273— parts.eventsFromParts has cyclomatic complexity 28 (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.
use-questionnaire-root.useQuestionnaireRoot (cyclomatic 28) packages/react/src/questionnaire/use-questionnaire-root.ts:38— use-questionnaire-root.useQuestionnaireRoot has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 198, 72, 113, …). 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.
monitor.runRegistryMonitor (cyclomatic 27) apps/v4/lib/registry-health/monitor.ts:476— monitor.runRegistryMonitor has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 537). 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.
migrate-base-color.migrateBaseColor (cyclomatic 27) packages/shadcn/src/migrations/migrate-base-color.ts:33— migrate-base-color.migrateBaseColor has cyclomatic complexity 27 (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.
group-chat.GroupChat (cyclomatic 26) apps/v4/registry/bases/radix/blocks/preview-03/cards/group-chat.tsx:137— group-chat.GroupChat has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 268, onSubmit, a function literal at line 316, …). 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.
package-imports.getAliasScore (cyclomatic 26) packages/registry/src/package-imports.ts:115— package-imports.getAliasScore 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.
transform-import.updateImportAliases (cyclomatic 26) packages/registry/src/transformers/transform-import.ts:193— transform-import.updateImportAliases 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.
update-css.processRule (cyclomatic 26) packages/registry/src/updaters/update-css.ts:486— update-css.processRule has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 5 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.
project-form.ProjectForm (cyclomatic 25) REDACTED:121— project-form.ProjectForm has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 149, 183, 209, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
message-parts.getStructuralPartKind (cyclomatic 25) apps/v4/components/message-parts.tsx:487— message-parts.getStructuralPartKind has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
network.isForbiddenIpv6 (cyclomatic 25) apps/v4/lib/registry-health/network.ts:127— network.isForbiddenIpv6 has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
parts.materializeParts (cyclomatic 25) packages/helpers/src/ai-sdk/parts.ts:117— parts.materializeParts has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.handleCallTool (cyclomatic 25) packages/shadcn/src/mcp/index.ts:197— index.handleCallTool has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate-icons.migrateIconsFileWithReport (cyclomatic 25) packages/shadcn/src/migrations/migrate-icons.ts:300— migrate-icons.migrateIconsFileWithReport has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
indentation.nodeWillIndentChild (cyclomatic 24) packages/registry/src/codemod/indentation.ts:530— indentation.nodeWillIndentChild has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
resolve-file-imports.recursivelyResolveFileImports (cyclomatic 24) packages/registry/src/registry/resolve-file-imports.ts:52— resolve-file-imports.recursivelyResolveFileImports has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolver.resolveDependenciesRecursively (cyclomatic 24) packages/registry/src/registry/resolver.ts:384— resolver.resolveDependenciesRecursively has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
preflight-init.preFlightInit (cyclomatic 24) packages/shadcn/src/preflights/preflight-init.ts:17— preflight-init.preFlightInit has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parts.materializeParts (cyclomatic 23) packages/helpers/src/tanstack-ai/parts.ts:131— parts.materializeParts has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
transform-import.getImportStringLiterals (cyclomatic 23) packages/registry/src/transformers/transform-import.ts:87— transform-import.getImportStringLiterals has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (collect, a function literal at line 90). 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.
directory-list.DirectoryListContent (cyclomatic 22) apps/v4/components/directory-list.tsx:175— directory-list.DirectoryListContent has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 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.
comma-lists.insertIntoCommaSeparatedNodes (cyclomatic 22) packages/registry/src/codemod/comma-lists.ts:119— comma-lists.insertIntoCommaSeparatedNodes has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 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.
search.searchRegistriesWithContext (cyclomatic 22) packages/registry/src/registry/search.ts:93— search.searchRegistriesWithContext has cyclomatic complexity 22 (threshold 15). Of this number, 20 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.
resolver.topologicalSortRegistryItems (cyclomatic 22) packages/registry/src/registry/resolver.ts:679— resolver.topologicalSortRegistryItems has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 728, 706, 723, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
add.addRegistriesToConfig (cyclomatic 22) packages/shadcn/src/commands/registry/add.ts:73— add.addRegistriesToConfig 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.
search.search (cyclomatic 22) packages/shadcn/src/commands/search.ts:56— search.search has cyclomatic complexity 22 (threshold 15). Of this number, 20 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.
bindings.collapseCanonicalWrappers (cyclomatic 22) packages/shadcn/src/migrations/cn/bindings.ts:15— bindings.collapseCanonicalWrappers has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
preview.Preview (cyclomatic 21) apps/v4/app/(app)/(create)/components/preview.tsx:39— preview.Preview has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 79, 52, 48). 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.
rehype.rehypeComponent (cyclomatic 21) apps/v4/lib/rehype.ts:72— rehype.rehypeComponent has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 128, 77, 150). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
transform-tw-prefix.getClassNameStrings (cyclomatic 21) packages/registry/src/transformers/transform-tw-prefix.ts:70— transform-tw-prefix.getClassNameStrings 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.
specifiers.migrateEsmImports (cyclomatic 21) packages/shadcn/src/migrations/cn/specifiers.ts:45— specifiers.migrateEsmImports 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.
migrate-radix.migrateRadixFile (cyclomatic 21) packages/shadcn/src/migrations/migrate-radix.ts:272— migrate-radix.migrateRadixFile has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 389, 358, 349, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-random.useRandom.randomizeTrueRandom (cyclomatic 20) apps/v4/app/(app)/(create)/hooks/use-random.tsx:54— use-random.useRandom.randomizeTrueRandom has cyclomatic complexity 20 (threshold 15). Of this number, 19 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.
monitor.recordIndexObservation (cyclomatic 20) apps/v4/lib/registry-health/monitor.ts:227— monitor.recordIndexObservation has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-history.HistoryProvider (cyclomatic 19) apps/v4/app/(app)/(create)/hooks/use-history.tsx:41— use-history.HistoryProvider has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 129, 62, 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.
use-history.TypesetHistoryProvider (cyclomatic 19) apps/v4/app/(app)/(typeset)/hooks/use-history.tsx:43— use-history.TypesetHistoryProvider has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 133, 67, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-layout.Layout (cyclomatic 19) apps/v4/hooks/use-layout.tsx:43— use-layout.Layout has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 51, 76, 113, …). 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.
parts.eventsFromParts (cyclomatic 19) packages/helpers/src/tanstack-ai/parts.ts:239— parts.eventsFromParts has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-message-scroller-controller.useMessageScrollerController.handleContentChange::reconcileScrollPosition (cyclomatic 19) packages/react/src/message-scroller/use-message-scroller-controller.ts:401— use-message-scroller-controller.useMessageScrollerController.handleContentChange::reconcileScrollPosition has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
collection.getCollectionRegistrationWarnings (cyclomatic 19) packages/react/src/questionnaire/collection.ts:118— collection.getCollectionRegistrationWarnings has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-questionnaire-choice.useQuestionnaireChoice (cyclomatic 19) packages/react/src/questionnaire/use-questionnaire-choice.ts:15— use-questionnaire-choice.useQuestionnaireChoice has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
update-fonts.updateHtmlClassName (cyclomatic 19) REDACTED:568— update-fonts.updateHtmlClassName has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
diff.diff (cyclomatic 19) packages/shadcn/src/commands/diff.ts:51— diff.diff has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 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.
build.buildRegistry (cyclomatic 19) packages/shadcn/src/commands/registry/build.ts:54— build.buildRegistry has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
transform-style-map.applyToCvaCalls (cyclomatic 19) packages/shadcn/src/styles/transform-style-map.ts:118— transform-style-map.applyToCvaCalls has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 123, 161, 171, …). 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.
transform-style-map.applyClassesToElement (cyclomatic 19) packages/shadcn/src/styles/transform-style-map.ts:390— transform-style-map.applyClassesToElement has cyclomatic complexity 19 (threshold 15). Of this number, 16 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.
message-parts.getMessagePartComponent (cyclomatic 18) apps/v4/components/message-parts.tsx:301— message-parts.getMessagePartComponent 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.
is-safe-target.isSafeTarget (cyclomatic 18) packages/registry/src/is-safe-target.ts:3— is-safe-target.isSafeTarget has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
specifiers.migrateCommonJsRequires (cyclomatic 18) packages/shadcn/src/migrations/cn/specifiers.ts:201— specifiers.migrateCommonJsRequires has cyclomatic complexity 18 (threshold 15). Of this number, 17 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.
menu-picker.MenuColorPicker (cyclomatic 17) apps/v4/app/(app)/(create)/components/menu-picker.tsx:48— menu-picker.MenuColorPicker has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 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.
font-picker.FontPicker (cyclomatic 17) apps/v4/app/(app)/(typeset)/components/font-picker.tsx:21— font-picker.FontPicker has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
docs-sidebar.DocsSidebar (cyclomatic 17) apps/v4/components/docs-sidebar.tsx:120— docs-sidebar.DocsSidebar 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 128, 193, 225, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
page-tree.getPagesFromFolder (cyclomatic 17) REDACTED:23— page-tree.getPagesFromFolder has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
score.deriveStatus (cyclomatic 17) apps/v4/lib/registry-health/score.ts:237— score.deriveStatus 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.
use-questionnaire-input.useQuestionnaireInput (cyclomatic 17) packages/react/src/questionnaire/use-questionnaire-input.ts:13— use-questionnaire-input.useQuestionnaireInput has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
use-questionnaire-item.useQuestionnaireItem.moveAnswerFocus (cyclomatic 17) packages/react/src/questionnaire/use-questionnaire-item.ts:386— use-questionnaire-item.useQuestionnaireItem.moveAnswerFocus has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
update-css-vars.updateThemePlugin.Once (cyclomatic 17) packages/registry/src/updaters/update-css-vars.ts:395— update-css-vars.updateThemePlugin.Once has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
apply.apply (cyclomatic 17) packages/shadcn/src/commands/apply.ts:86— apply.apply 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.
apply.syncApplyWorkspaceConfigs (cyclomatic 17) packages/shadcn/src/commands/apply.ts:438— apply.syncApplyWorkspaceConfigs 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.
migrate-icons.rewriteIconUsages (cyclomatic 17) packages/shadcn/src/migrations/migrate-icons.ts:556— migrate-icons.rewriteIconUsages 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.
migrate-radix.migrateRadix (cyclomatic 17) packages/shadcn/src/migrations/migrate-radix.ts:101— migrate-radix.migrateRadix 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.
dry-run.processFiles (cyclomatic 17) packages/shadcn/src/utils/dry-run.ts:132— dry-run.processFiles has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
network.fetchOnce (cyclomatic 16) apps/v4/lib/registry-health/network.ts:339— network.fetchOnce 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.
geometry.getMessageScrollerVisibilityState (cyclomatic 16) packages/react/src/message-scroller/geometry.ts:37— geometry.getMessageScrollerVisibilityState 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.
update-css-vars.updateCssVarsPluginV4.Once (cyclomatic 16) packages/registry/src/updaters/update-css-vars.ts:296— update-css-vars.updateCssVarsPluginV4.Once 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 6 function literals inside it that branch (lines 350, 297, 303, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
update-files.resolveModuleByProbablePath (cyclomatic 16) packages/registry/src/updaters/update-files.ts:559— update-files.resolveModuleByProbablePath has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, 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.
update-files.toAliasedImport (cyclomatic 16) packages/registry/src/updaters/update-files.ts:622— update-files.toAliasedImport has cyclomatic complexity 16 (threshold 15). Of this number, 10 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.
update-fonts.transformLayoutFonts (cyclomatic 16) REDACTED:263— update-fonts.transformLayoutFonts 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.
migrate-rtl.migrateRtl (cyclomatic 16) packages/shadcn/src/migrations/migrate-rtl.ts:21— migrate-rtl.migrateRtl has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
resolve.resolveHeadingFont (cyclomatic 16) packages/shadcn/src/preset/resolve.ts:339— resolve.resolveHeadingFont 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.
Skipped test: should override existing components.json when using --force packages/tests/src/tests/init.test.ts:730— Skipped — switched off by it.skip
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/registry/test/fixtures/frameworks/remix-indie-stack packages/registry/test/fixtures/frameworks/remix-indie-stack/cypress/e2e/smoke.cy.ts:8— No conventional assertion call was detected in 2 of 2 tests in `packages/registry/test/fixtures/frameworks/remix-indie-stack` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×1
One package at two majors across the workspace: zod — `zod` is maintained at 2 different major versions inside this one repository — major 3 in apps/v4/package.json; major 4 in packages/registry/package.json, packages/shadcn/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
update-css.updateCssPlugin.Once (cognitive 183) packages/registry/src/updaters/update-css.ts:112— update-css.updateCssPlugin.Once has cognitive complexity 183 (threshold 15). Drivers by points: if/else 40 (136 pts), boolean chains 21, loops 4 (18 pts), ternaries 1 (8 pts) (nesting depth added 117). Of this number, 157 points are the body's own statements and 26 belong to 13 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.
init.init (cognitive 115) packages/shadcn/src/commands/init.ts:170— init.init has cognitive complexity 115 (threshold 15). Drivers by points: if/else 46 (87 pts), boolean chains 19, loops 1 (4 pts), error handling 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 46). Of this number, 113 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.
update-files.updateFiles (cognitive 105) packages/registry/src/updaters/update-files.ts:50— update-files.updateFiles has cognitive complexity 105 (threshold 15). Drivers by points: if/else 33 (68 pts), loops 5 (13 pts), ternaries 7 (13 pts), boolean chains 11 (nesting depth added 49). 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.
chat.createChatRuntime (cognitive 90) packages/helpers/src/core/chat.ts:139— chat.createChatRuntime has cognitive complexity 90 (threshold 15). Drivers by points: if/else 32 (45 pts), ternaries 18 (22 pts), boolean chains 15, loops 8 (nesting depth added 17). Of this number, 25 points are the body's own statements and 65 belong to 16 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.
get-project-info.stripJsonCommentsAndTrailingCommas (cognitive 75) packages/registry/src/get-project-info.ts:408— get-project-info.stripJsonCommentsAndTrailingCommas has cognitive complexity 75 (threshold 15). Drivers by points: if/else 14 (41 pts), loops 7 (24 pts), boolean chains 10 (nesting depth added 44). 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.
resolver.resolveDependenciesRecursively (cognitive 67) packages/registry/src/registry/resolver.ts:384— resolver.resolveDependenciesRecursively has cognitive complexity 67 (threshold 15). Drivers by points: if/else 14 (38 pts), ternaries 4 (20 pts), boolean chains 4, error handling 1 (4 pts), loops 1 (nesting depth added 43). 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.
parts.eventsFromParts (cognitive 62) packages/helpers/src/ai-sdk/parts.ts:273— parts.eventsFromParts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 19 (46 pts), ternaries 4 (12 pts), boolean chains 3, loops 1 (nesting depth added 35). 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.
init.runInit (cognitive 60) packages/shadcn/src/commands/init.ts:610— init.runInit has cognitive complexity 60 (threshold 15). Drivers by points: if/else 27 (46 pts), ternaries 6, boolean chains 5, loops 1 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
monitor.runRegistryMonitor (cognitive 57) apps/v4/lib/registry-health/monitor.ts:476— monitor.runRegistryMonitor has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 9 (25 pts), if/else 10 (23 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 31). Most of this is not in the body itself: 10 of the 57 points are its own statements and the rest belongs to one function literal inside it that branches (line 537). 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.
resolver.resolveRegistryTree (cognitive 56) packages/registry/src/registry/resolver.ts:147— resolver.resolveRegistryTree has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (39 pts), loops 4 (9 pts), boolean chains 7, ternaries 1 (nesting depth added 24). Of this number, 49 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update-css.processRule (cognitive 53) packages/registry/src/updaters/update-css.ts:486— update-css.processRule has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (35 pts), ternaries 2 (8 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 31). Of this number, 46 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
transform-tw-prefix.getClassNameStrings (cognitive 52) packages/registry/src/transformers/transform-tw-prefix.ts:70— transform-tw-prefix.getClassNameStrings has cognitive complexity 52 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 7 (19 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-rtl.applyRtlMapping (cognitive 50) packages/registry/src/transformers/transform-rtl.ts:128— transform-rtl.applyRtlMapping has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 6 (20 pts), boolean chains 5, loops 5 (nesting depth added 22). None of this is in the body itself: all 50 points belong to one function literal inside it that branches (line 131). 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.
command-menu.CommandMenu (cognitive 47) apps/v4/components/command-menu.tsx:42— command-menu.CommandMenu has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 17, ternaries 8 (nesting depth added 4). Most of this is not in the body itself: 9 of the 47 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 379, 395, 271, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
migrate-icons.migrateIcons (cognitive 47) packages/shadcn/src/migrations/migrate-icons.ts:56— migrate-icons.migrateIcons has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (30 pts), ternaries 5 (10 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 16). Of this number, 44 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.
specifiers.migrateEsmImports (cognitive 44) packages/shadcn/src/migrations/cn/specifiers.ts:45— specifiers.migrateEsmImports has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (29 pts), ternaries 2 (9 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
resolve-file-imports.recursivelyResolveFileImports (cognitive 43) packages/registry/src/registry/resolve-file-imports.ts:52— resolve-file-imports.recursivelyResolveFileImports has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 3 (7 pts), error handling 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-icons.migrateIconsFileWithReport (cognitive 43) packages/shadcn/src/migrations/migrate-icons.ts:300— migrate-icons.migrateIconsFileWithReport has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 7, ternaries 2 (6 pts), loops 3 (5 pts) (nesting depth added 20). Of this number, 40 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
add.add (cognitive 42) packages/shadcn/src/commands/add.ts:77— add.add has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 17, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build-registry.buildRegistryIndex (cognitive 39) apps/v4/scripts/build-registry.mts:1235— build-registry.buildRegistryIndex has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (21 pts), if/else 5 (14 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 25). Of this number, 35 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.
add-components.addWorkspaceComponents (cognitive 38) packages/registry/src/add-components.ts:148— add-components.addWorkspaceComponents has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 8, loops 5 (8 pts), ternaries 4 (7 pts) (nesting depth added 8). Of this number, 35 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
add.addRegistriesToConfig (cognitive 38) packages/shadcn/src/commands/registry/add.ts:73— add.addRegistriesToConfig has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 5 (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.
collection.getCollectionRegistrationWarnings (cognitive 36) packages/react/src/questionnaire/collection.ts:118— collection.getCollectionRegistrationWarnings has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 4 (7 pts), boolean chains 3 (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.
package-imports.getAliasScore (cognitive 36) packages/registry/src/package-imports.ts:115— package-imports.getAliasScore has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 5, match/switch 1 (nesting depth added 15). 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.
use-questionnaire-root.useQuestionnaireRoot.handleKeyDown (cognitive 35) packages/react/src/questionnaire/use-questionnaire-root.ts:361— use-questionnaire-root.useQuestionnaireRoot.handleKeyDown has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 9, ternaries 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.handleCallTool (cognitive 35) packages/shadcn/src/mcp/index.ts:197— index.handleCallTool has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (31 pts), ternaries 1 (2 pts), error handling 1, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bindings.collapseCanonicalWrappers (cognitive 35) packages/shadcn/src/migrations/cn/bindings.ts:15— bindings.collapseCanonicalWrappers has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 4 (5 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 14). Of this number, 33 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.
design-system-provider.DesignSystemProvider (cognitive 34) apps/v4/app/(app)/(create)/components/design-system-provider.tsx:67— design-system-provider.DesignSystemProvider has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (24 pts), boolean chains 9, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 258, 143, 110, …). 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.
monitor.recordIndexObservation (cognitive 34) apps/v4/lib/registry-health/monitor.ts:227— monitor.recordIndexObservation has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parts.eventsFromParts (cognitive 34) packages/helpers/src/tanstack-ai/parts.ts:239— parts.eventsFromParts has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
group-chat.GroupChat (cognitive 33) apps/v4/registry/bases/radix/blocks/preview-03/cards/group-chat.tsx:137— group-chat.GroupChat has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 5 (10 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (onSubmit, a function literal at line 188, a function literal at line 316, …). 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.
diff.diff (cognitive 33) packages/shadcn/src/commands/diff.ts:51— diff.diff has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 5 (10 pts), ternaries 1 (3 pts), error handling 1 (nesting depth added 15). Of this number, 25 points are the body's own statements and 8 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.
specifiers.migrateCommonJsRequires (cognitive 33) packages/shadcn/src/migrations/cn/specifiers.ts:201— specifiers.migrateCommonJsRequires has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 5, ternaries 1 (4 pts), loops 2 (3 pts) (nesting depth added 15). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
migrate-base-color.migrateBaseColor (cognitive 33) packages/shadcn/src/migrations/migrate-base-color.ts:33— migrate-base-color.migrateBaseColor has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 4 (8 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preflight-init.preFlightInit (cognitive 33) packages/shadcn/src/preflights/preflight-init.ts:17— preflight-init.preFlightInit has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 7, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-icons.rewriteIconUsages (cognitive 32) packages/shadcn/src/migrations/migrate-icons.ts:556— migrate-icons.rewriteIconUsages has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (7 pts), boolean chains 3 (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.
migrate-radix.migrateRadix (cognitive 32) packages/shadcn/src/migrations/migrate-radix.ts:101— migrate-radix.migrateRadix has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (28 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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.
apply.apply (cognitive 31) packages/shadcn/src/commands/apply.ts:86— apply.apply has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 2 (7 pts), error handling 1, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-style-map.applyClassesToElement (cognitive 31) packages/shadcn/src/styles/transform-style-map.ts:390— transform-style-map.applyClassesToElement has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 13). Of this number, 25 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.
use-questionnaire-root.useQuestionnaireRoot (cognitive 30) packages/react/src/questionnaire/use-questionnaire-root.ts:38— use-questionnaire-root.useQuestionnaireRoot has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 8, ternaries 7 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 198, 72, 113, …). 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.
namespaces.resolveRegistryNamespaces (cognitive 30) packages/registry/src/registry/namespaces.ts:8— namespaces.resolveRegistryNamespaces has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-import.updateImportAliases (cognitive 30) packages/registry/src/transformers/transform-import.ts:193— transform-import.updateImportAliases has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 11 (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.
update-css-vars.updateThemePlugin.Once (cognitive 30) packages/registry/src/updaters/update-css-vars.ts:395— update-css-vars.updateThemePlugin.Once has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 13). Of this number, 27 points are the body's own statements and 3 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.
update-fonts.updateHtmlClassName (cognitive 30) REDACTED:568— update-fonts.updateHtmlClassName has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 5, loops 1 (nesting depth added 13). Of this number, 29 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.
network.fetchOnce (cognitive 29) apps/v4/lib/registry-health/network.ts:339— network.fetchOnce has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 3 (6 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (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.
resolver.topologicalSortRegistryItems (cognitive 29) packages/registry/src/registry/resolver.ts:679— resolver.topologicalSortRegistryItems has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 8, loops 1 (nesting depth added 7). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 728, 706, 723, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
create-template.rewriteWorkspaceProtocol (cognitive 29) packages/shadcn/src/templates/create-template.ts:188— create-template.rewriteWorkspaceProtocol has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rehype.rehypeComponent (cognitive 28) apps/v4/lib/rehype.ts:72— rehype.rehypeComponent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 8, error handling 1 (nesting depth added 7). None of this is in the body itself: all 28 points belong to 3 function literals inside it that branch (lines 128, 77, 150). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
build-icons.generateIconMapping (cognitive 28) REDACTED:142— build-icons.generateIconMapping has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (7 pts), ternaries 2 (5 pts), boolean chains 2 (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.
build.buildRegistry (cognitive 28) packages/shadcn/src/commands/registry/build.ts:54— build.buildRegistry has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 5 (9 pts), error handling 2 (4 pts), boolean chains 2 (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.
migrate-rtl.migrateRtl (cognitive 28) packages/shadcn/src/migrations/migrate-rtl.ts:21— migrate-rtl.migrateRtl has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 1 (2 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 10). 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 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.
search.searchRegistriesWithContext (cognitive 27) packages/registry/src/registry/search.ts:93— search.searchRegistriesWithContext has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 9, ternaries 4 (7 pts), loops 1 (nesting depth added 7). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
build-icons.scanIconUsage (cognitive 26) REDACTED:31— build-icons.scanIconUsage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 4 (9 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
comma-lists.insertIntoCommaSeparatedNodes (cognitive 26) packages/registry/src/codemod/comma-lists.ts:119— comma-lists.insertIntoCommaSeparatedNodes has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 4). Of this number, 19 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
update-css-vars.updateCssVarsPluginV4.Once (cognitive 26) packages/registry/src/updaters/update-css-vars.ts:296— update-css-vars.updateCssVarsPluginV4.Once has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 4, ternaries 1 (nesting depth added 7). None of this is in the body itself: all 26 points belong to 6 function literals inside it that branch (lines 350, 303, 297, …). 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.
update-css.processAtRule (cognitive 25) packages/registry/src/updaters/update-css.ts:423— update-css.processAtRule has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 12). Of this number, 21 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.
parts.materializeParts (cognitive 24) packages/helpers/src/ai-sdk/parts.ts:117— parts.materializeParts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), ternaries 2 (6 pts), match/switch 1 (2 pts), loops 1 (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.
update-fonts.transformLayoutFonts (cognitive 24) REDACTED:263— update-fonts.transformLayoutFonts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 2, loops 1, 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.
search.search (cognitive 24) packages/shadcn/src/commands/search.ts:56— search.search has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 5 (7 pts), boolean chains 4, error handling 2 (nesting depth added 3). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
dry-run.processFiles (cognitive 24) packages/shadcn/src/utils/dry-run.ts:132— dry-run.processFiles has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3 (5 pts), boolean chains 4, error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-layout.Layout (cognitive 23) apps/v4/hooks/use-layout.tsx:43— use-layout.Layout has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 3, boolean chains 2, error handling 1 (nesting depth added 2). None of this is in the body itself: all 23 points belong to 7 function literals inside it that branch (lines 76, 51, 70, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-message-scroller-controller.useMessageScrollerController.handleContentChange::reconcileScrollPosition (cognitive 23) packages/react/src/message-scroller/use-message-scroller-controller.ts:401— use-message-scroller-controller.useMessageScrollerController.handleContentChange::reconcileScrollPosition has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, 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.
fetcher.fetchRegistry (cognitive 23) packages/registry/src/registry/fetcher.ts:26— fetcher.fetchRegistry has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, loops 1 (nesting depth added 10). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 45, 36). 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.
resolve-file-path.resolveFilePath (cognitive 23) packages/registry/src/resolve-file-path.ts:8— resolve-file-path.resolveFilePath has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (4 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.
transform-import.getImportStringLiterals (cognitive 23) packages/registry/src/transformers/transform-import.ts:87— transform-import.getImportStringLiterals has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (collect, a function literal at line 90). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
transform-render.transformRenderSourceFile (cognitive 23) packages/shadcn/src/utils/transformers/transform-render.ts:12— transform-render.transformRenderSourceFile has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 2 (4 pts), loops 2 (nesting depth added 10). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
font-picker.FontPicker (cognitive 22) apps/v4/app/(app)/(typeset)/components/font-picker.tsx:21— font-picker.FontPicker has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 8 (9 pts), boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 56, 100). 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.
page.generateStaticParams (cognitive 22) apps/v4/app/(view)/view/[style]/[name]/page.tsx:85— page.generateStaticParams has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-questionnaire-item.useQuestionnaireItem (cognitive 22) packages/react/src/questionnaire/use-questionnaire-item.ts:35— use-questionnaire-item.useQuestionnaireItem has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Of this number, 16 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
comment-nodes.getCommentNodes (cognitive 22) packages/registry/src/codemod/comment-nodes.ts:45— comment-nodes.getCommentNodes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 3, ternaries 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
github-cli.getGitHubTransportFailureGuidance (cognitive 22) packages/registry/src/registry/github-cli.ts:292— github-cli.getGitHubTransportFailureGuidance has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 3 (7 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-menu.transformMenu (cognitive 22) packages/registry/src/transformers/transform-menu.ts:18— transform-menu.transformMenu has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, 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.
update-env-vars.updateEnvVars (cognitive 22) packages/registry/src/updaters/update-env-vars.ts:15— update-env-vars.updateEnvVars has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (7 pts), boolean chains 2 (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.
update-fonts.massageTreeForFonts (cognitive 22) REDACTED:47— update-fonts.massageTreeForFonts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· mcp.mcp.command("init").description("Initialize MCP configuration for your client").option("--client <client>").action() (cognitive 22) · ×1
mcp.mcp.command("init").description("Initialize MCP configuration for your client").option("--client <client>").action() (cognitive 22) packages/shadcn/src/commands/mcp.ts:121— mcp.mcp.command("init").description("Initialize MCP configuration for your client").option("--client <client>").action() has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 7 (9 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dry-run-formatter.processHunk (cognitive 22) packages/shadcn/src/utils/dry-run-formatter.ts:557— dry-run-formatter.processHunk has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 4 (5 pts), boolean chains 4 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
registries.ensureRegistriesInConfig (cognitive 22) packages/shadcn/src/utils/registries.ts:12— registries.ensureRegistriesInConfig has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-radix.migrateRadixFile (cognitive 21) packages/shadcn/src/migrations/migrate-radix.ts:272— migrate-radix.migrateRadixFile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, ternaries 3, loops 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-random.useRandom.randomizeTrueRandom (cognitive 20) apps/v4/app/(app)/(create)/hooks/use-random.tsx:54— use-random.useRandom.randomizeTrueRandom has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 4, if/else 3 (nesting depth added 1). Of this number, 19 points are the body's own statements and 1 belongs to one function literal 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.
registry.createFileTreeForRegistryItemFiles (cognitive 20) apps/v4/lib/registry.ts:311— registry.createFileTreeForRegistryItemFiles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 1 (4 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capture-explore.captureScreenshots (cognitive 20) apps/v4/scripts/capture-explore.mts:14— capture-explore.captureScreenshots has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 8). 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.
stream.createTurnStream (cognitive 20) packages/helpers/src/core/stream.ts:16— stream.createTurnStream has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 2 (3 pts) (nesting depth added 8). Of this number, 15 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body 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.
apply.syncApplyWorkspaceConfigs (cognitive 20) packages/shadcn/src/commands/apply.ts:438— apply.syncApplyWorkspaceConfigs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 5 (6 pts), ternaries 5 (6 pts), boolean chains 1, error handling 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.
info.printInfo (cognitive 20) packages/shadcn/src/commands/info.ts:159— info.printInfo has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 7 (8 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-radix.processNamedImports (cognitive 20) packages/shadcn/src/migrations/migrate-radix.ts:19— migrate-radix.processNamedImports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.resolveHeadingFont (cognitive 20) packages/shadcn/src/preset/resolve.ts:339— resolve.resolveHeadingFont has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.extractNextFontState (cognitive 20) packages/shadcn/src/preset/resolve.ts:529— resolve.extractNextFontState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (6 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.
page-tree.getPagesFromFolder (cognitive 19) REDACTED:23— page-tree.getPagesFromFolder has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 3 (8 pts), loops 1 (2 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
geometry.getMessageScrollerVisibilityState (cognitive 19) packages/react/src/message-scroller/geometry.ts:37— geometry.getMessageScrollerVisibilityState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
diff.diffComponent (cognitive 19) packages/shadcn/src/commands/diff.ts:171— diff.diffComponent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-icons.findIconUsages (cognitive 19) packages/shadcn/src/migrations/migrate-icons.ts:489— migrate-icons.findIconUsages has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-form.ProjectForm (cognitive 18) REDACTED:121— project-form.ProjectForm has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 5, if/else 3 (nesting depth added 1). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 149, 183, 209, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
docs-sidebar.DocsSidebar (cognitive 18) apps/v4/components/docs-sidebar.tsx:120— docs-sidebar.DocsSidebar has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 18 points belong to 5 function literals inside it that branch (lines 128, 193, 225, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
score.deriveStatus (cognitive 18) apps/v4/lib/registry-health/score.ts:237— score.deriveStatus has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
tool-chat.ToolChat (cognitive 18) apps/v4/registry/bases/radix/blocks/preview-03/cards/tool-chat.tsx:93— tool-chat.ToolChat has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 2, if/else 2 (nesting depth added 5). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 165, onSubmit, a function literal at line 148). 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.
config.buildRegistryTheme (cognitive 18) apps/v4/registry/config.ts:698— config.buildRegistryTheme has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, 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.
capture-registry.captureScreenshots (cognitive 18) apps/v4/scripts/capture-registry.mts:12— capture-registry.captureScreenshots has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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.
comma-lists.getLastTokenEnd (cognitive 18) packages/registry/src/codemod/comma-lists.ts:410— comma-lists.getLastTokenEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
font-markers.getSupportedFontMarkers (cognitive 18) packages/registry/src/font-markers.ts:18— font-markers.getSupportedFontMarkers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 4 (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.
transform-font.transformFontCalls (cognitive 18) packages/registry/src/transformers/transform-font.ts:165— transform-font.transformFontCalls has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update-files.resolveModuleByProbablePath (cognitive 18) packages/registry/src/updaters/update-files.ts:559— update-files.resolveModuleByProbablePath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, ternaries 4, loops 2 (nesting depth added 3). Of this number, 13 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
templates.parseAttributeTokens (cognitive 18) packages/shadcn/src/icons/templates.ts:89— templates.parseAttributeTokens has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preview.Preview (cognitive 17) apps/v4/app/(app)/(create)/components/preview.tsx:39— preview.Preview has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 1. None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 79, 52, 48). 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.
directory.createRegistryDirectoryView (cognitive 17) apps/v4/lib/registry-health/directory.ts:36— directory.createRegistryDirectoryView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 1 (3 pts), boolean chains 2, 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.
build-registry.buildBasesIndex (cognitive 17) apps/v4/scripts/build-registry.mts:867— build-registry.buildBasesIndex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-questionnaire-choice.useQuestionnaireChoice (cognitive 17) packages/react/src/questionnaire/use-questionnaire-choice.ts:15— use-questionnaire-choice.useQuestionnaireChoice has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 5, ternaries 4 (5 pts) (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 belong to 4 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.
trivia.iterateCommentRanges (cognitive 17) packages/registry/src/codemod/trivia.ts:116— trivia.iterateCommentRanges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 4, 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.
is-safe-target.isSafeTarget (cognitive 17) packages/registry/src/is-safe-target.ts:3— is-safe-target.isSafeTarget has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, error handling 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
transform-icons.transformIcons (cognitive 17) packages/registry/src/transformers/transform-icons.ts:36— transform-icons.transformIcons has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 2 (3 pts), 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.
check-exports.collect (cognitive 17) packages/shadcn/scripts/check-exports.mjs:100— check-exports.collect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (7 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.
preflight-apply.preFlightApply (cognitive 17) packages/shadcn/src/preflights/preflight-apply.ts:15— preflight-apply.preFlightApply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.resolveProjectPreset (cognitive 17) packages/shadcn/src/preset/resolve.ts:78— resolve.resolveProjectPreset has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (4 pts), error handling 1 (3 pts) (nesting depth added 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.
transform-style-map.applyToCvaCalls (cognitive 17) packages/shadcn/src/styles/transform-style-map.ts:118— transform-style-map.applyToCvaCalls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 7. None of this is in the body itself: all 17 points belong to 4 function literals inside it that branch (lines 123, 161, 171, …). 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.
transform-legacy-icons.transformLegacyIconsSourceFile (cognitive 17) packages/shadcn/src/utils/transformers/transform-legacy-icons.ts:10— transform-legacy-icons.transformLegacyIconsSourceFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
menu-picker.MenuColorPicker (cognitive 16) apps/v4/app/(app)/(create)/components/menu-picker.tsx:48— menu-picker.MenuColorPicker has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9, boolean chains 5, if/else 2. Of this number, 10 points are the body's own statements and 6 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.
use-history.HistoryProvider (cognitive 16) apps/v4/app/(app)/(create)/hooks/use-history.tsx:41— use-history.HistoryProvider has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 129, 62, 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.
use-history.TypesetHistoryProvider (cognitive 16) apps/v4/app/(app)/(typeset)/hooks/use-history.tsx:43— use-history.TypesetHistoryProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 6. None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 133, 67, 110, …). 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.
message-animated.getMessageAnimatedContentParts (cognitive 16) apps/v4/components/message-animated.tsx:151— message-animated.getMessageAnimatedContentParts has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 7). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 153). 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.
reasoning-chat.ReasoningChat (cognitive 16) apps/v4/registry/bases/radix/blocks/preview-03/cards/reasoning-chat.tsx:103— reasoning-chat.ReasoningChat has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 2, if/else 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 3 function items inside it that branch (a function literal at line 175, onSubmit, a function literal at line 158). 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.
sources-chat.SourcesChat (cognitive 16) apps/v4/registry/bases/radix/blocks/preview-03/cards/sources-chat.tsx:66— sources-chat.SourcesChat has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 3, if/else 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 3 function items inside it that branch (a function literal at line 138, onSubmit, a function literal at line 121). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.mergeProps (cognitive 16) packages/react/src/use-render/index.ts:84— index.mergeProps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-cleanup.cleanupCalls (cognitive 16) packages/registry/src/transformers/transform-cleanup.ts:101— transform-cleanup.cleanupCalls has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform-import.transformImport (cognitive 16) packages/registry/src/transformers/transform-import.ts:7— transform-import.transformImport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update-files.toAliasedImport (cognitive 16) packages/registry/src/updaters/update-files.ts:622— update-files.toAliasedImport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, ternaries 3 (nesting depth added 2). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
collect-bindings.collectCommonJsBindings (cognitive 16) packages/shadcn/src/migrations/cn/collect-bindings.ts:56— collect-bindings.collectCommonJsBindings has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cross-context type TailwindVersion (registry → shadcn) packages/shadcn/src/migrations/migrate-base-color.ts:200— TailwindVersion (context registry) is exposed in shadcn's public surface via migrate-base-color.getBaseColorMigration — couples the contexts.
End-of-life runtime: Node.js 20 .nvmrc:1— .nvmrc declares Node.js 20 as this project's version file, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
Hollow method — returns a constant without doing the work apps/v4/app/(app)/llm/[[...slug]]/route.ts:59— `generateStaticParams` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Fake-async — async method never awaits packages/shadcn/src/index.ts:23— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 2124 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· Runner config excludes tests no gate runs · ×1
Runner config excludes tests no gate runs packages/react/vitest.config.ts:10— `**/*.browser.test.*` removes 46 test(s) in 3 file(s) (e.g. `packages/react/src/message-scroller/message-scroller.browser.test.tsx`, `packages/react/src/message-scroller/message-scroller.perf.browser.test.tsx`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Forked directory tree (5 identical files, ~408 lines × 2 trees) apps/v4/registry/bases/radix/blocks/sidebar-10/components/nav-favorites.tsx:1— apps/v4/registry/bases/radix/blocks/sidebar-10/ and apps/v4/registry/bases/radix/blocks/sidebar-15/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~408 lines; the trees hold 8 and 11 files). That is one structural fact, not 5 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (5 identical files, ~340 lines × 2 trees) apps/v4/registry/new-york-v4/blocks/sidebar-10/components/nav-favorites.tsx:1— apps/v4/registry/new-york-v4/blocks/sidebar-10/ and apps/v4/registry/new-york-v4/blocks/sidebar-15/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~340 lines; the trees hold 8 and 11 files). That is one structural fact, not 5 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 3 sibling directories (244 clone groups) apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3— 244 duplicated blocks under apps/v4/registry/bases/ have copies in at least two of the sibling directories aria, base, radix — 230 of them are reported below, and 14 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 244 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 244 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 244 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (152 clone groups) apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3— 152 duplicated blocks under apps/v4/registry/ have copies in at least two of the sibling directories bases, new-york-v4 — 128 of them are reported below, and 24 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 152 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 152 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 152 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (69 clone groups) apps/v4/app/(app)/(root)/cards/transfer-funds.tsx:32— 69 duplicated blocks under apps/v4/ have copies in at least two of the sibling directories app, components, hooks, registry — 51 of them are reported below, and 18 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 69 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 69 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 69 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 22 sibling directories (38 clone groups) apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3— 38 duplicated blocks under apps/v4/registry/new-york-v4/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+16 more sibling(s) not listed) — 30 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 24 sibling directories (33 clone groups) apps/v4/registry/bases/base/blocks/sidebar-08/components/app-sidebar.tsx:20— 33 duplicated blocks under apps/v4/registry/bases/base/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+18 more sibling(s) not listed) — 29 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 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 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 33 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 24 sibling directories (28 clone groups) apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20— 28 duplicated blocks under apps/v4/registry/bases/radix/blocks/ have copies in at least two of the sibling directories dashboard-01, login-01, login-02, login-03, login-04, login-05 (+18 more sibling(s) not listed) — 22 of them are reported below, and 6 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 28 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 28 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 28 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 17 sibling directories (22 clone groups) apps/v4/registry/bases/aria/blocks/sidebar-08/components/app-sidebar.tsx:20— 22 duplicated blocks under apps/v4/registry/bases/aria/blocks/ have copies in at least two of the sibling directories dashboard-01, login-05, sidebar-01, sidebar-02, sidebar-03, sidebar-04 (+11 more sibling(s) not listed) — 20 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (20 clone groups) apps/v4/app/(app)/(create)/components/picker.tsx:13— 20 duplicated blocks under apps/v4/app/(app)/ have copies in at least two of the sibling directories (create), (root), (styles), (typeset), blocks, charts (+1 more sibling(s) not listed) — 17 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (9 clone groups) apps/v4/app/(app)/(styles)/sera/media-library-table/components/preview-header.tsx:12— 9 duplicated blocks under apps/v4/app/(app)/(styles)/sera/ have copies in at least two of the sibling directories article-directory, audience-analytics, edit-article, empty-state, media-library, media-library-table — 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.
Duplication concentrated across 2 sibling directories (5 clone groups) packages/registry/src/updaters/update-files.ts:109— 5 duplicated blocks under packages/ have copies in at least two of the sibling directories registry, shadcn — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (583 identical lines × 2 files) apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3— apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 583 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (525 identical lines × 2 files) apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3— apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:3 · apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 525 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (471 identical lines × 2 files) apps/v4/registry/bases/base/ui/_registry.ts:1— apps/v4/registry/bases/base/ui/_registry.ts:1 · apps/v4/registry/bases/radix/ui/_registry.ts:1 — these 2 files are line-for-line copies of one another — 471 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (450 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/_registry.ts:1— apps/v4/registry/bases/aria/blocks/_registry.ts:1 · apps/v4/registry/bases/base/blocks/_registry.ts:1 · apps/v4/registry/bases/radix/blocks/_registry.ts:1 — these 3 files are line-for-line copies of one another — 450 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (449 identical lines × 2 files) apps/v4/registry/bases/aria/ui/_registry.ts:1— apps/v4/registry/bases/aria/ui/_registry.ts:1 · apps/v4/registry/bases/radix/ui/_registry.ts:1 — these 2 files are line-for-line copies of one another — 449 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (391 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:3— apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:3 — these 3 files are line-for-line copies of one another — 391 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 (391 matched lines × 2 locations) · ×1
Duplicated block with local edits (391 matched lines × 2 locations) packages/registry/src/registry/loader.ts:77— packages/registry/src/registry/loader.ts:77 · packages/registry/src/registry/source.ts:87 — the two spans are one implementation copied and then locally edited — 1664 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (307 identical lines × 2 files) apps/v4/registry/bases/radix/ui/sidebar.tsx:3— apps/v4/registry/bases/radix/ui/sidebar.tsx:3 · apps/v4/registry/new-york-v4/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 307 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (302 identical lines × 2 files) apps/v4/registry/bases/aria/ui/sidebar.tsx:3— apps/v4/registry/bases/aria/ui/sidebar.tsx:3 · apps/v4/registry/bases/radix/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 302 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (291 identical lines × 2 files) apps/v4/registry/bases/base/ui/sidebar.tsx:3— apps/v4/registry/bases/base/ui/sidebar.tsx:3 · apps/v4/registry/bases/radix/ui/sidebar.tsx:3 — these 2 files are line-for-line copies of one another — 291 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (244 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/preview/cards/bar-visualizer.tsx:3— apps/v4/registry/bases/aria/blocks/preview/cards/bar-visualizer.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/bar-visualizer.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/bar-visualizer.tsx:3 — these 3 files are line-for-line copies of one another — 244 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (236 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/preview/cards/codespaces-card.tsx:3— apps/v4/registry/bases/aria/blocks/preview/cards/codespaces-card.tsx:3 · apps/v4/registry/bases/base/blocks/preview/cards/codespaces-card.tsx:3 · apps/v4/registry/bases/radix/blocks/preview/cards/codespaces-card.tsx:3 — these 3 files are line-for-line copies of one another — 236 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (233 lines × 2 locations) apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20— apps/v4/registry/bases/radix/blocks/sidebar-08/components/app-sidebar.tsx:20 · apps/v4/registry/bases/radix/blocks/sidebar-16/components/app-sidebar.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Wholesale file copy (230 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/preview-02/cards/sidebar-nav.tsx:16— apps/v4/registry/bases/aria/blocks/preview-02/cards/sidebar-nav.tsx:16 · apps/v4/registry/bases/base/blocks/preview-02/cards/sidebar-nav.tsx:16 · apps/v4/registry/bases/radix/blocks/preview-02/cards/sidebar-nav.tsx:16 — these 3 files are line-for-line copies of one another — 230 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (225 lines × 3 locations) apps/v4/registry/bases/aria/blocks/sidebar-07/components/app-sidebar.tsx:19— apps/v4/registry/bases/aria/blocks/sidebar-07/components/app-sidebar.tsx:19 · apps/v4/registry/bases/base/blocks/sidebar-07/components/app-sidebar.tsx:19 · apps/v4/registry/bases/radix/blocks/sidebar-07/components/app-sidebar.tsx:19 — 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.
Wholesale file copy (208 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/preview-02/cards/recent-transactions.tsx:3— apps/v4/registry/bases/aria/blocks/preview-02/cards/recent-transactions.tsx:3 · apps/v4/registry/bases/base/blocks/preview-02/cards/recent-transactions.tsx:3 · apps/v4/registry/bases/radix/blocks/preview-02/cards/recent-transactions.tsx:3 — these 3 files are line-for-line copies of one another — 208 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (208 identical lines × 6 files) apps/v4/registry/bases/aria/blocks/sidebar-10/components/app-sidebar.tsx:3— apps/v4/registry/bases/aria/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/bases/aria/blocks/sidebar-15/components/sidebar-left.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-15/components/sidebar-left.tsx:3 · +2 more site(s) not listed — these 6 files are line-for-line copies of one another — 208 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (189 identical lines × 4 files) REDACTED:3— REDACTED:3 · REDACTED:3 · REDACTED:3 · REDACTED:3 — these 4 files are line-for-line copies of one another — 189 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (187 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/sidebar-09/components/app-sidebar.tsx:3— apps/v4/registry/bases/aria/blocks/sidebar-09/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/sidebar-09/components/app-sidebar.tsx:3 · apps/v4/registry/bases/radix/blocks/sidebar-09/components/app-sidebar.tsx:3 — these 3 files are line-for-line copies of one another — 187 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (180 identical lines × 5 files) apps/v4/registry/bases/aria/blocks/dashboard-01/components/chart-area-interactive.tsx:3— apps/v4/registry/bases/aria/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/bases/base/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · apps/v4/registry/new-york-v4/blocks/dashboard-01/components/chart-area-interactive.tsx:3 · +1 more site(s) not listed — these 5 files are line-for-line copies of one another — 180 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (175 lines × 2 locations) apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:625— apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:625 · apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:663 — 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.
Wholesale file copy (165 identical lines × 3 files) apps/v4/registry/bases/aria/blocks/dashboard-01/components/app-sidebar.tsx:3— apps/v4/registry/bases/aria/blocks/dashboard-01/components/app-sidebar.tsx:3 · apps/v4/registry/bases/base/blocks/dashboard-01/components/app-sidebar.tsx:3 · apps/v4/registry/bases/radix/blocks/dashboard-01/components/app-sidebar.tsx:3 — these 3 files are line-for-line copies of one another — 165 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (165 identical lines × 2 files) apps/v4/registry/bases/base/ui/combobox.tsx:3— apps/v4/registry/bases/base/ui/combobox.tsx:3 · apps/v4/registry/bases/radix/ui/combobox.tsx:3 — these 2 files are line-for-line copies of one another — 165 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (160 identical lines × 2 files) apps/v4/registry/new-york-v4/charts/chart-bar-interactive.tsx:3— apps/v4/registry/new-york-v4/charts/chart-bar-interactive.tsx:3 · apps/v4/registry/new-york-v4/charts/chart-line-interactive.tsx:3 — these 2 files are line-for-line copies of one another — 160 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (152 identical lines × 3 files) apps/v4/registry/bases/aria/ui/questionnaire.tsx:3— apps/v4/registry/bases/aria/ui/questionnaire.tsx:3 · apps/v4/registry/bases/base/ui/questionnaire.tsx:3 · apps/v4/registry/bases/radix/ui/questionnaire.tsx:3 — these 3 files are line-for-line copies of one another — 152 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (149 identical lines × 2 files) apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3— apps/v4/registry/new-york-v4/blocks/sidebar-10/components/app-sidebar.tsx:3 · apps/v4/registry/new-york-v4/blocks/sidebar-15/components/sidebar-left.tsx:3 — these 2 files are line-for-line copies of one another — 149 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.
Complex function (anonymous) (cyclomatic 82, cognitive 125) packages/shadcn/src/commands/init.ts:170— (anonymous) has cyclomatic complexity 82 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateFiles (cyclomatic 59, cognitive 105) packages/registry/src/updaters/update-files.ts:50— updateFiles has cyclomatic complexity 59 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 Once (cyclomatic 49, cognitive 161) · ×1
Complex function Once (cyclomatic 49, cognitive 161) packages/registry/src/updaters/update-css.ts:112— Once has cyclomatic complexity 49 and cognitive complexity 161; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function convertNode (cyclomatic 49, cognitive 13) packages/registry/src/codemod/indentation.ts:809— convertNode has cyclomatic complexity 49 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 45, cognitive 47) packages/shadcn/src/commands/add.ts:77— (anonymous) has cyclomatic complexity 45 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runInit (cyclomatic 41, cognitive 63) packages/shadcn/src/commands/init.ts:610— runInit has cyclomatic complexity 41 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isForbiddenIpv4 (cyclomatic 37, cognitive 24) apps/v4/lib/registry-health/network.ts:102— isForbiddenIpv4 has cyclomatic complexity 37 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleKeyDown (cyclomatic 36, cognitive 36) packages/react/src/questionnaire/use-questionnaire-root.ts:361— handleKeyDown has cyclomatic complexity 36 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function stripJsonCommentsAndTrailingCommas (cyclomatic 34, cognitive 75) packages/registry/src/get-project-info.ts:408— stripJsonCommentsAndTrailingCommas has cyclomatic complexity 34 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function addWorkspaceComponents (cyclomatic 31, cognitive 38) packages/registry/src/add-components.ts:148— addWorkspaceComponents has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 30, cognitive 52) packages/registry/src/transformers/transform-rtl.ts:131— (anonymous) has cyclomatic complexity 30 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function migrateIcons (cyclomatic 30, cognitive 49) packages/shadcn/src/migrations/migrate-icons.ts:56— migrateIcons has cyclomatic complexity 30 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.
Complex function handleCallTool (cyclomatic 30, cognitive 40) packages/shadcn/src/mcp/index.ts:197— handleCallTool has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function eventsFromParts (cyclomatic 28, cognitive 62) packages/helpers/src/ai-sdk/parts.ts:273— eventsFromParts has cyclomatic complexity 28 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function migrateBaseColor (cyclomatic 28, cognitive 33) packages/shadcn/src/migrations/migrate-base-color.ts:33— migrateBaseColor has cyclomatic complexity 28 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getMessagePartComponent (cyclomatic 28, cognitive 24) apps/v4/components/message-parts.tsx:301— getMessagePartComponent has cyclomatic complexity 28 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateImportAliases (cyclomatic 27, cognitive 31) packages/registry/src/transformers/transform-import.ts:193— updateImportAliases has cyclomatic complexity 27 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· apps/v4/registry/bases/base/ui/_registry.ts · ×1
apps/v4/registry/bases/base/ui/_registry.ts: 1150 lines of code apps/v4/registry/bases/base/ui/_registry.ts:1— apps/v4/registry/bases/base/ui/_registry.ts has 1150 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· apps/v4/registry/bases/radix/ui/_registry.ts · ×1
apps/v4/registry/bases/radix/ui/_registry.ts: 1128 lines of code apps/v4/registry/bases/radix/ui/_registry.ts:1— apps/v4/registry/bases/radix/ui/_registry.ts has 1128 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/registry/src/codemod/indentation.ts · ×1
packages/registry/src/codemod/indentation.ts: 1122 lines of code packages/registry/src/codemod/indentation.ts:1— packages/registry/src/codemod/indentation.ts has 1122 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/commands/init.ts · ×1
packages/shadcn/src/commands/init.ts: 955 lines of code packages/shadcn/src/commands/init.ts:1— packages/shadcn/src/commands/init.ts has 955 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· apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx · ×1
apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx: 947 lines of code apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx:1— apps/v4/registry/bases/base/blocks/dashboard-01/components/data-table.tsx has 947 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· apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx · ×1
apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx: 883 lines of code apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx:1— apps/v4/registry/bases/aria/blocks/dashboard-01/components/data-table.tsx has 883 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· apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx · ×1
apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx: 871 lines of code apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx:1— apps/v4/registry/bases/radix/blocks/dashboard-01/components/data-table.tsx has 871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
apps/v4/registry/config.ts: 870 lines of code apps/v4/registry/config.ts:1— apps/v4/registry/config.ts has 870 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· apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx · ×1
apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx: 795 lines of code apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx:1— apps/v4/registry/new-york-v4/blocks/dashboard-01/components/data-table.tsx has 795 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· apps/v4/registry/new-york-v4/ui/_registry.ts · ×1
apps/v4/registry/new-york-v4/ui/_registry.ts: 758 lines of code apps/v4/registry/new-york-v4/ui/_registry.ts:1— apps/v4/registry/new-york-v4/ui/_registry.ts has 758 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/registry/src/updaters/update-files.ts · ×1
packages/registry/src/updaters/update-files.ts: 744 lines of code packages/registry/src/updaters/update-files.ts:1— packages/registry/src/updaters/update-files.ts has 744 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· apps/v4/components/theme-customizer.tsx · ×1
apps/v4/components/theme-customizer.tsx: 730 lines of code apps/v4/components/theme-customizer.tsx:1— apps/v4/components/theme-customizer.tsx has 730 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/helpers/src/core/chat.ts · ×1
packages/helpers/src/core/chat.ts: 707 lines of code packages/helpers/src/core/chat.ts:1— packages/helpers/src/core/chat.ts has 707 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: 697 lines of code REDACTED:1— REDACTED has 697 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/registry/src/registry/resolver.ts · ×1
packages/registry/src/registry/resolver.ts: 696 lines of code packages/registry/src/registry/resolver.ts:1— packages/registry/src/registry/resolver.ts has 696 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/registry/src/updaters/update-css-vars.ts · ×1
packages/registry/src/updaters/update-css-vars.ts: 696 lines of code packages/registry/src/updaters/update-css-vars.ts:1— packages/registry/src/updaters/update-css-vars.ts has 696 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: 692 lines of code REDACTED:1— REDACTED has 692 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/preset/resolve.ts · ×1
packages/shadcn/src/preset/resolve.ts: 684 lines of code packages/shadcn/src/preset/resolve.ts:1— packages/shadcn/src/preset/resolve.ts has 684 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· apps/v4/registry/bases/base/ui/sidebar.tsx · ×1
apps/v4/registry/bases/base/ui/sidebar.tsx: 680 lines of code apps/v4/registry/bases/base/ui/sidebar.tsx:1— apps/v4/registry/bases/base/ui/sidebar.tsx has 680 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/migrations/migrate-icons.ts · ×1
packages/shadcn/src/migrations/migrate-icons.ts: 675 lines of code packages/shadcn/src/migrations/migrate-icons.ts:1— packages/shadcn/src/migrations/migrate-icons.ts has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react/src/message-scroller/use-message-scroller-controller.ts · ×1
packages/react/src/message-scroller/use-message-scroller-controller.ts: 673 lines of code packages/react/src/message-scroller/use-message-scroller-controller.ts:1— packages/react/src/message-scroller/use-message-scroller-controller.ts has 673 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· apps/v4/registry/new-york-v4/ui/sidebar.tsx · ×1
apps/v4/registry/new-york-v4/ui/sidebar.tsx: 672 lines of code apps/v4/registry/new-york-v4/ui/sidebar.tsx:1— apps/v4/registry/new-york-v4/ui/sidebar.tsx has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/registry/src/updaters/update-tailwind-config.ts · ×1
packages/registry/src/updaters/update-tailwind-config.ts: 666 lines of code packages/registry/src/updaters/update-tailwind-config.ts:1— packages/registry/src/updaters/update-tailwind-config.ts has 666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/shadcn/src/utils/dry-run-formatter.ts · ×1
packages/shadcn/src/utils/dry-run-formatter.ts: 665 lines of code packages/shadcn/src/utils/dry-run-formatter.ts:1— packages/shadcn/src/utils/dry-run-formatter.ts has 665 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· apps/v4/registry/bases/aria/ui/sidebar.tsx · ×1
apps/v4/registry/bases/aria/ui/sidebar.tsx: 663 lines of code apps/v4/registry/bases/aria/ui/sidebar.tsx:1— apps/v4/registry/bases/aria/ui/sidebar.tsx has 663 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/v4/registry/bases/radix/ui/sidebar.tsx · ×1
apps/v4/registry/bases/radix/ui/sidebar.tsx: 654 lines of code apps/v4/registry/bases/radix/ui/sidebar.tsx:1— apps/v4/registry/bases/radix/ui/sidebar.tsx has 654 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/registry/src/registry/validate.ts · ×1
packages/registry/src/registry/validate.ts: 639 lines of code packages/registry/src/registry/validate.ts:1— packages/registry/src/registry/validate.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· apps/v4/lib/registry-health/monitor.ts · ×1
apps/v4/lib/registry-health/monitor.ts: 618 lines of code apps/v4/lib/registry-health/monitor.ts:1— apps/v4/lib/registry-health/monitor.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/v4/components/command-menu.tsx · ×1
apps/v4/components/command-menu.tsx: 592 lines of code apps/v4/components/command-menu.tsx:1— apps/v4/components/command-menu.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/registry/src/registry/source.ts · ×1
packages/registry/src/registry/source.ts: 581 lines of code packages/registry/src/registry/source.ts:1— packages/registry/src/registry/source.ts has 581 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/registry/src/registry/loader.ts · ×1
packages/registry/src/registry/loader.ts: 577 lines of code packages/registry/src/registry/loader.ts:1— packages/registry/src/registry/loader.ts has 577 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/registry/src/get-project-info.ts · ×1
packages/registry/src/get-project-info.ts: 569 lines of code packages/registry/src/get-project-info.ts:1— packages/registry/src/get-project-info.ts has 569 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/styles/transform-style-map.ts · ×1
packages/shadcn/src/styles/transform-style-map.ts: 552 lines of code packages/shadcn/src/styles/transform-style-map.ts:1— packages/shadcn/src/styles/transform-style-map.ts has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 547 lines of code REDACTED:1— REDACTED has 547 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· apps/v4/components/message-parts.tsx · ×1
apps/v4/components/message-parts.tsx: 547 lines of code apps/v4/components/message-parts.tsx:1— apps/v4/components/message-parts.tsx has 547 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· apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx · ×1
apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx: 544 lines of code apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:1— apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx has 544 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· apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx · ×1
apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx: 544 lines of code apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx:1— apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx has 544 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· apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx · ×1
apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx: 544 lines of code apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx:1— apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.tsx has 544 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/mcp/index.ts · ×1
packages/shadcn/src/mcp/index.ts: 540 lines of code packages/shadcn/src/mcp/index.ts:1— packages/shadcn/src/mcp/index.ts has 540 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/registry/src/updaters/update-css.ts · ×1
packages/registry/src/updaters/update-css.ts: 530 lines of code packages/registry/src/updaters/update-css.ts:1— packages/registry/src/updaters/update-css.ts 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.
Dead file (~367 LoC) apps/v4/mdx-components.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~360 LoC) apps/v4/components/directory-list.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/mdx-components.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~277 LoC) apps/v4/components/docs-sidebar.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~273 LoC) apps/v4/components/cards/chat.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~231 LoC) packages/shadcn/src/commands/registry/build.ts— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~223 LoC) apps/v4/components/docs-copy-page.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~221 LoC) apps/v4/lib/rehype.ts— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~213 LoC) apps/v4/components/directory-add-button.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/directory-list.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~186 LoC) apps/v4/components/message-animated.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~179 LoC) apps/v4/components/docs-page-links.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~163 LoC) apps/v4/hooks/use-layout.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/site-config.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~142 LoC) apps/v4/components/cards/team-members.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~140 LoC) apps/v4/components/cards/forms.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~137 LoC) apps/v4/lib/message-animations.ts— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/message-animated.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~134 LoC) apps/v4/components/cards/payment-method.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~129 LoC) apps/v4/components/cards/exercise-minutes.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~128 LoC) apps/v4/components/code-block-command.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/mdx-components.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~126 LoC) apps/v4/components/docs-toc.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~125 LoC) apps/v4/app/(app)/(create)/components/preset-picker.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~117 LoC) apps/v4/components/cards/share.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~114 LoC) apps/v4/components/nav-user.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~108 LoC) apps/v4/app/(app)/(create)/components/item-explorer.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~100 LoC) apps/v4/components/cards/report-issue.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~94 LoC) apps/v4/components/examples-nav.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) apps/v4/components/cards/create-account.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/cards/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~69 LoC) apps/v4/components/components-list.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/mdx-components.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~59 LoC) apps/v4/components/cards/index.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~58 LoC) apps/v4/app/(app)/(styles)/sera/components/theme-switcher.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~57 LoC) apps/v4/components/directory-search.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/components/directory-list.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~56 LoC) apps/v4/app/(app)/(root)/cards/skeleton/index.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~54 LoC) apps/v4/components/code-collapsible-pre.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/v4/mdx-components.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~49 LoC) apps/v4/components/docs-base-switcher.tsx— no import path from any entry point (890 application, 25 tooling, 164 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@manypkg/cli' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pretty-quick' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@ai-sdk/anthropic' — Declared in apps/v4/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) apps/v4/scripts/build-registry.mts:1435— `spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `proc.stdout`, while `proc.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`proc.stdout.on('data', …)`, or `proc.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot.
Duplicated predicate packages/registry/src/registry/loader.ts:625— `!!relative && !relative.startsWith("..") && !path.isAbsolute(relative)` appears character-identically in 2 files — packages/registry/src/registry/loader.ts, packages/registry/src/registry/validate.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/registry/src/updaters/update-css.ts:36— `!config.resolvedPaths.tailwindCss || (!hasCss && !hasCssVars)` appears character-identically in 2 files — packages/registry/src/updaters/update-css.ts, packages/shadcn/src/utils/dry-run.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 apps/v4/scripts/capture-explore.mts:25— `!existsSync(lightPath) || !existsSync(darkPath)` appears character-identically in 2 files — apps/v4/scripts/capture-explore.mts, apps/v4/scripts/capture-registry.mts. 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/commands/info.ts:38— `!existsSync(path.resolve(cwd, "components.json")) && (await isMonorepoRoot(cwd))` appears character-identically in 2 files — packages/shadcn/src/commands/info.ts, packages/shadcn/src/commands/preset.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/shadcn/src/preflights/preflight-add.ts:22— `!fs.existsSync(options.cwd) || !fs.existsSync(path.resolve(options.cwd, "REDACTED"))` appears character-identically in 4 files — packages/shadcn/src/preflights/preflight-add.ts, packages/shadcn/src/preflights/preflight-apply.ts, packages/shadcn/src/preflights/preflight-init.ts, packages/shadcn/src/preflights/preflight-migrate.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 apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:424— `!gradientCacheRef.current || lastWidthRef.current !== rect.width` appears character-identically in 3 files — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.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/migrations/cn/collect-bindings.ts:61— `!initializer || !Node.isCallExpression(initializer)` appears character-identically in 3 files — packages/shadcn/src/migrations/cn/collect-bindings.ts, packages/shadcn/src/migrations/cn/specifiers.ts, packages/shadcn/src/styles/transform-style-map.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 apps/v4/components/command-menu.tsx:254— `!showMcpDocs && item.url.includes("/mcp")` appears character-identically in 2 files — apps/v4/components/command-menu.tsx, apps/v4/components/mobile-nav.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 apps/v4/app/(app)/(create)/hooks/use-theme-toggle.tsx:24— `(e.key === "d" || e.key === "D") && !e.metaKey && !e.ctrlKey && !e.altKey` appears character-identically in 3 files — apps/v4/app/(app)/(create)/hooks/use-theme-toggle.tsx, apps/v4/app/(app)/(typeset)/hooks/use-theme-toggle.tsx, apps/v4/components/theme-provider.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 apps/v4/app/(app)/(create)/hooks/use-history.tsx:135— `(e.target instanceof HTMLElement && e.target.isContentEditable) || e.target instanceof HTMLInputElement || e.target instanceof HTMLTextAreaE…` appears character-identically in 9 files — apps/v4/app/(app)/(create)/hooks/use-history.tsx, apps/v4/app/(app)/(create)/hooks/use-random.tsx, apps/v4/app/(app)/(create)/hooks/use-reset.tsx, apps/v4/app/(app)/(create)/hooks/use-theme-toggle.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 apps/v4/app/(app)/(create)/hooks/use-history.tsx:145— `(key === "z" && e.shiftKey) || (key === "y" && e.ctrlKey)` appears character-identically in 2 files — apps/v4/app/(app)/(create)/hooks/use-history.tsx, apps/v4/app/(app)/(typeset)/hooks/use-history.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/preset/resolve.ts:715— `Node.isStringLiteral(node) || Node.isNoSubstitutionTemplateLiteral(node)` appears character-identically in 2 files — packages/shadcn/src/preset/resolve.ts, packages/shadcn/src/styles/transform-style-map.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 apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:312— `active && currentTime - lastUpdateRef.current > updateRate` appears character-identically in 3 files — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.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/registry/src/transformers/transform-cleanup.ts:120— `arg.type === "TemplateLiteral" && arg.expressions.length === 0` appears character-identically in 2 files — packages/registry/src/transformers/transform-cleanup.ts, packages/registry/src/transformers/transform-font.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/registry/src/transformers/transform-cleanup.ts:72— `attrName !== "className" && attrName !== "classNames"` appears character-identically in 2 files — packages/registry/src/transformers/transform-cleanup.ts, packages/registry/src/transformers/transform-font.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 apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:227— `audioContextRef.current && audioContextRef.current.state !== "closed"` appears character-identically in 3 files — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.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 apps/v4/registry/new-york-v4/charts/chart-tooltip-advanced.tsx:91— `chartConfig[name as keyof typeof chartConfig]?.label || name` appears character-identically in 2 files — apps/v4/registry/new-york-v4/charts/chart-tooltip-advanced.tsx, apps/v4/registry/new-york-v4/charts/chart-tooltip-formatter.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 apps/v4/registry/bases/aria/ui/code-block.tsx:216— `children === undefined || children === null || children === "" || (Array.isArray(children) && children.length === 0)` appears character-identically in 3 files — apps/v4/registry/bases/aria/ui/code-block.tsx, apps/v4/registry/bases/base/ui/code-block.tsx, apps/v4/registry/bases/radix/ui/code-block.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/registry/src/updaters/update-tailwind-config.ts:251— `config.resolvedPaths?.tailwindConfig || "tailwind.config.ts"` appears character-identically in 2 files — packages/registry/src/updaters/update-tailwind-config.ts, packages/shadcn/src/utils/updaters/update-tailwind-content.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx:115— `containerRef.current?.getBoundingClientRect().width || 200` appears character-identically in 3 files — apps/v4/registry/bases/aria/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/base/blocks/preview/cards/live-waveform.tsx, apps/v4/registry/bases/radix/blocks/preview/cards/live-waveform.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 apps/v4/registry/bases/aria/blocks/preview/cards/style-overview.tsx:34— `currentFontHeading?.name && currentFontHeading.name !== currentFont?.name` appears character-identically in 6 files — apps/v4/registry/bases/aria/blocks/preview/cards/style-overview.tsx, apps/v4/registry/bases/aria/blocks/preview/cards/typography-specimen.tsx, apps/v4/registry/bases/base/blocks/preview/cards/style-overview.tsx, apps/v4/registry/bases/base/blocks/preview/cards/typography-specimen.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/migrations/cn/collect-bindings.ts:34— `declaration.isTypeOnly() || specifier.isTypeOnly()` appears character-identically in 2 files — packages/shadcn/src/migrations/cn/collect-bindings.ts, packages/shadcn/src/migrations/cn/specifiers.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/registry/src/registry/github-ref.ts:174— `error.kind === "http" && error.statusCode === 404` appears character-identically in 2 files — packages/registry/src/registry/github-ref.ts, packages/registry/src/registry/github.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 apps/v4/registry/bases/aria/ui/sidebar.tsx:103— `event.key === SIDEBAR_KEYBOARD_SHORTCUT && (event.metaKey || event.ctrlKey)` appears character-identically in 3 files — apps/v4/registry/bases/aria/ui/sidebar.tsx, apps/v4/registry/bases/base/ui/sidebar.tsx, apps/v4/registry/bases/radix/ui/sidebar.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react/src/questionnaire/use-questionnaire-root.ts:387— `event.metaKey || event.ctrlKey || event.altKey` appears character-identically in 5 files — packages/react/src/questionnaire/use-questionnaire-root.ts, templates/next-app/components/theme-provider.tsx, templates/next-monorepo/apps/web/components/theme-provider.tsx, templates/vite-app/src/components/theme-provider.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.
Mock-dominated test: should throw error if project path already exists packages/shadcn/src/utils/create-project.test.ts:149— This test sets up 3 test doubles (for example `vi
.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should throw error if path is not writable packages/shadcn/src/utils/create-project.test.ts:168— This test sets up 3 test doubles (for example `vi
.spyOn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: installs components via addComponents when a valid project exists packages/shadcn/src/commands/add.test.ts:280— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: offers components for the initialized style in the interactive picker packages/shadcn/src/commands/add.test.ts:338— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: uses the initialized style for --all (empty project: %s) packages/shadcn/src/commands/add.test.ts:375— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: updates the app index for a single v0 chat component packages/shadcn/src/commands/add.test.ts:635— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: does not update the app index for multiple components packages/shadcn/src/commands/add.test.ts:660— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not update the app index for a non-matching single component packages/shadcn/src/commands/add.test.ts:681— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: calls addComponents directly without running preflight/init packages/shadcn/src/commands/add.test.ts:754— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: runs template postInit after creating a new project packages/shadcn/src/commands/init.test.ts:227— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: prints no-config output when no components.json exists packages/shadcn/src/commands/preset.test.ts:379— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: prints null JSON when no components.json exists packages/shadcn/src/commands/preset.test.ts:388— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should route registry:hook files to workspaceConfig.hooks packages/registry/src/add-components.workspace.test.ts:236— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should route registry:lib files to workspaceConfig.lib packages/registry/src/add-components.workspace.test.ts:322— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should fall back to app config for unmapped types like registry:component packages/registry/src/add-components.workspace.test.ts:394— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should fall back to app config when workspace key is missing packages/registry/src/add-components.workspace.test.ts:440— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should route all three mapped types to their workspace configs packages/registry/src/add-components.workspace.test.ts:500— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should fall back to app config for registry:file packages/registry/src/add-components.workspace.test.ts:570— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should default files with no type to registry:ui packages/registry/src/add-components.workspace.test.ts:630— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should group multiple files of the same type into one updateFiles call packages/registry/src/add-components.workspace.test.ts:676— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should route hooks to separate package when aliases differ packages/registry/src/add-components.workspace.test.ts:734— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call updateFonts with app config, not workspace config packages/registry/src/add-components.workspace.test.ts:891— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: reports a layout updateFonts skipped, unless silent ($silent) packages/registry/src/add-components.workspace.test.ts:956— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) 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.
P2 · Observability· Console output used as the logging channel · ×19
Console output used as the logging channel packages/registry/src/logger.ts:5— `packages/registry/src/logger.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/logger.ts:8— `packages/registry/src/logger.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/logger.ts:11— `packages/registry/src/logger.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/logger.ts:14— `packages/registry/src/logger.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/logger.ts:17— `packages/registry/src/logger.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/logger.ts:20— `packages/registry/src/logger.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/updaters/update-css.ts:480— `packages/registry/src/updaters/update-css.ts` reports through `console.*` at line 480 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/registry/src/updaters/update-css.ts:577— `packages/registry/src/updaters/update-css.ts` reports through `console.*` at line 577 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/utils/file-helper.ts:40— `packages/shadcn/src/utils/file-helper.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/docs.ts:83— `packages/shadcn/src/commands/docs.ts` reports through `console.*` at line 83 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/info.ts:44— `packages/shadcn/src/commands/info.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/info.ts:70— `packages/shadcn/src/commands/info.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/preset.ts:90— `packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 90 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/preset.ts:171— `packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/preset.ts:193— `packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 193 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/preset.ts:205— `packages/shadcn/src/commands/preset.ts` reports through `console.*` at line 205 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/search.ts:219— `packages/shadcn/src/commands/search.ts` reports through `console.*` at line 219 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/view.ts:71— `packages/shadcn/src/commands/view.ts` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/shadcn/src/commands/registry/build.ts:143— `packages/shadcn/src/commands/registry/build.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Outdated (npm): @commitlint/config-conventional REDACTED:56— @commitlint/config-conventional is pinned at 17.8.1; registry.npmjs.org publishes 21.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hookform/resolvers apps/v4/package.json:40— @hookform/resolvers is pinned at 3.10.0; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hugeicons/core-free-icons apps/v4/package.json:41— @hugeicons/core-free-icons is pinned at 1.2.1; registry.npmjs.org publishes 4.3.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cross-env REDACTED:64— cross-env is pinned at 7.0.3; registry.npmjs.org publishes 10.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Silent fallback default in catch apps/v4/lib/format-code.ts:78— `getStyleMap` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/helpers/src/tanstack-ai/parts.ts:23— `parseJson` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/registry/src/registry/resolve-file-imports.ts:217— `getCssImportSpecifiers` 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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 113 significant file(s) lose their only recent owner: apps/v4/scripts/build-registry.mts, apps/v4/registry/themes.ts, packages/shadcn/src/commands/init.ts, apps/v4/components/theme-customizer.tsx, apps/v4/registry/bases/radix/ui/_registry.ts, REDACTED, packages/helpers/src/core/chat.ts, REDACTED (+105 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 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 (114 single-owned of 801 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; 801 of the 1573 production source files in this repository met that bar). They are anonymized user #2 (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: apps/v4/registry/_legacy-colors.ts.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `apps/v4` (374615 LoC, 3558 module-visible types across 333 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Disabled test packages/tests/src/tests/init.test.ts:730— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Thin README — The root README is 58 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/v4`.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 44136 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 2/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 50/70 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~1.2 `!` null assertions per 1k TypeScript source lines — 252 assertion(s) across the 209700 source line(s) of the 1545 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/registry/src/codemod/indentation.ts (59), packages/registry/src/updaters/update-tailwind-config.ts (15), packages/registry/src/codemod/array-literals.ts (14). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @ai-sdk/anthropic — @ai-sdk/anthropic is pinned at 4.0.0-canary.66; registry.npmjs.org publishes 4.0.88 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @ai-sdk/openai — @ai-sdk/openai is pinned at 4.0.0-canary.73; registry.npmjs.org publishes 4.0.102 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @ai-sdk/react — @ai-sdk/react is pinned at 4.0.0-canary.162; registry.npmjs.org publishes 4.0.157 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @astrojs/react — @astrojs/react is pinned at 7.1.0; registry.npmjs.org publishes 7.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/core — @babel/core is pinned at 7.28.0; registry.npmjs.org publishes 8.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/parser — @babel/parser is pinned at 7.28.0; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-typescript — @babel/plugin-transform-typescript is pinned at 7.28.0; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-typescript — @babel/preset-typescript is pinned at 7.27.1; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @base-ui/react — @base-ui/react is pinned at 1.6.0; registry.npmjs.org publishes 1.9.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @changesets/cli — @changesets/cli is pinned at 2.31.1; registry.npmjs.org publishes 3.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @commitlint/cli — @commitlint/cli is pinned at 20.1.0; registry.npmjs.org publishes 21.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dotenvx/dotenvx — @dotenvx/dotenvx is pinned at 1.48.4; registry.npmjs.org publishes 2.38.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @faker-js/faker — @faker-js/faker is pinned at 10.1.0; registry.npmjs.org publishes 10.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @formisch/react — @formisch/react is pinned at 0.4.4; registry.npmjs.org publishes 1.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hugeicons/react — @hugeicons/react is pinned at 1.1.1; registry.npmjs.org publishes 1.1.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @ianvs/prettier-plugin-sort-imports — @ianvs/prettier-plugin-sort-imports is pinned at 4.6.1; registry.npmjs.org publishes 4.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @internationalized/date — @internationalized/date is pinned at 3.12.3; registry.npmjs.org publishes 3.12.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @manypkg/cli — @manypkg/cli is pinned at 0.20.0; registry.npmjs.org publishes 0.25.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.32.1; registry.npmjs.org publishes 1.32.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @paper-design/shaders-react — @paper-design/shaders-react is pinned at 0.0.72; registry.npmjs.org publishes 0.0.82 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-checkbox — @radix-ui/react-checkbox is pinned at 1.1.4; registry.npmjs.org publishes 1.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-label — @radix-ui/react-label is pinned at 2.1.2; registry.npmjs.org publishes 2.1.17 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-radio-group — @radix-ui/react-radio-group is pinned at 1.2.3; registry.npmjs.org publishes 1.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-select — @radix-ui/react-select is pinned at 2.1.6; registry.npmjs.org publishes 2.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-slot — @radix-ui/react-slot is pinned at 1.1.2; registry.npmjs.org publishes 1.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): (unnamed test) packages/registry/src/get-config.test.ts:90— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/registry/src/registry/api.test.ts:1966— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/registry/src/registry/api.test.ts:2448— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 147 file(s) — `apps/v4/app/(app)/(create)/lib/fonts.ts`, `REDACTED`, `apps/v4/app/(app)/(styles)/sera/audience-analytics/components/traffic-overview.tsx`, `apps/v4/app/(app)/blocks/[...categories]/page.tsx`, `apps/v4/app/(app)/charts/[type]/page.tsx`, … (+142 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17804-99e0-749b-bd6c-f18e7881d145 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 139 · Warnings: 850 · Recommendations: 99 · Info: 102 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 11:42 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.