Public report of remix-run/remix, published 7 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 7 November 2026, 17:55 UTC · Survey ID cd_6d45016d65da43d99eb1760dec7a7c7e
remix-run/remix
Measured 7 November 2026, 17:54 UTC, at code version 305d22d
First survey, so nothing to compare with yet
CAI scoreAt risk
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: 157,090 lines of product code in 56 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Production Readiness, 51
Findings by how serious they are
177 critical843 serious188 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
7 November 2026, 17:54 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
87of 87 dimensions measured by tools.
1177of 1208 findings point to an exact file and line, so you can open each one in the code. The other 31 concern the repository as a whole, such as missing documentation.
87dimensions across 7 lenses, read from 157,090 lines of product code in 56 projects.
remix-run/remix is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and adopting a logging library, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 62.
103 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-five known security holes in the packages the code depends on can be used by attackers, and nine 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. Correcting the flagged pipeline settings would fix the ten weaknesses in the build pipeline's configuration, and the five passwords or keys in the code's history need replacing, with the old ones switched off. The 18 tests that check nothing need to check the result they produce.
The product code is 157,090 lines, about €310,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
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 51 to 70, the lowest score rated Strong, the score would rise from 57 to about 62.
Code composition: what the lines of code are
Product code 53%Tests 47%
Rebuild cost: about €310,000 · Estimate
Cost to rebuild
€100,000 to €510,000, for 1,703 to 5,403 hours of work, about 2.1 person-years for 1 to 5 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.8 at a score of 57. 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: 157,090 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
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.
Adopt pino (or winston) and log at meaningful points in the services you run.
Raises the score by about 5 points · Medium effort · Observability
3
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.
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 €310,000 to build again, about 2.1 person-years of work. Its weakest lens is Production Readiness, at 51 (Adequate). 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
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. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 221,580 lines over the last 90 days, which is about 898,630 lines a year. At that pace, the extra work comes to an estimated 100.9 to 605.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
388 modules, with 480 dependencies between them. 6 loops run through 17 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 348 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.
packages.assets.src.lib.asset-server uses packages.assets.src.lib.inspection, so a change to packages.assets.src.lib.inspection can break packages.assets.src.lib.asset-server, while a change to packages.assets.src.lib.asset-server can't break packages.assets.src.lib.inspection.
Position
Below the diagonal: packages.assets.src.lib.asset-server uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.core.vnode uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.component.src.runtime.core.vnode, while a change to packages.component.src.runtime.core.vnode can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.component.src.runtime.core.vnode uses a module listed above it, which is the healthy direction.
packages.data-table.src.lib.database uses packages.data-table.src.lib.driver, so a change to packages.data-table.src.lib.driver can break packages.data-table.src.lib.database, while a change to packages.data-table.src.lib.database can't break packages.data-table.src.lib.driver.
Position
Below the diagonal: packages.data-table.src.lib.database uses a module listed above it, which is the healthy direction.
packages.data-table.src.lib.database uses packages.data-table.src.lib.operators, so a change to packages.data-table.src.lib.operators can break packages.data-table.src.lib.database, while a change to packages.data-table.src.lib.database can't break packages.data-table.src.lib.operators.
Position
Below the diagonal: packages.data-table.src.lib.database uses a module listed above it, which is the healthy direction.
22→33 packages.fetch-router.src.lib.request-context uses packages.fetch-router.src.lib.routerpart of a loop✕
Connections
1 pair of types, where a type in packages.fetch-router.src.lib.request-context uses a type in packages.fetch-router.src.lib.router.
packages.fetch-router.src.lib.request-context uses packages.fetch-router.src.lib.router, so a change to packages.fetch-router.src.lib.router can break packages.fetch-router.src.lib.request-context, while a change to packages.fetch-router.src.lib.request-context can't break packages.fetch-router.src.lib.router.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.assets.src.lib uses packages.assets.src.lib.inspection, so a change to packages.assets.src.lib.inspection can break packages.assets.src.lib, while a change to packages.assets.src.lib can't break packages.assets.src.lib.inspection.
Position
Below the diagonal: packages.assets.src.lib uses a module listed above it, which is the healthy direction.
packages.assets.src.lib uses packages.assets.src.lib.asset-server, so a change to packages.assets.src.lib.asset-server can break packages.assets.src.lib, while a change to packages.assets.src.lib can't break packages.assets.src.lib.asset-server.
Position
Below the diagonal: packages.assets.src.lib uses a module listed above it, which is the healthy direction.
packages.auth.src.lib.provider uses packages.fetch-router.src.lib.request-context, so a change to packages.fetch-router.src.lib.request-context can break packages.auth.src.lib.provider, while a change to packages.auth.src.lib.provider can't break packages.fetch-router.src.lib.request-context.
Position
Below the diagonal: packages.auth.src.lib.provider uses a module listed above it, which is the healthy direction.
24→30 packages.auth.src.lib.provider uses packages.auth.src.libpart of a loop✕
Connections
4 pairs of types, where a type in packages.auth.src.lib.provider uses a type in packages.auth.src.lib.
packages.auth.src.lib.provider uses packages.auth.src.lib, so a change to packages.auth.src.lib can break packages.auth.src.lib.provider, while a change to packages.auth.src.lib.provider can't break packages.auth.src.lib.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.cli.src.lib.commands uses packages.assets.src.lib.inspection, so a change to packages.assets.src.lib.inspection can break packages.cli.src.lib.commands, while a change to packages.cli.src.lib.commands can't break packages.assets.src.lib.inspection.
Position
Below the diagonal: packages.cli.src.lib.commands uses a module listed above it, which is the healthy direction.
packages.cli.src.lib.commands uses packages.data-table.src.lib.database, so a change to packages.data-table.src.lib.database can break packages.cli.src.lib.commands, while a change to packages.cli.src.lib.commands can't break packages.data-table.src.lib.database.
Position
Below the diagonal: packages.cli.src.lib.commands uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.component uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.component.src.runtime.component, while a change to packages.component.src.runtime.component can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.component.src.runtime.component uses a module listed above it, which is the healthy direction.
packages.fetch-router.src.lib uses packages.fetch-router.src.lib.request-context, so a change to packages.fetch-router.src.lib.request-context can break packages.fetch-router.src.lib, while a change to packages.fetch-router.src.lib can't break packages.fetch-router.src.lib.request-context.
Position
Below the diagonal: packages.fetch-router.src.lib uses a module listed above it, which is the healthy direction.
27→33 packages.fetch-router.src.lib uses packages.fetch-router.src.lib.routerpart of a loop✕
Connections
4 pairs of types, where a type in packages.fetch-router.src.lib uses a type in packages.fetch-router.src.lib.router.
packages.fetch-router.src.lib uses packages.fetch-router.src.lib.router, so a change to packages.fetch-router.src.lib.router can break packages.fetch-router.src.lib, while a change to packages.fetch-router.src.lib can't break packages.fetch-router.src.lib.router.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.ui.src.listbox uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.ui.src.listbox, while a change to packages.ui.src.listbox can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.ui.src.listbox uses a module listed above it, which is the healthy direction.
packages.ui.src.listbox uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.ui.src.listbox, while a change to packages.ui.src.listbox can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.ui.src.listbox uses a module listed above it, which is the healthy direction.
docs.shared.ui uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break docs.shared.ui, while a change to docs.shared.ui can't break packages.component.src.runtime.component.
Position
Below the diagonal: docs.shared.ui uses a module listed above it, which is the healthy direction.
packages.auth.src.lib uses packages.fetch-router.src.lib.request-context, so a change to packages.fetch-router.src.lib.request-context can break packages.auth.src.lib, while a change to packages.auth.src.lib can't break packages.fetch-router.src.lib.request-context.
Position
Below the diagonal: packages.auth.src.lib uses a module listed above it, which is the healthy direction.
packages.auth.src.lib uses packages.auth.src.lib.provider, so a change to packages.auth.src.lib.provider can break packages.auth.src.lib, while a change to packages.auth.src.lib can't break packages.auth.src.lib.provider.
Position
Below the diagonal: packages.auth.src.lib uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins.mixin uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.component.src.runtime.mixins.mixin, while a change to packages.component.src.runtime.mixins.mixin can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.component.src.runtime.mixins.mixin uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins.mixin uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break packages.component.src.runtime.mixins.mixin, while a change to packages.component.src.runtime.mixins.mixin can't break packages.component.src.runtime.component.
Position
Below the diagonal: packages.component.src.runtime.mixins.mixin uses a module listed above it, which is the healthy direction.
packages.component.src.server.stream uses packages.component.src.runtime.reconcile, so a change to packages.component.src.runtime.reconcile can break packages.component.src.server.stream, while a change to packages.component.src.server.stream can't break packages.component.src.runtime.reconcile.
Position
Below the diagonal: packages.component.src.server.stream uses a module listed above it, which is the healthy direction.
packages.component.src.server.stream uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.component.src.server.stream, while a change to packages.component.src.server.stream can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.component.src.server.stream uses a module listed above it, which is the healthy direction.
packages.component.src.server.stream uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break packages.component.src.server.stream, while a change to packages.component.src.server.stream can't break packages.component.src.runtime.component.
Position
Below the diagonal: packages.component.src.server.stream uses a module listed above it, which is the healthy direction.
packages.fetch-router.src.lib.router uses packages.assets.src.lib, so a change to packages.assets.src.lib can break packages.fetch-router.src.lib.router, while a change to packages.fetch-router.src.lib.router can't break packages.assets.src.lib.
Position
Below the diagonal: packages.fetch-router.src.lib.router uses a module listed above it, which is the healthy direction.
packages.fetch-router.src.lib.router uses packages.fetch-router.src.lib, so a change to packages.fetch-router.src.lib can break packages.fetch-router.src.lib.router, while a change to packages.fetch-router.src.lib.router can't break packages.fetch-router.src.lib.
Position
Below the diagonal: packages.fetch-router.src.lib.router uses a module listed above it, which is the healthy direction.
packages.ui.src uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.ui.src, while a change to packages.ui.src can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.ui.src uses a module listed above it, which is the healthy direction.
packages.ui.src uses packages.assets.src.lib, so a change to packages.assets.src.lib can break packages.ui.src, while a change to packages.ui.src can't break packages.assets.src.lib.
Position
Below the diagonal: packages.ui.src uses a module listed above it, which is the healthy direction.
packages.ui.src uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break packages.ui.src, while a change to packages.ui.src can't break packages.component.src.runtime.component.
Position
Below the diagonal: packages.ui.src uses a module listed above it, which is the healthy direction.
packages.ui.src uses packages.ui.src.listbox, so a change to packages.ui.src.listbox can break packages.ui.src, while a change to packages.ui.src can't break packages.ui.src.listbox.
Position
Below the diagonal: packages.ui.src uses a module listed above it, which is the healthy direction.
packages.ui.src.animation uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.ui.src.animation, while a change to packages.ui.src.animation can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.ui.src.animation uses a module listed above it, which is the healthy direction.
packages.ui.src.animation uses packages.assets.src.lib, so a change to packages.assets.src.lib can break packages.ui.src.animation, while a change to packages.ui.src.animation can't break packages.assets.src.lib.
Position
Below the diagonal: packages.ui.src.animation uses a module listed above it, which is the healthy direction.
docs.shared.prerender uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break docs.shared.prerender, while a change to docs.shared.prerender can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: docs.shared.prerender uses a module listed above it, which is the healthy direction.
docs.shared.prerender uses packages.assets.src.lib.asset-server, so a change to packages.assets.src.lib.asset-server can break docs.shared.prerender, while a change to docs.shared.prerender can't break packages.assets.src.lib.asset-server.
Position
Below the diagonal: docs.shared.prerender uses a module listed above it, which is the healthy direction.
docs.shared.prerender uses packages.fetch-router.src.lib.router, so a change to packages.fetch-router.src.lib.router can break docs.shared.prerender, while a change to docs.shared.prerender can't break packages.fetch-router.src.lib.router.
Position
Below the diagonal: docs.shared.prerender uses a module listed above it, which is the healthy direction.
packages.auth.src.lib.providers uses packages.fetch-router.src.lib.request-context, so a change to packages.fetch-router.src.lib.request-context can break packages.auth.src.lib.providers, while a change to packages.auth.src.lib.providers can't break packages.fetch-router.src.lib.request-context.
Position
Below the diagonal: packages.auth.src.lib.providers uses a module listed above it, which is the healthy direction.
packages.auth.src.lib.providers uses packages.auth.src.lib.provider, so a change to packages.auth.src.lib.provider can break packages.auth.src.lib.providers, while a change to packages.auth.src.lib.providers can't break packages.auth.src.lib.provider.
Position
Below the diagonal: packages.auth.src.lib.providers uses a module listed above it, which is the healthy direction.
packages.auth.src.lib.providers uses packages.auth.src.lib, so a change to packages.auth.src.lib can break packages.auth.src.lib.providers, while a change to packages.auth.src.lib.providers can't break packages.auth.src.lib.
Position
Below the diagonal: packages.auth.src.lib.providers uses a module listed above it, which is the healthy direction.
packages.component.src.runtime uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.component.src.runtime, while a change to packages.component.src.runtime can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.component.src.runtime uses a module listed above it, which is the healthy direction.
packages.component.src.runtime uses packages.component.src.runtime.reconcile, so a change to packages.component.src.runtime.reconcile can break packages.component.src.runtime, while a change to packages.component.src.runtime can't break packages.component.src.runtime.reconcile.
Position
Below the diagonal: packages.component.src.runtime uses a module listed above it, which is the healthy direction.
packages.component.src.runtime uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.component.src.runtime, while a change to packages.component.src.runtime can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.component.src.runtime uses a module listed above it, which is the healthy direction.
packages.component.src.runtime uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break packages.component.src.runtime, while a change to packages.component.src.runtime can't break packages.component.src.runtime.component.
Position
Below the diagonal: packages.component.src.runtime uses a module listed above it, which is the healthy direction.
packages.component.src.runtime uses packages.component.src.server.stream, so a change to packages.component.src.server.stream can break packages.component.src.runtime, while a change to packages.component.src.runtime can't break packages.component.src.server.stream.
Position
Below the diagonal: packages.component.src.runtime uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins uses docs.shared.prerender.html-parser, so a change to docs.shared.prerender.html-parser can break packages.component.src.runtime.mixins, while a change to packages.component.src.runtime.mixins can't break docs.shared.prerender.html-parser.
Position
Below the diagonal: packages.component.src.runtime.mixins uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.component.src.runtime.mixins, while a change to packages.component.src.runtime.mixins can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.component.src.runtime.mixins uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins uses packages.assets.src.lib, so a change to packages.assets.src.lib can break packages.component.src.runtime.mixins, while a change to packages.component.src.runtime.mixins can't break packages.assets.src.lib.
Position
Below the diagonal: packages.component.src.runtime.mixins uses a module listed above it, which is the healthy direction.
packages.component.src.runtime.mixins uses packages.component.src.runtime.mixins.mixin, so a change to packages.component.src.runtime.mixins.mixin can break packages.component.src.runtime.mixins, while a change to packages.component.src.runtime.mixins can't break packages.component.src.runtime.mixins.mixin.
Position
Below the diagonal: packages.component.src.runtime.mixins uses a module listed above it, which is the healthy direction.
packages.component.src.server uses packages.component.src.runtime.reconcile, so a change to packages.component.src.runtime.reconcile can break packages.component.src.server, while a change to packages.component.src.server can't break packages.component.src.runtime.reconcile.
Position
Below the diagonal: packages.component.src.server uses a module listed above it, which is the healthy direction.
packages.component.src.server uses packages.component.src.runtime.core.vnode, so a change to packages.component.src.runtime.core.vnode can break packages.component.src.server, while a change to packages.component.src.server can't break packages.component.src.runtime.core.vnode.
Position
Below the diagonal: packages.component.src.server uses a module listed above it, which is the healthy direction.
packages.component.src.server uses packages.component.src.runtime.component, so a change to packages.component.src.runtime.component can break packages.component.src.server, while a change to packages.component.src.server can't break packages.component.src.runtime.component.
Position
Below the diagonal: packages.component.src.server uses a module listed above it, which is the healthy direction.
packages.component.src.server uses packages.component.src.server.stream, so a change to packages.component.src.server.stream can break packages.component.src.server, while a change to packages.component.src.server can't break packages.component.src.server.stream.
Position
Below the diagonal: packages.component.src.server uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 65% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
156
High / Critical
A03:2025 — Software Supply Chain Failures
45
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
Top priorities: 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; Adopt pino (or winston) and log at meaningful points in the services you run; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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.
Enforce accessibility in the toolchain you already use: add `jsx-a11y` to the `plugins` array in your oxlint config (its a11y rules are off until the plugin is listed), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Test Quality: No assertions (empty test): test one
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
packages/component/src/test/jsx.test.tsx
4.0
Mixed
Test Quality: No assertions (empty test): allows optional explicit narrowing for specific element kinds
REDACTED
4.2
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 177
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 — 843
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 — 188
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 87 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 87 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, 1177 of 1208 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `demos/i18n/app/i18n/config.ts`, `demos/i18n/app/i18n/locales/ar.ts`, `demos/i18n/app/i18n/locales/es.ts`, `demos/i18n/app/i18n/locales/fr.ts`, `demos/i18n/app/i18n/locales/ja.ts`, … (+78 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC5 ARIA correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 47 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/component/src/runtime/frame-runtime.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run preview`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "throw new ERR_UNKNOWN_FILE_EXTENSION(ext, filepath); / ^ / TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for <repo>/REDACTED / at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:219:9) / at defaultGetFormat (node:internal/modules/esm/get_format:245:36) / at defaultLoad (node:internal/modules/esm/load:120:22) / at async ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:483:32) / at async ModuleJob._link (node:internal/modules/esm/module_job:115:19) { / code: 'ERR_UNKNOWN_FILE_EXTENSION' / } / Node.js v22.13.0" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (preview). the dev server (`npm run preview`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "throw new ERR_UNKNOWN_FILE_EXTENSION(ext, filepath); / ^ / TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for <repo>/REDACTED / at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:219:9) / at defaultGetFormat (node:internal/modules/esm/get_format:245:36) / at defaultLoad (node:internal/modules/esm/load:120:22) / at async ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:483:32) / at async ModuleJob._link (node:internal/modules/esm/module_job:115:19) { / code: 'ERR_UNKNOWN_FILE_EXTENSION' / } / Node.js v22.13.0" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'pg' is imported (packages/data-table-postgres/src/lib/driver.ts:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'pg' is imported (packages/data-table-postgres/src/lib/driver.ts:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'pg' is imported (packages/data-table-postgres/src/lib/driver.ts:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'pg' is imported (packages/data-table-postgres/src/lib/driver.ts:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 160 further occurrence(s) are not listed individually; the score already reflects all 200.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 24 further occurrence(s) are not listed individually; the score already reflects all 64.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
115 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was compiler.createScriptCompiler at 112. 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 listbox.ListboxProvider at 18 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/ui/src/listbox.ts (listbox.ListboxProvider at 18), packages/node-hmr/src/register.ts (register.isBrowserHmrFileEventsMessage at 16). 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.
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with compiler.createScriptCompiler (cyclomatic 112), asset-server.createAssetServer (cyclomatic 87), menu.MenuProvider (cyclomatic 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.6 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 188 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with compiler.createScriptCompiler (cognitive 168), reconcile.insert (cognitive 123). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 3.0 to about 3.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.0 / 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 50 FunctionTooLong finding(s) in God Classes — start with compiler.ts (3), optimize-barrel-file-imports.ts (3), accordion.tsx (2). — One of this dimension's main actionable groups (50 warning-level).
Resolve the 29 FileTooLong finding(s) in God Classes — start with transform.ts (2), compiler.ts (2), dom.ts. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with multipart.ts (2). — One of this dimension's main actionable groups (2 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 · Coupling7.9 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
56 production modules (npm), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 53 of the 56 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @remix-run/data-schema · ×11
Unstable project @remix-run/cli
Unstable project @remix-run/static-middleware
Unstable project remix
What to do
Resolve the 11 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Unstable project @remix-run/cli finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project @remix-run/static-middleware finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Classify ADR enforcement: RoutePattern vs. URLPattern · ×8decisions/001-route-pattern-vs-url-pattern.md
What to do
Resolve the 8 Classify ADR enforcement finding(s) in Architectural Integrity — start with 001-route-pattern-vs-url-pattern.md, 002-branching-and-releasing.md, 003-coverage-transform-determinism.md. — One of this dimension's main actionable groups (8 recommendation-level).
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 93.9%. Measured from the JavaScript/TypeScript suite (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in packages/assert/; node:test in packages/node-fetch-server/: not run; node:test in packages/node-tsx/: not run; node:test in packages/terminal/: not run).
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution9.8 / 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.
6285 test methods: 6191 unit, 0 integration, 0 BDD, 94 e2e. The JavaScript/TypeScript suite contributes 6285 `it`/`test` case(s) across 392 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 Quality9.6 / 10Adequategated by 18 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
49 skipped (31 with a documented reason), 115 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6285 tests.
No assertions (empty test): test one · ×18packages/test/src/test/framework.test.ts:50
No assertions: runs server tests without loading Playwright · ×97packages/test/src/test/optional-playwright.test.ts:25
Skipped test: skip: can skip tests · ×18packages/test/src/test/framework.test.browser.ts:54
Fixed-sleep synchronisation: releases pending hydration metadata when its frame is disposedpackages/component/src/test/frame.test.ts:1028
Skipped (documented): arrow down/up selects first last when there is no selection · ×31packages/ui/src/select.test.tsx:585
What to do
Resolve the 18 No assertions (empty test) finding(s) in Test Quality — start with framework.test.ts (14), jsx.test.tsx (2), tar-size.test.ts. — One of this dimension's main actionable groups (18 issue-level).
Resolve the 97 No assertions finding(s) in Test Quality — start with jsx.test.tsx (16), router-types.test.ts (15), schema.test.ts (15). — One of this dimension's main actionable groups (97 warning-level).
Resolve the 18 Skipped test finding(s) in Test Quality — start with type-safety.test.ts (11), framework.test.ts (5), framework.test.browser.ts. — One of this dimension's main actionable groups (18 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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: 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 40 Hotspot finding(s) in Churn × Complexity Hotspots — start with compiler.ts (3), frame.ts, REDACTED. — One of this dimension's main actionable groups (40 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.7 / 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.
55 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts. Counted over 403 of the 932 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 · ×3
Further sole-owners (lower concentration)
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 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.
5 deducted task-comment markers across 156877 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 3 TodoComment finding(s) in Explicit Debt — start with documented-api.ts (2), stream.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with entry.ts, entry.tsx. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 8 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
5 naming inconsistencies among 174 declarations measured against a convention their peers follow.
`itemID` spells `ID` where 108 names in the project spell it `Id` · ×2packages/component/src/runtime/dom.ts:1602
`classID` spells `ID` where 108 names in the project spell it `Id`packages/component/src/runtime/dom.ts:3156
`RoutePatternJSON` spells `JSON` where 62 names in the project spell it `Json`packages/route-pattern/src/lib/route-pattern.ts:39
`toJSON` spells `JSON` where 62 names in the project spell it `Json`packages/route-pattern/src/lib/route-pattern.ts:127
What to do
Resolve the 2 `itemID` spells `ID` where 108 names in the project spell it `Id` finding(s) in Naming Consistency — start with dom.ts (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `classID` spells `ID` where 108 names in the project spell it `Id` finding(s) in Naming Consistency — start with dom.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `RoutePatternJSON` spells `JSON` where 62 names in the project spell it… finding(s) in Naming Consistency — start with route-pattern.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
51 domain type(s) cross context boundaries across 73 contexts; they are measured and withheld (not published, not scored). Contexts: assert, assets, async-context-middleware, auth, auth-middleware, bench, bookstore, bun, cf-workers, cli, component, component-hmr and 61 more.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×10packages/component/src/runtime/render.ts:5
What to do
Resolve the 16 redundant comment finding(s) in Comment Value — start with frame.test.tsx (3), changes-version.ts (2), changes.ts (2). — One of this dimension's main actionable groups (16 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 55 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
156 finding(s): 0 critical, 123 high, 31 medium, 2 low. 101 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 102 file(s) — `demos/i18n/app/i18n/config.ts` (lines 32–40, line 46, line 48, …), `demos/i18n/app/i18n/locales/ar.ts` (lines 4–72), `demos/i18n/app/i18n/locales/es.ts` (lines 3–68), `demos/i18n/app/i18n/locales/fr.ts` (lines 3–68), `demos/i18n/app/i18n/locales/ja.ts` (lines 3–64), … (+97 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 7 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
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 101 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (103 issue-level, 2 of them charged here).
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (16), REDACTED (3). — One of this dimension's main actionable groups (19 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 High 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.
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.
1 of 403 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/route-pattern/src/lib/route-pattern/split.ts. Counted over 403 of the 932 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.
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with driver.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels6.9 / 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.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — docs/shared/ui/docs-header.tsx:160
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — docs/shared/ui/table-of-contents.tsx:60
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.
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. — docs/site/app/ui/document.tsx:128
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — docs/site/app/ui/document.tsx:128, docs/ui/app/ui/document.tsx:46, packages/static-middleware/src/lib/directory-listing.ts:113, …
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 ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — docs/shared/ui/docs-header.tsx:112
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×7) — packages/ui/src/demos/animation/default-animate.tsx:31, packages/ui/src/demos/animation/default-animate.tsx:56, packages/ui/src/demos/animation/mixin-presence-list.tsx:32, …
`.ui-preview-card-content h3 a:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/ui/app/actions/public/ui.css:142
`.book-card` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — demos/bookstore/app/actions/public/app.css:172
`css-in-js object` moves (`animation: 'srgb-color 4s linear infinite'`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/ui/src/demos/animation/color-interpolation.tsx:51
`box.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — packages/ui/src/demos/animation/interruptible-keyframes.tsx:28, packages/ui/src/demos/animation/interruptible-keyframes.tsx:44
`css-in-js object` moves (`animation: 'box-animation 3s ease-in-out infinite'`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/ui/src/demos/animation/keyframes.tsx:23
`badgeEl.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — packages/ui/src/demos/animation/multi-state-badge.tsx:87, packages/ui/src/demos/animation/multi-state-badge.tsx:100
`node.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/ui/src/demos/animation/multi-state-badge.tsx:197
`css-in-js object` moves (`animation: `rotate-demo 1s ease-in-out 1``) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/ui/src/demos/animation/rotate.tsx:16
`htmlNode.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/ui/src/animation/animate-layout-mixin.ts:223
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 — your oxlint config does not list the `jsx-a11y` plugin (its a11y rules are off until it does) and there's no axe/pa11y/Lighthouse in tests or CI. Start by enabling that plugin to catch issues at author time. What was searched, so you can tell an absence from a miss: the 47 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. — REDACTED:15
What to do
Enforce accessibility in the toolchain you already use: add `jsx-a11y` to the `plugins` array in your oxlint config (its a11y rules are off until the plugin is listed), 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?
C2 · Access Controls7.0 / 10Strong✓ 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. — packages/auth-middleware/src/lib/require-auth.ts:57
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.
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.
`runVersionCommand` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/lib/commands/version.ts:8
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×3) — packages/data-table-mysql/src/lib/driver.ts:513, packages/data-table-mysql/src/lib/driver.ts:518, packages/headers/src/lib/super-headers.ts:1028
The guard above `return source;` also returns `source`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — packages/node-hmr/src/register.ts:141
`createBrowserHmrChannel` 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/node-hmr/src/runtime.ts:20
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×27) — packages/component/src/runtime/mixins/on-mixin.test.tsx:372, packages/data-table/src/lib/type-safety.test.ts:108, packages/data-table/src/lib/type-safety.test.ts:121, …
`write` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/terminal/src/lib/terminal.ts:139
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 20 of 99 project(s) that lack one — worth up to 0.4 pts.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
packages/remix/src/route-pattern/README.md links to `./bench/`, but `packages/remix/src/route-pattern/bench` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/remix/src/route-pattern/README.md:418
What to do
Reconcile the README with reality: packages/remix/src/route-pattern/README.md links to `./bench/`, but `packages/remix/src/route-pattern/bench` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability1.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 819 JavaScript/TypeScript production file(s) this check read across 82 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
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 911197 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:71
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:6
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.statSync` in `loadDemoModule` 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. — demos/ui/app/demo-runner/discovery.ts:70
`fs.existsSync` in `discoverDemoFiles` 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. — docs/site/app/data/demos.tsx:35
`fs.readFileSync` in `getDemoFile` 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. — docs/site/app/data/demos.tsx:97
`fs.readdirSync` in `walk` 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. — docs/site/app/data/markdown.ts:49
`fs.readFileSync` in `renderMarkdownFile` 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. — docs/site/app/data/markdown.ts:119
`fs.realpathSync` in `inspectRouteMatch` 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:121
`fs.realpathSync` in `runAssetsCommand` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/commands/assets.ts:30
`fs.writeFileSync` in `callback to http.createServer` 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/multipart-parser/demos/node/server.js:39
`closeSync` in `closeBranch` 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/ui/src/menu.tsx:388
`closeSync` in `closeAll` 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/ui/src/menu.tsx:411
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.
42 duplicated blocks under packages/ have copies in at least two of the sibling directories assets, cli, component, component-hmr, data-table-mysql, data-table-postgres (+15 more sibling(s) not listed) — 37 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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/data-table-mysql/src/lib/driver.ts:78
23 duplicated blocks under packages/assets/src/lib/ have copies in at least two of the sibling directories files, scripts, styles — 13 of them are reported below, and 10 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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/assets/src/lib/scripts/compiler.ts:1106
packages/data-table-mysql/src/lib/driver.ts:78 · packages/data-table-postgres/src/lib/driver.ts:72 — the two spans are one implementation copied and then locally edited — 1707 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/data-table-mysql/src/lib/driver.ts:78
packages/ui/src/accordion.tsx:13 · packages/ui/src/tabs.ts:14 — the two spans are one implementation copied and then locally edited — 1043 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/ui/src/accordion.tsx:13
packages/data-table-mysql/src/lib/sql-compiler.ts:1 · packages/data-table-sqlite/src/lib/sql-compiler.ts:1 — these 2 files are line-for-line copies of one another — 192 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/data-table-mysql/src/lib/sql-compiler.ts:1
packages/headers/src/lib/accept-language.ts:8 · packages/headers/src/lib/accept.ts:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/headers/src/lib/accept-language.ts:8
packages/headers/src/lib/accept-encoding.ts:70 · packages/headers/src/lib/accept-language.ts:75 · packages/headers/src/lib/accept.ts:74 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/headers/src/lib/accept-encoding.ts:70
packages/data-table-postgres/src/lib/sql-compiler.ts:545 · packages/data-table-sqlite/src/lib/sql-compiler.ts:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/data-table-postgres/src/lib/sql-compiler.ts:545
packages/fetch-router/src/lib/route-helpers/resource.ts:21 · packages/fetch-router/src/lib/route-helpers/resources.ts:28 — the two spans are one implementation copied and then locally edited — 459 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/fetch-router/src/lib/route-helpers/resource.ts:21
packages/assets/src/lib/scripts/resolve.ts:174 · packages/assets/src/lib/scripts/resolve.ts:331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/assets/src/lib/scripts/resolve.ts:174
packages/auth/src/lib/providers/facebook.ts:52 · packages/auth/src/lib/providers/x.ts:54 — the two spans are one implementation copied and then locally edited — 314 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/auth/src/lib/providers/facebook.ts:52
packages/form-data-parser/src/lib/form-data.ts:232 · packages/form-data-parser/src/lib/future/form-data.ts:271 — the two spans are one implementation copied and then locally edited — 263 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/form-data-parser/src/lib/form-data.ts:232
packages/multipart-parser/src/lib/future/multipart.ts:341 · packages/multipart-parser/src/lib/multipart.ts:511 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/multipart-parser/src/lib/future/multipart.ts:341
packages/node-tsx/src/lib/loader.ts:30 · packages/node-tsx/src/lib/register-hooks.ts:21 — the two spans are one implementation copied and then locally edited — 230 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/node-tsx/src/lib/loader.ts:30
packages/assets/src/lib/source-maps.ts:60 · packages/node-hmr/src/register.ts:275 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/source-maps.ts:60
packages/multipart-parser/src/lib/future/multipart.ts:291 · packages/multipart-parser/src/lib/multipart.ts:453 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/multipart-parser/src/lib/future/multipart.ts:291
packages/assets/src/lib/scripts/compiler.ts:1106 · packages/assets/src/lib/styles/compiler.ts:570 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/scripts/compiler.ts:1106
packages/data-table-postgres/src/lib/sql-compiler.ts:97 · packages/data-table-sqlite/src/lib/sql-compiler.ts:99 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/data-table-postgres/src/lib/sql-compiler.ts:97
packages/session-storage-memcache/src/lib/memcache-storage.ts:62 · packages/session/src/lib/session-storage/fs.ts:130 — the two spans are one implementation copied and then locally edited — 223 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/session-storage-memcache/src/lib/memcache-storage.ts:62
packages/data-table-postgres/src/lib/sql-compiler.ts:48 · packages/data-table-sqlite/src/lib/sql-compiler.ts:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/data-table-postgres/src/lib/sql-compiler.ts:48
packages/assets/src/lib/scripts/transform.ts:200 · packages/assets/src/lib/styles/transform.ts:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/assets/src/lib/scripts/transform.ts:200
packages/assets/src/lib/scripts/transform.ts:349 · packages/node-hmr/src/lib/hmr-analysis.ts:72 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/scripts/transform.ts:349
packages/component/src/runtime/run.ts:71 · packages/spa/src/lib/spa.ts:164 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/component/src/runtime/run.ts:71
packages/headers/src/lib/if-match.ts:7 · packages/headers/src/lib/if-none-match.ts:7 — the two spans are one implementation copied and then locally edited — 217 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/headers/src/lib/if-match.ts:7
packages/assets/src/lib/asset-server.ts:714 · packages/assets/src/lib/asset-server.ts:781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/assets/src/lib/asset-server.ts:714
packages/lazy-file/src/lib/lazy-file.ts:61 · packages/lazy-file/src/lib/lazy-file.ts:232 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/lazy-file/src/lib/lazy-file.ts:61
packages/data-table-postgres/src/lib/sql-compiler.ts:151 · packages/data-table-sqlite/src/lib/sql-compiler.ts:150 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/data-table-postgres/src/lib/sql-compiler.ts:151
packages/assets/src/lib/styles/resolve.ts:183 · packages/assets/src/lib/styles/resolve.ts:246 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/assets/src/lib/styles/resolve.ts:183
packages/assets/src/lib/scripts/emit.ts:52 · packages/assets/src/lib/styles/emit.ts:51 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/scripts/emit.ts:52
packages/component/src/server/stream.ts:1087 · packages/component/src/server/stream.ts:1162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/component/src/server/stream.ts:1087
scripts/detect-changed-packages.ts:188 · scripts/utils/workspaces.ts:78 — the two spans are one implementation copied and then locally edited — 160 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. — scripts/detect-changed-packages.ts:188
packages/assets/src/lib/module-store.ts:387 · packages/assets/src/lib/module-store.ts:418 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/assets/src/lib/module-store.ts:387
packages/data-table-mysql/src/lib/driver.ts:705 · packages/data-table-postgres/src/lib/driver.ts:652 · packages/data-table-sqlite/src/lib/driver.ts:539 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/data-table-mysql/src/lib/driver.ts:705
packages/data-table-postgres/src/lib/driver.ts:652 · packages/data-table-sqlite/src/lib/driver.ts:539 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/data-table-postgres/src/lib/driver.ts:652
packages/ui/src/combobox.tsx:30 · packages/ui/src/select.tsx:29 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/ui/src/combobox.tsx:30
packages/assets/src/lib/files/compiler.ts:507 · packages/assets/src/lib/styles/resolve.ts:157 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/files/compiler.ts:507
packages/component-hmr/src/lib/transform.ts:672 · packages/component-hmr/src/lib/transform.ts:699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/component-hmr/src/lib/transform.ts:672
packages/multipart-parser/src/lib/future/multipart.ts:226 · packages/multipart-parser/src/lib/multipart.ts:390 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/multipart-parser/src/lib/future/multipart.ts:226
packages/assets/src/lib/scripts/transform.ts:873 · packages/node-hmr/src/lib/hmr-analysis.ts:139 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/assets/src/lib/scripts/transform.ts:873
packages/multipart-parser/src/lib/future/multipart.ts:167 · packages/multipart-parser/src/lib/multipart.ts:331 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/multipart-parser/src/lib/future/multipart.ts:167
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
scripts/postinstall.ts:9 reaches into another package with a relative path (../packages/component/node_modules/playwright/cli.js) — import the package by name instead. — scripts/postinstall.ts:9
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.
(top-level) has cyclomatic complexity 87 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/route-pattern/src/lib/types/parse.ts:1
insert has cyclomatic complexity 59 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1162
compare has cyclomatic complexity 59 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/assert/src/lib/deep-equal.ts:278
isChildMessage has cyclomatic complexity 57 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1261
write has cyclomatic complexity 46 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/multipart-parser/src/lib/multipart.ts:298
main has cyclomatic complexity 45 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/publish.ts:399
executeRun has cyclomatic complexity 43 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/test/src/cli.ts:146
normalizeFilesOptions has cyclomatic complexity 43 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/assets/src/lib/files/config.ts:183
onResult has cyclomatic complexity 42 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/test/src/lib/reporters/spec.ts:20
write has cyclomatic complexity 42 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/multipart-parser/src/lib/future/multipart.ts:136
runTests has cyclomatic complexity 42 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/test/src/lib/executor.ts:43
parsePackageChanges has cyclomatic complexity 39 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/utils/changes.ts:188
getExportAnalysis has cyclomatic complexity 35 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:414
(anonymous) has cyclomatic complexity 34 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/multiple-import-maps-polyfill/src/lib/core.ts:271
buildElementSegment has cyclomatic complexity 34 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/component/src/server/stream.ts:663
matchPart has cyclomatic complexity 33 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/route-pattern/src/lib/match/program.ts:252
patchHostProps has cyclomatic complexity 33 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. — REDACTED:57
createFileResponse has cyclomatic complexity 33 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/response/src/lib/file.ts:129
walkForCommonJS has cyclomatic complexity 33 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/assets/src/lib/scripts/cjs-check.ts:49
resolveModule has cyclomatic complexity 32 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/assets/src/lib/scripts/resolve.ts:135
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files4.8 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/component/src/runtime/dom.ts has 3970 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/component/src/runtime/dom.ts:1
packages/component/src/runtime/frame.ts has 2006 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/component/src/runtime/frame.ts:1
REDACTED has 1901 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/component/src/server/stream.ts has 1781 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/component/src/server/stream.ts:1
packages/assets/src/lib/asset-server.ts has 1255 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/assets/src/lib/asset-server.ts:1
packages/component-hmr/src/lib/transform.ts has 1248 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/component-hmr/src/lib/transform.ts:1
REDACTED has 1248 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/data-schema/src/lib/schema.ts has 1199 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/data-schema/src/lib/schema.ts:1
packages/data-table/src/lib/table.ts has 1159 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/data-table/src/lib/table.ts:1
packages/ui/src/menu.tsx has 1096 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/ui/src/menu.tsx:1
packages/assets/src/lib/scripts/compiler.ts has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/assets/src/lib/scripts/compiler.ts:1
packages/headers/src/lib/super-headers.ts has 931 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/headers/src/lib/super-headers.ts:1
packages/data-table/src/lib/query.ts has 873 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/data-table/src/lib/query.ts:1
packages/data-table/src/lib/database.ts has 861 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/data-table/src/lib/database.ts:1
packages/assets/src/lib/scripts/transform.ts has 860 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/assets/src/lib/scripts/transform.ts:1
packages/ui/src/anchor.ts has 858 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/ui/src/anchor.ts:1
packages/component/src/runtime/diff-dom.ts has 833 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/component/src/runtime/diff-dom.ts:1
scripts/utils/changes.ts has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/utils/changes.ts:1
packages/ui/src/combobox.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. — packages/ui/src/combobox.tsx:1
scripts/generate-remix.ts 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. — scripts/generate-remix.ts:1
packages/assert/src/lib/assert.ts has 788 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/assert/src/lib/assert.ts:1
packages/component/src/runtime/navigation.ts has 774 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/component/src/runtime/navigation.ts:1
REDACTED has 761 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/assets/src/lib/scripts/resolve.ts has 749 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/assets/src/lib/scripts/resolve.ts:1
packages/assets/src/lib/files/compiler.ts has 748 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/assets/src/lib/files/compiler.ts:1
REDACTED has 741 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/node-fetch-server/src/lib/request-listener.ts has 683 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/node-fetch-server/src/lib/request-listener.ts:1
scripts/utils/preview.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/utils/preview.ts:1
packages/multipart-parser/src/lib/future/multipart.ts has 667 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/multipart-parser/src/lib/future/multipart.ts:1
REDACTED 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. — REDACTED:1
packages/data-table-mysql/src/lib/driver.ts has 641 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/data-table-mysql/src/lib/driver.ts:1
packages/data-table-postgres/src/lib/driver.ts has 637 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/data-table-postgres/src/lib/driver.ts:1
packages/cli/src/lib/completion.ts has 635 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/cli/src/lib/completion.ts:1
packages/multipart-parser/src/lib/multipart.ts has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/multipart-parser/src/lib/multipart.ts:1
REDACTED has 606 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/assets/src/lib/scripts/optimize-barrel-file-imports.ts has 602 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/assets/src/lib/scripts/optimize-barrel-file-imports.ts:1
packages/data-table/src/lib/database/query-execution.ts has 599 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/data-table/src/lib/database/query-execution.ts:1
packages/data-table-postgres/src/lib/sql-compiler.ts has 584 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/data-table-postgres/src/lib/sql-compiler.ts:1
packages/data-table-sqlite/src/lib/driver.ts has 582 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/data-table-sqlite/src/lib/driver.ts:1
scripts/publish.ts has 580 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/publish.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 Coverage9.4 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2 imports './fixtures/es-modules/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2
packages/multiple-import-maps-polyfill/test/fixtures/es-modules/import-relative-path.js:1 imports './relative-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/fixtures/es-modules/import-relative-path.js:1
packages/multiple-import-maps-polyfill/test/fixtures/es-modules/load-non-existent.js:1 imports './non-existent.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/fixtures/es-modules/load-non-existent.js:1
packages/multiple-import-maps-polyfill/test/polyfill.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/polyfill.test.browser.ts:3
packages/multiple-import-maps-polyfill/test/revoke-blob-urls.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/revoke-blob-urls.test.browser.ts:3
packages/multiple-import-maps-polyfill/test/revoke-blob-urls.ts:11 imports './fixtures/es-modules/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/revoke-blob-urls.ts:11
packages/multiple-import-maps-polyfill/test/shim.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/shim.test.browser.ts:3
packages/multiple-import-maps-polyfill/test/shim.ts:14 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/multiple-import-maps-polyfill/test/shim.ts:14
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. (×21) — packages/component/src/runtime/dom.ts:1, scripts/generate-remix.ts:1, scripts/publish.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts and 7 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2
Do you agree with this assessment?
R7 · Dead Code8.7 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 276 application, 22 tooling and 516 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 (276 application, 22 tooling, 516 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 (×3) — packages/cli/src/lib/load-route-map-worker.ts, scripts/node-test-reporter.ts, packages/node-fetch-server/src/lib/read-stream.ts
Nothing imports this binding — it is safe to review for removal. (×15) — packages/auth/src/lib/utils.ts:59, packages/cli/src/lib/errors.ts:234, packages/cli/src/lib/errors.ts:300, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×10) — packages/assets/src/lib/asset-server.test.ts:33, packages/auth-middleware/src/lib/auth-types.test.ts:151, packages/component-hmr/test/hmr.test.e2e.tsx:2820, …
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.
Every import is type-only — move it to devDependencies. — packages/data-schema/src/lib/schema.ts:1
Only test files import it (first: scripts/utils/preview.test.ts:3) — move it to devDependencies. — scripts/package.json:14
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
packages/data-table/src/lib/database/helpers.ts → packages/data-table/src/lib/database/query-execution.ts → packages/data-table/src/lib/database/helpers.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/data-table/src/lib/database/helpers.ts:21
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — docs/shared/hmr/run.ts:26
`server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) (×3) — docs/shared/server.ts:30, REDACTED:1133, template/server.ts:15
What to do
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.6 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`getPredicateColumns` is exported and takes `predicate: Predicate` from its caller, and it calls itself at line 378 (`getPredicateColumns`) with a piece of `predicate` — and nowhere in `getPredicateColumns` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getPredicateColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/data-table/src/lib/operators.ts:378
`quoteLiteral` is exported and takes `value: unknown` from its caller, and it calls itself at line 140 (`quoteLiteral`) with a piece of `value` — and nowhere in `quoteLiteral` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `quoteLiteral` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/data-table/src/lib/sql-helpers.ts:140
`renderToStream` is exported, takes a document from its caller (line 320) and hands it to `buildSegment`, which calls itself at line 560 (`buildSegment`) with a piece of `node` (and at line 570) — and nowhere in `buildSegment` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `buildSegment` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/component/src/server/stream.ts:560
`parseDocument` is exported, takes a document from its caller (line 3) and hands it to `removeNoscriptContents`, which calls itself at line 35 (`removeNoscriptContents`) with a piece of `source` — and nowhere in `removeNoscriptContents` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `removeNoscriptContents` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/component/src/runtime/parse-document.ts:35
`diffVNodes` is exported, takes a document from its caller (line 823) and hands it to `insert`, which calls itself at line 1351 (`insert`) with a piece of `node` — and nowhere in `insert` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `insert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:1351
`remove` is exported and takes `node: CommittedVNode` from its caller, and it calls itself at line 1573 (`remove`) with a piece of `node` (and at line 1579) — and nowhere in `remove` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:1573
`findFirstDomAnchor` is exported, takes a document from its caller (line 2052) and hands it to `findEdgeDomNode`, which calls itself at line 2063 (`findEdgeDomNode`) with a piece of `node` (and at line 2070) — and nowhere in `findEdgeDomNode` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `findEdgeDomNode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:2063
`isRemixNode` is exported and takes `value: unknown` from its caller, and it calls itself at line 218 (`isRemixNode`) with a piece of `value` — and nowhere in `isRemixNode` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isRemixNode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/component/src/runtime/core/vnode.ts:218
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 5/6 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`s3Fetch` 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:96
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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
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 unescaped4.9 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`content.trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/component/src/runtime/frame.ts:2150
`content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/component/src/runtime/parse-document.ts:26
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/component/src/runtime/prefetch.ts:380
`nextProps.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:952
`hostProps.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1126
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. (×19) — scripts/generate-remix.ts:169, scripts/postinstall.ts:167, scripts/utils/packages.ts:52, …
`.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. (×20) — packages/ui/src/animation/animate-layout-mixin.ts:245, packages/ui/src/animation/animate-mixins.ts:129, packages/ui/src/animation/animate-mixins.ts:148, …
`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. — packages/multiple-import-maps-polyfill/src/lib/native-resolve.ts:50
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.
~0.8 `!` null assertions per 1k TypeScript source lines — 93 assertion(s) across the 119041 source line(s) of the 594 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/multiple-import-maps-polyfill/src/lib/core.ts (16), REDACTED (15), docs/site/scripts/generate/documented-api.ts (8). 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 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'pg' (packages/data-table-postgres/src/lib/driver.ts:14) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'pg' (packages/data-table-postgres/src/lib/driver.ts:14) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'pg' (packages/data-table-postgres/src/lib/driver.ts:14) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 39 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC4 Keyboard semantics — AC4 could not be measured here. This repository renders user interface from HTML strings built in plain scripts — 15 script file(s) building 78 markup element(s) as HTML strings, carrying 47 role/aria/tabindex attribute(s) (e.g. packages/multiple-import-maps-polyfill/src/lib/features.ts, packages/component/src/server/stream.ts, docs/ui/app/pages/patterns/accordion.tsx) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no interactive element from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no interactive element.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run preview`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "throw new ERR_UNKNOWN_FILE_EXTENSION(ext, filepath); / ^ / TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for <repo>/REDACTED / at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:219:9) / at defaultGetFormat (node:internal/modules/esm/get_format:245:36) / at defaultLoad (node:internal/modules/esm/load:120:22) / at async ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:483:32) / at async ModuleJob._link (node:internal/modules/esm/module_job:115:19) { / code: 'ERR_UNKNOWN_FILE_EXTENSION' / } / Node.js v22.13.0" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'pg' (packages/data-table-postgres/src/lib/driver.ts:14) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
D12 Dependency Hygiene — Dependency currency not established — registry.npmjs.org did not answer
D14 License Compliance — Not scored — this repository's 529 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 133 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — 83 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: template/hmr.ts:23 (http.createServer())
P9 Domain vs controller coverage — coverage data present for 4 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
D10 · Test Quality· No assertions (empty test) · ×18
No assertions (empty test): test one packages/test/src/test/framework.test.ts:50— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test two packages/test/src/test/framework.test.ts:51— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test packages/test/src/test/framework.test.ts:93— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test packages/test/src/test/framework.test.ts:105— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test packages/test/src/test/framework.test.ts:119— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test packages/test/src/test/framework.test.ts:133— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test packages/test/src/test/framework.test.ts:164— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): my test packages/test/src/test/framework.test.ts:225— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): skipped test packages/test/src/test/framework.test.ts:235— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): todo test packages/test/src/test/framework.test.ts:236— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): my test packages/test/src/test/framework.test.ts:248— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): only test packages/test/src/test/framework.test.ts:293— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): same name packages/test/src/test/framework.test.ts:362— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): same name packages/test/src/test/framework.test.ts:363— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): allows entries exactly at the default limit and explicit larger limits packages/tar-parser/src/lib/tar-size.test.ts:320— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): allows optional explicit narrowing for specific element kinds packages/component/src/test/jsx.test.tsx:350— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): allows base descriptors on subtype hosts without allowing the inverse packages/component/src/test/jsx.test.tsx:358— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): propagates auth state into controller and action contracts packages/auth-middleware/src/lib/auth-types.test.ts:193— Test method has an empty body — it asserts nothing and exercises no code.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text docs/shared/ui/docs-header.tsx:160— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name docs/shared/ui/table-of-contents.tsx:60— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> docs/site/app/ui/document.tsx:128— 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.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×1
aria-hidden on a focusable element docs/shared/ui/docs-header.tsx:112— aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
No assertions: runs server tests without loading Playwright packages/test/src/test/optional-playwright.test.ts:25— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: treats missing keys as a successful delete packages/session-storage-memcache/src/lib/memcache-client.test.ts:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: cancels internal frame requests with the original request packages/render-middleware/src/lib/render-ui.test.ts:552— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: derives renderer context from middleware packages/render-middleware/src/lib/render.test.ts:87— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when an accepted dependency is not statically analyzable packages/node-hmr/src/lib/hmr-analysis.test.ts:163— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when the first accept argument is an unsupported literal packages/node-hmr/src/lib/hmr-analysis.test.ts:174— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when the first accept argument is null packages/node-hmr/src/lib/hmr-analysis.test.ts:181— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when the first accept argument is an object packages/node-hmr/src/lib/hmr-analysis.test.ts:188— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when an accepted dependency array is not statically analyzable packages/node-hmr/src/lib/hmr-analysis.test.ts:195— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when an accepted dependency array contains a non-string item packages/node-hmr/src/lib/hmr-analysis.test.ts:208— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws when an accepted dependency array contains a spread element packages/node-hmr/src/lib/hmr-analysis.test.ts:219— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should support dynamic import with an import map packages/multiple-import-maps-polyfill/test/polyfill.ts:18— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should support multiple import maps packages/multiple-import-maps-polyfill/test/polyfill.ts:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: import maps passthrough polyfill mode packages/multiple-import-maps-polyfill/test/polyfill.ts:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Dynamic import map shim with override to the same mapping is allowed packages/multiple-import-maps-polyfill/test/shim.ts:322— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not eagerly use Web Encoding globals while importing and parsing packages/multipart-parser/src/lib/multipart.test.ts:305— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not eagerly use Web Encoding globals while importing and parsing packages/multipart-parser/src/lib/future/multipart.test.ts:417— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not type constructor keys as available unless they are in context packages/fetch-router/src/lib/request-context.test.ts:95— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: derives direct property types from context entries packages/fetch-router/src/lib/request-context.test.ts:250— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not derive direct property types from broad string properties packages/fetch-router/src/lib/request-context.test.ts:267— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keeps direct property types independent from entries without properties packages/fetch-router/src/lib/request-context.test.ts:289— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: derives direct property types from the last entry that declares the property packages/fetch-router/src/lib/request-context.test.ts:310— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: derives app context from a router with inline middleware packages/fetch-router/src/lib/router-types.test.ts:151— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: derives context from middleware factory return types packages/fetch-router/src/lib/router-types.test.ts:168— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: types stored actions with route params and explicit app context packages/fetch-router/src/lib/router-types.test.ts:189— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
FunctionTooLong: runner.createHmrSupervisor REDACTED:211— FunctionTooLong — createHmrSupervisor runs 547 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 447 over it, 5.47× 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: compiler.createScriptCompiler packages/assets/src/lib/scripts/compiler.ts:148— FunctionTooLong — createScriptCompiler runs 508 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 408 over it, 5.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: frame.createFrame packages/component/src/runtime/frame.ts:308— FunctionTooLong — createFrame 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: accordion.AccordionPage docs/ui/app/pages/patterns/accordion.tsx:121— FunctionTooLong — AccordionPage runs 395 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 295 over it, 3.95× 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: asset-server.createAssetServer packages/assets/src/lib/asset-server.ts:413— FunctionTooLong — createAssetServer runs 388 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 288 over it, 3.88× 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: combobox.ComboboxProvider packages/ui/src/combobox.tsx:152— FunctionTooLong — ComboboxProvider runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× 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: combobox.ComboboxPage docs/ui/app/pages/patterns/combobox.tsx:131— FunctionTooLong — ComboboxPage runs 344 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 244 over it, 3.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: menu.MenuPage docs/ui/app/pages/patterns/menu.tsx:196— FunctionTooLong — MenuPage runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: menu.MenuProvider packages/ui/src/menu.tsx:235— FunctionTooLong — MenuProvider runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× 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: listbox.ListboxPage docs/ui/app/pages/patterns/listbox.tsx:192— FunctionTooLong — ListboxPage runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: docs-header.DocsHeader docs/shared/ui/docs-header.tsx:39— FunctionTooLong — DocsHeader runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: select.SelectPage docs/ui/app/pages/patterns/select.tsx:123— FunctionTooLong — SelectPage runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: compiler.createFileCompiler packages/assets/src/lib/files/compiler.ts:122— FunctionTooLong — createFileCompiler runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× 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: compiler.createStyleCompiler packages/assets/src/lib/styles/compiler.ts:94— FunctionTooLong — createStyleCompiler runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tabs.TabsPage docs/ui/app/pages/patterns/tabs.tsx:163— FunctionTooLong — TabsPage runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: resolve.resolveModule packages/assets/src/lib/scripts/resolve.ts:135— FunctionTooLong — resolveModule runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: home-page.HomePage template/app/actions/home-page.tsx:8— FunctionTooLong — HomePage runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: s3.createS3FileStorage REDACTED:80— FunctionTooLong — createS3FileStorage runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: expect.createMatchers packages/assert/src/lib/expect.ts:203— FunctionTooLong — createMatchers runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: select.SelectProvider packages/ui/src/select.tsx:95— FunctionTooLong — SelectProvider runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: publish.main scripts/publish.ts:399— FunctionTooLong — main runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: spring.SpringPage docs/ui/app/pages/animation/spring.tsx:75— FunctionTooLong — SpringPage runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: router.createRouter packages/fetch-router/src/lib/router.ts:362— FunctionTooLong — createRouter runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: anchor.AnchorPage docs/ui/app/pages/patterns/anchor.tsx:120— FunctionTooLong — AnchorPage runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: scheduler.createScheduler packages/component/src/runtime/scheduler.ts:61— FunctionTooLong — createScheduler runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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.
Hotspot: packages/component/src/runtime/frame.ts packages/component/src/runtime/frame.ts:308— packages/component/src/runtime/frame.ts changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 103 in frame.createFrame at line 308. 2 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/component/src/runtime/frame.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:1162— REDACTED changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in reconcile.insert at line 1162. 1 of those changes was a fix/bug commit, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05: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/component/src/runtime/navigation.ts packages/component/src/runtime/navigation.ts:337— packages/component/src/runtime/navigation.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in navigation.startNavigationListenerImpl at line 337. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/component/src/runtime/navigation.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/component/src/server/stream.ts packages/component/src/server/stream.ts:663— packages/component/src/server/stream.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in stream.buildElementSegment at line 663. 3 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/component/src/server/stream.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/assets/src/lib/scripts/compiler.ts packages/assets/src/lib/scripts/compiler.ts:148— packages/assets/src/lib/scripts/compiler.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 112 in compiler.createScriptCompiler at line 148. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/scripts/compiler.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/assets/src/lib/asset-server.ts packages/assets/src/lib/asset-server.ts:413— packages/assets/src/lib/asset-server.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 87 in asset-server.createAssetServer at line 413. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/asset-server.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: demos/timeboxer/app/actions/schedules/public/schedule-grid.tsx demos/timeboxer/app/actions/schedules/public/schedule-grid.tsx:116— demos/timeboxer/app/actions/schedules/public/schedule-grid.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 137 in schedule-grid.ScheduleGrid at line 116. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- demos/timeboxer/app/actions/schedules/public/schedule-grid.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/component/src/runtime/diff-dom.ts packages/component/src/runtime/diff-dom.ts:55— packages/component/src/runtime/diff-dom.ts changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in diff-dom.diffNode at line 55. 2 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/component/src/runtime/diff-dom.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:211— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 117 in runner.createHmrSupervisor at line 211. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05: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: scripts/publish.ts scripts/publish.ts:399— scripts/publish.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in publish.main at line 399. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- scripts/publish.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/assets/src/lib/module-store.ts packages/assets/src/lib/module-store.ts:94— packages/assets/src/lib/module-store.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in module-store.createModuleStore at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/module-store.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: scripts/generate-remix.ts scripts/generate-remix.ts:263— scripts/generate-remix.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in generate-remix.updateRemixPackage 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- scripts/generate-remix.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/multipart-parser/src/lib/multipart.ts packages/multipart-parser/src/lib/multipart.ts:298— packages/multipart-parser/src/lib/multipart.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in MultipartParser.write at line 298. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/multipart-parser/src/lib/multipart.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/assets/src/lib/styles/compiler.ts packages/assets/src/lib/styles/compiler.ts:94— packages/assets/src/lib/styles/compiler.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in compiler.createStyleCompiler at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/styles/compiler.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:57— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in props.patchHostProps at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05: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/assets/src/lib/scripts/resolve.ts packages/assets/src/lib/scripts/resolve.ts:135— packages/assets/src/lib/scripts/resolve.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in resolve.resolveModule at line 135. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/scripts/resolve.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/assets/src/lib/files/compiler.ts packages/assets/src/lib/files/compiler.ts:122— packages/assets/src/lib/files/compiler.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in compiler.createFileCompiler at line 122. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/assets/src/lib/files/compiler.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: docs/site/app/ui/document.tsx docs/site/app/ui/document.tsx:315— docs/site/app/ui/document.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in document.DocsNavigation.<returned closure> at line 315. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- docs/site/app/ui/document.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: docs/shared/ui/public/docs-shell.tsx docs/shared/ui/public/docs-shell.tsx:32— docs/shared/ui/public/docs-shell.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in docs-shell.startDocsShellBehavior at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- docs/shared/ui/public/docs-shell.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/response/src/lib/file.ts packages/response/src/lib/file.ts:129— packages/response/src/lib/file.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in file.createFileResponse at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/response/src/lib/file.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: scripts/utils/preview.ts scripts/utils/preview.ts:366— scripts/utils/preview.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in preview.publishPreview at line 366. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- scripts/utils/preview.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/fetch-proxy/src/lib/fetch-proxy.ts packages/fetch-proxy/src/lib/fetch-proxy.ts:99— packages/fetch-proxy/src/lib/fetch-proxy.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in fetch-proxy.createFetchProxy.<returned closure> at line 99. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/fetch-proxy/src/lib/fetch-proxy.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/ui/src/demos/animation/spring.demo.tsx packages/ui/src/demos/animation/spring.demo.tsx:12— packages/ui/src/demos/animation/spring.demo.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in spring.demo.PointerTrail at line 12. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- packages/ui/src/demos/animation/spring.demo.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: docs/site/scripts/generate/documented-api.ts docs/site/scripts/generate/documented-api.ts:767— docs/site/scripts/generate/documented-api.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in documented-api.processApiComment at line 767. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- docs/site/scripts/generate/documented-api.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: docs/site/app/data/registry.ts docs/site/app/data/registry.ts:60— docs/site/app/data/registry.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in registry.buildRegistry at line 60. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 10:05:33 -05:00' --until='2026-11-06 10:05:33 -05:00' --full-history --no-merges -- docs/site/app/data/registry.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Swallowed exception (empty catch) scripts/generate-remix.ts:169— 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) scripts/postinstall.ts:167— 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) scripts/utils/packages.ts:52— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/utils/packages.ts:150— 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/ui/src/animation/animate-layout-mixin.ts:245— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/ui/src/animation/animate-mixins.ts:129— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/ui/src/animation/animate-mixins.ts:148— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/ui/src/animation/animate-mixins.ts:213— 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) REDACTED:517— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/static-middleware/src/lib/directory-listing.ts:35— 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/static-middleware/src/lib/static.ts:158— 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/static-middleware/src/lib/static.ts:168— 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/session-middleware/src/lib/session.ts:94— 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/session/src/lib/session-storage/cookie.ts:19— 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/session/src/lib/session-storage/fs.ts:85— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/multiple-import-maps-polyfill/src/lib/core.ts:265— 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/multiple-import-maps-polyfill/src/lib/features.ts:83— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/multiple-import-maps-polyfill/src/lib/polyfill.ts:16— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/multiple-import-maps-polyfill/src/lib/polyfill.ts:81— 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/multiple-import-maps-polyfill/src/lib/resolve.ts:18— 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/multiple-import-maps-polyfill/src/lib/trusted-types.ts:40— 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/multipart-parser/src/lib/future/multipart.ts:511— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/multipart-parser/src/lib/future/multipart.ts:659— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/fs/src/lib/fs.ts:125— `.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) REDACTED:169— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
FileTooLong: runtime/dom.ts packages/component/src/runtime/dom.ts— FileTooLong — 2024 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1524 over it, 4.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: runtime/frame.ts packages/component/src/runtime/frame.ts— FileTooLong — 1582 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1082 over it, 3.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1001 over it, 3.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.
FileTooLong: server/stream.ts packages/component/src/server/stream.ts— FileTooLong — 1334 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 834 over it, 2.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/transform.ts packages/component-hmr/src/lib/transform.ts— FileTooLong — 988 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 488 over it, 1.98× 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 — 972 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 472 over it, 1.94× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/menu.tsx packages/ui/src/menu.tsx— FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 351 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: lib/asset-server.ts packages/assets/src/lib/asset-server.ts— FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 300 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: lib/super-headers.ts packages/headers/src/lib/super-headers.ts— FileTooLong — 783 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 283 over it, 1.57× 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: scripts/compiler.ts packages/assets/src/lib/scripts/compiler.ts— FileTooLong — 775 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: createScriptCompiler (148-912). The bar is 500 significant lines; this is 275 over it, 1.55× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/query.ts packages/data-table/src/lib/query.ts— FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 226 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: lib/table.ts packages/data-table/src/lib/table.ts— FileTooLong — 702 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 202 over it, 1.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/anchor.ts packages/ui/src/anchor.ts— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/schema.ts packages/data-schema/src/lib/schema.ts— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scripts/transform.ts packages/assets/src/lib/scripts/transform.ts— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 159 over it, 1.32× 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: runtime/diff-dom.ts packages/component/src/runtime/diff-dom.ts— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/combobox.tsx packages/ui/src/combobox.tsx— FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: ComboboxProvider (152-742). The bar is 500 significant lines; this is 123 over it, 1.25× 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: lib/database.ts packages/data-table/src/lib/database.ts— FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: Database (363-979). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: scripts/resolve.ts packages/assets/src/lib/scripts/resolve.ts— FileTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 86 over it, 1.17× 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: scripts/generate-remix.ts scripts/generate-remix.ts— FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 81 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: files/compiler.ts packages/assets/src/lib/files/compiler.ts— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 76 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: utils/changes.ts scripts/utils/changes.ts— FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 56 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: generate/documented-api.ts docs/site/scripts/generate/documented-api.ts— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 52 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: utils/preview.ts scripts/utils/preview.ts— FileTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 47 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: REDACTED REDACTED— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
+ 4 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×21
No test reaches this file packages/component/src/runtime/dom.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 scripts/generate-remix.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 scripts/publish.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 scripts/detect-changed-packages.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 scripts/postinstall.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 scripts/changes-version.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 scripts/release-pr.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/src/lib/load-route-map-worker.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 scripts/preview-pr.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/node-tsx/src/lib/register-hooks.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/changes-preview.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 scripts/copy-package-type-only-exports.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 template/hmr.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 scripts/test-browser.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 template/server.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 scripts/node-test-reporter.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 template/app/actions/public/entry.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 scripts/sync-cli-template.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/node-fetch-server/src/lib/read-stream.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 scripts/sync-remix-package-files.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.
Skipped test: skip: can skip tests packages/test/src/test/framework.test.browser.ts:54— Skipped — switched off by it.skip
Skipped test: skipped test packages/test/src/test/framework.test.ts:260— Skipped — switched off by it.skip
Skipped test: no fn packages/test/src/test/framework.test.ts:269— Skipped — switched off by it.skip
Skipped test: with fn packages/test/src/test/framework.test.ts:279— Skipped — switched off by it.skip
Skipped test: without fn packages/test/src/test/framework.test.ts:280— Skipped — switched off by it.skip
Skipped test: skip: can skip tests packages/test/src/test/framework.test.ts:516— Skipped — switched off by it.skip
Skipped test: infers unvalidated column types from physical types and falls back to unknown packages/data-table/src/lib/type-safety.test.ts:108— Skipped — switched off by it.skip
Skipped test: types transaction callbacks as Database packages/data-table/src/lib/type-safety.test.ts:121— Skipped — switched off by it.skip
Skipped test: uses Database as both the public class and instance type packages/data-table/src/lib/type-safety.test.ts:127— Skipped — switched off by it.skip
Skipped test: exposes Query generics as column and row output maps packages/data-table/src/lib/type-safety.test.ts:151— Skipped — switched off by it.skip
Skipped test: types query(table) and db.exec(...) for unbound queries in every execution mode packages/data-table/src/lib/type-safety.test.ts:207— Skipped — switched off by it.skip
Skipped test: narrows select() result types while preserving relation types packages/data-table/src/lib/type-safety.test.ts:334— Skipped — switched off by it.skip
Skipped test: supports typed alias select() and joined order/group columns packages/data-table/src/lib/type-safety.test.ts:347— Skipped — switched off by it.skip
Skipped test: enforces typed keys for where/having/join/relation filters packages/data-table/src/lib/type-safety.test.ts:391— Skipped — switched off by it.skip
Skipped test: keeps findOne/findMany where and orderBy typing symmetric for single-table queries packages/data-table/src/lib/type-safety.test.ts:425— Skipped — switched off by it.skip
Skipped test: keeps update/delete helper typing symmetric for single-table queries packages/data-table/src/lib/type-safety.test.ts:471— Skipped — switched off by it.skip
Skipped test: supports typed create/createMany helper return modes packages/data-table/src/lib/type-safety.test.ts:519— Skipped — switched off by it.skip
Skipped test: infers types in jsx for `event`, `event.currentTarget`, and `signal` packages/component/src/runtime/mixins/on-mixin.test.tsx:372— Skipped — switched off by it.skip
Off the main sequence: @remix-run/data-schema — @remix-run/data-schema: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @remix-run/mime — @remix-run/mime: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: @remix-run/node-tsx — @remix-run/node-tsx: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @remix-run/route-pattern — @remix-run/route-pattern: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @remix-run/tar-parser — @remix-run/tar-parser: 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: @remix-run/data-table — @remix-run/data-table: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @remix-run/headers — @remix-run/headers: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: @remix-run/session — @remix-run/session: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: @remix-run/component-hmr — @remix-run/component-hmr: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @remix-run/component — @remix-run/component: abstractness 0.28, instability 0.00, distance 0.72 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @remix-run/fetch-router — @remix-run/fetch-router: abstractness 0.24, instability 0.06, distance 0.71 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×10
Animation without a prefers-reduced-motion guard demos/bookstore/app/actions/public/app.css:172— `.book-card` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/color-interpolation.tsx:51— `css-in-js object` moves (`animation: 'srgb-color 4s linear infinite'`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/interruptible-keyframes.tsx:28— `box.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/interruptible-keyframes.tsx:44— `box.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/keyframes.tsx:23— `css-in-js object` moves (`animation: 'box-animation 3s ease-in-out infinite'`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/multi-state-badge.tsx:87— `badgeEl.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/multi-state-badge.tsx:100— `badgeEl.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/multi-state-badge.tsx:197— `node.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/demos/animation/rotate.tsx:16— `css-in-js object` moves (`animation: `rotate-demo 1s ease-in-out 1``) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/ui/src/animation/animate-layout-mixin.ts:223— `htmlNode.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Sync-over-async blocking demos/ui/app/demo-runner/discovery.ts:70— `fs.statSync` in `loadDemoModule` 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 docs/site/app/data/demos.tsx:35— `fs.existsSync` in `discoverDemoFiles` 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 docs/site/app/data/demos.tsx:97— `fs.readFileSync` in `getDemoFile` 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 docs/site/app/data/markdown.ts:49— `fs.readdirSync` in `walk` 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 docs/site/app/data/markdown.ts:119— `fs.readFileSync` in `renderMarkdownFile` 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:121— `fs.realpathSync` in `inspectRouteMatch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/commands/assets.ts:30— `fs.realpathSync` in `runAssetsCommand` 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/multipart-parser/demos/node/server.js:39— `fs.writeFileSync` in `callback to http.createServer` 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/ui/src/menu.tsx:388— `closeSync` in `closeBranch` 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/ui/src/menu.tsx:411— `closeSync` in `closeAll` 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.
R4 · Test Coverage· This test file cannot be loaded · ×8
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2— packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2 imports './fixtures/es-modules/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/fixtures/es-modules/import-relative-path.js:1— packages/multiple-import-maps-polyfill/test/fixtures/es-modules/import-relative-path.js:1 imports './relative-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/fixtures/es-modules/load-non-existent.js:1— packages/multiple-import-maps-polyfill/test/fixtures/es-modules/load-non-existent.js:1 imports './non-existent.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/polyfill.test.browser.ts:3— packages/multiple-import-maps-polyfill/test/polyfill.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/revoke-blob-urls.test.browser.ts:3— packages/multiple-import-maps-polyfill/test/revoke-blob-urls.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/revoke-blob-urls.ts:11— packages/multiple-import-maps-polyfill/test/revoke-blob-urls.ts:11 imports './fixtures/es-modules/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/shim.test.browser.ts:3— packages/multiple-import-maps-polyfill/test/shim.test.browser.ts:3 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/multiple-import-maps-polyfill/test/shim.ts:14— packages/multiple-import-maps-polyfill/test/shim.ts:14 imports './', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×8
Recursive walk over a caller-supplied document has no depth cap packages/data-table/src/lib/operators.ts:378— `getPredicateColumns` is exported and takes `predicate: Predicate` from its caller, and it calls itself at line 378 (`getPredicateColumns`) with a piece of `predicate` — and nowhere in `getPredicateColumns` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getPredicateColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/data-table/src/lib/sql-helpers.ts:140— `quoteLiteral` is exported and takes `value: unknown` from its caller, and it calls itself at line 140 (`quoteLiteral`) with a piece of `value` — and nowhere in `quoteLiteral` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `quoteLiteral` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/component/src/server/stream.ts:560— `renderToStream` is exported, takes a document from its caller (line 320) and hands it to `buildSegment`, which calls itself at line 560 (`buildSegment`) with a piece of `node` (and at line 570) — and nowhere in `buildSegment` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `buildSegment` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/component/src/runtime/parse-document.ts:35— `parseDocument` is exported, takes a document from its caller (line 3) and hands it to `removeNoscriptContents`, which calls itself at line 35 (`removeNoscriptContents`) with a piece of `source` — and nowhere in `removeNoscriptContents` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `removeNoscriptContents` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap REDACTED:1351— `diffVNodes` is exported, takes a document from its caller (line 823) and hands it to `insert`, which calls itself at line 1351 (`insert`) with a piece of `node` — and nowhere in `insert` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `insert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap REDACTED:1573— `remove` is exported and takes `node: CommittedVNode` from its caller, and it calls itself at line 1573 (`remove`) with a piece of `node` (and at line 1579) — and nowhere in `remove` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap REDACTED:2063— `findFirstDomAnchor` is exported, takes a document from its caller (line 2052) and hands it to `findEdgeDomNode`, which calls itself at line 2063 (`findEdgeDomNode`) with a piece of `node` (and at line 2070) — and nowhere in `findEdgeDomNode` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `findEdgeDomNode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/component/src/runtime/core/vnode.ts:218— `isRemixNode` is exported and takes `value: unknown` from its caller, and it calls itself at line 218 (`isRemixNode`) with a piece of `value` — and nowhere in `isRemixNode` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isRemixNode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×5
Untrusted text written into markup unescaped packages/component/src/runtime/frame.ts:2150— `content.trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/component/src/runtime/parse-document.ts:26— `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/component/src/runtime/prefetch.ts:380— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:952— `nextProps.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:1126— `hostProps.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark docs/site/app/ui/document.tsx:128— 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 docs/ui/app/ui/document.tsx:46— 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 packages/static-middleware/src/lib/directory-listing.ts:113— 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 template/app/actions/document.tsx:21— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
sql-compiler.compilePredicate (cyclomatic 29) packages/data-table-mysql/src/lib/sql-compiler.ts:300— sql-compiler.compilePredicate has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sql-compiler.compilePredicate (cyclomatic 29) packages/data-table-postgres/src/lib/sql-compiler.ts:588— sql-compiler.compilePredicate has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sql-compiler.compilePredicate (cyclomatic 29) packages/data-table-sqlite/src/lib/sql-compiler.ts:345— sql-compiler.compilePredicate has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TodoComment packages/component/src/server/stream.ts:1096— // TODO: need better vnode types to avoid defensive checks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment docs/site/scripts/generate/documented-api.ts:352— //TODO: We my need to do manual signature construction for types with generics — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment docs/site/scripts/generate/documented-api.ts:714— // TODO: Cross-link to the class — 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.
sql-compiler.compilePredicate (cognitive 53) packages/data-table-mysql/src/lib/sql-compiler.ts:300— sql-compiler.compilePredicate has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (33 pts), ternaries 5 (15 pts), boolean chains 5 (nesting depth added 26). 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.
sql-compiler.compilePredicate (cognitive 53) packages/data-table-postgres/src/lib/sql-compiler.ts:588— sql-compiler.compilePredicate has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (33 pts), ternaries 5 (15 pts), boolean chains 5 (nesting depth added 26). 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.
sql-compiler.compilePredicate (cognitive 53) packages/data-table-sqlite/src/lib/sql-compiler.ts:345— sql-compiler.compilePredicate has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (33 pts), ternaries 5 (15 pts), boolean chains 5 (nesting depth added 26). 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.
IC1 · Incompleteness & stubs· Both branches are identical · ×3
Both branches are identical — the condition decides nothing packages/data-table-mysql/src/lib/driver.ts:513— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/data-table-mysql/src/lib/driver.ts:518— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/headers/src/lib/super-headers.ts:1028— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Duplicated block (25 lines × 2 locations) packages/assets/src/lib/module-store.ts:387— packages/assets/src/lib/module-store.ts:387 · packages/assets/src/lib/module-store.ts:418 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) packages/data-table-postgres/src/lib/driver.ts:652— packages/data-table-postgres/src/lib/driver.ts:652 · packages/data-table-sqlite/src/lib/driver.ts:539 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (25 lines × 2 locations) packages/ui/src/combobox.tsx:30— packages/ui/src/combobox.tsx:30 · packages/ui/src/select.tsx:29 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2 locations) packages/assets/src/lib/files/compiler.ts:507— packages/assets/src/lib/files/compiler.ts:507 · packages/assets/src/lib/styles/resolve.ts:157 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (24 lines × 2 locations) packages/component-hmr/src/lib/transform.ts:672— packages/component-hmr/src/lib/transform.ts:672 · packages/component-hmr/src/lib/transform.ts:699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2 locations) packages/multipart-parser/src/lib/future/multipart.ts:226— packages/multipart-parser/src/lib/future/multipart.ts:226 · packages/multipart-parser/src/lib/multipart.ts:390 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Low contrast colour pair in CSS-in-JS (2.5:1) packages/ui/src/demos/animation/default-animate.tsx:31— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS-in-JS (2.5:1) packages/ui/src/demos/animation/mixin-reclaim.tsx:37— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS-in-JS (3.8:1) packages/ui/src/demos/animation/mixin-presence-list.tsx:52— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS-in-JS (3.8:1) packages/ui/src/demos/animation/mixin-reclaim.tsx:77— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
HackComment docs/ui/app/actions/public/entry.ts:100— // HACK: `remix/component` currently intercepts reloads and same-document hash — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment docs/site/app/actions/public/entry.tsx:74— // HACK: `remix/component` currently intercepts reloads and same-document hash navigations. Stop — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
frame.createFrame::renderContent (cognitive 35) packages/component/src/runtime/frame.ts:411— frame.createFrame::renderContent has cognitive complexity 35 (threshold 15). Drivers by points: if/else 22 (33 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. This shape REPEATS in the file: one other method here (frame.createFrame::reload) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
frame.createFrame::reload (cognitive 20) packages/component/src/runtime/frame.ts:689— frame.createFrame::reload has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 1 (4 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (frame.createFrame::renderContent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
runner.createHmrSupervisor::handleChildMessage (cognitive 22) REDACTED:359— runner.createHmrSupervisor::handleChildMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (runner.createHmrSupervisor::flushPendingWatchEvents) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
runner.createHmrSupervisor::flushPendingWatchEvents (cognitive 18) REDACTED:574— runner.createHmrSupervisor::flushPendingWatchEvents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (runner.createHmrSupervisor::handleChildMessage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MethodTooLong: MultipartScanner.write packages/multipart-parser/src/lib/future/multipart.ts:136— MethodTooLong — write runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MultipartParser.write packages/multipart-parser/src/lib/multipart.ts:298— MethodTooLong — write runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TooManyMethods: Database packages/data-table/src/lib/database.ts:363— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Query packages/data-table/src/lib/query.ts:231— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Fake-async — async method never awaits packages/cli/src/lib/commands/version.ts:8— `runVersionCommand` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/node-hmr/src/runtime.ts:20— `createBrowserHmrChannel` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (39 lines × 2 locations) packages/assets/src/lib/source-maps.ts:60— packages/assets/src/lib/source-maps.ts:60 · packages/node-hmr/src/register.ts:275 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (39 lines × 2 locations) packages/multipart-parser/src/lib/future/multipart.ts:291— packages/multipart-parser/src/lib/future/multipart.ts:291 · packages/multipart-parser/src/lib/multipart.ts:453 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (38 lines × 2 locations) packages/assets/src/lib/scripts/compiler.ts:1106— packages/assets/src/lib/scripts/compiler.ts:1106 · packages/assets/src/lib/styles/compiler.ts:570 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (38 lines × 2 locations) packages/data-table-postgres/src/lib/sql-compiler.ts:97— packages/data-table-postgres/src/lib/sql-compiler.ts:97 · packages/data-table-sqlite/src/lib/sql-compiler.ts:99 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (31 lines × 2 locations) packages/assets/src/lib/scripts/transform.ts:349— packages/assets/src/lib/scripts/transform.ts:349 · packages/node-hmr/src/lib/hmr-analysis.ts:72 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (31 lines × 2 locations) packages/component/src/runtime/run.ts:71— packages/component/src/runtime/run.ts:71 · packages/spa/src/lib/spa.ts:164 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (30 lines × 2 locations) packages/assets/src/lib/asset-server.ts:714— packages/assets/src/lib/asset-server.ts:714 · packages/assets/src/lib/asset-server.ts:781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2 locations) packages/lazy-file/src/lib/lazy-file.ts:61— packages/lazy-file/src/lib/lazy-file.ts:61 · packages/lazy-file/src/lib/lazy-file.ts:232 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (26 lines × 2 locations) packages/assets/src/lib/scripts/emit.ts:52— packages/assets/src/lib/scripts/emit.ts:52 · packages/assets/src/lib/styles/emit.ts:51 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (26 lines × 2 locations) packages/component/src/server/stream.ts:1087— packages/component/src/server/stream.ts:1087 · packages/component/src/server/stream.ts:1162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2 locations) packages/assets/src/lib/scripts/transform.ts:873— packages/assets/src/lib/scripts/transform.ts:873 · packages/node-hmr/src/lib/hmr-analysis.ts:139 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (23 lines × 2 locations) packages/multipart-parser/src/lib/future/multipart.ts:167— packages/multipart-parser/src/lib/future/multipart.ts:167 · packages/multipart-parser/src/lib/multipart.ts:331 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Low contrast colour pair in CSS-in-JS (4.4:1) packages/ui/src/demos/animation/default-animate.tsx:56— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS-in-JS (2.8:1) packages/ui/src/demos/animation/mixin-presence-list.tsx:32— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS-in-JS (2.1:1) packages/ui/src/demos/animation/mixin-reclaim.tsx:54— A styled-components/emotion style declares a foreground/background colour pair below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement docs/ui/app/actions/public/ui.css:142— `.ui-preview-card-content h3 a:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung REDACTED:15— No accessibility enforcement found — your oxlint config does not list the `jsx-a11y` plugin (its a11y rules are off until it does) and there's no axe/pa11y/Lighthouse in tests or CI. Start by enabling that plugin to catch issues at author time. What was searched, so you can tell an absence from a miss: the 47 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.
compiler.createScriptCompiler (cyclomatic 112) packages/assets/src/lib/scripts/compiler.ts:148— compiler.createScriptCompiler has cyclomatic complexity 112 (threshold 15). Of this number, 36 points are the body's own statements and 76 belong to 23 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
asset-server.createAssetServer (cyclomatic 87) packages/assets/src/lib/asset-server.ts:413— asset-server.createAssetServer has cyclomatic complexity 87 (threshold 15). Of this number, 65 points are the body's own statements and 22 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
menu.MenuProvider (cyclomatic 80) packages/ui/src/menu.tsx:235— menu.MenuProvider has cyclomatic complexity 80 (threshold 15). Most of this is not in the body itself: 7 of the 80 points are its own statements and the rest belongs to 16 function items inside it that branch (activateItem, closeAll, highlight, …). 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.
form-context.control.<returned closure> (cyclomatic 61) packages/ui/src/form-context.ts:241— form-context.control.<returned closure> has cyclomatic complexity 61 (threshold 15). Of this number, 27 points are the body's own statements and 34 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
deep-equal.compare (cyclomatic 59) packages/assert/src/lib/deep-equal.ts:278— deep-equal.compare has cyclomatic complexity 59 (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.
compiler.createStyleCompiler (cyclomatic 57) packages/assets/src/lib/styles/compiler.ts:94— compiler.createStyleCompiler has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 14 of the 57 points are its own statements and the rest belongs to 13 function items inside it that branch (getOrCreateEmittedStyleFromGraph, getOrCreateTransformedStyle, resolveStyleGraph, …). 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.
reconcile.insert (cyclomatic 57) REDACTED:1162— reconcile.insert has cyclomatic complexity 57 (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.
runner.isChildMessage (cyclomatic 57) REDACTED:1261— runner.isChildMessage has cyclomatic complexity 57 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
module-store.createModuleStore (cyclomatic 47) packages/assets/src/lib/module-store.ts:94— module-store.createModuleStore has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 12 of the 47 points are its own statements and the rest belongs to 10 function items inside it that branch (updateWatchDirectoryRefCounts, updateWatchFileRefCounts, invalidateContent, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
form-control.fieldValidity.<returned closure> (cyclomatic 47) packages/ui/src/form-control.ts:155— form-control.fieldValidity.<returned closure> has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 6 of the 47 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 159, updateFeedback, getFeedbackProps, …). 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.
MultipartParser.write (cyclomatic 46) packages/multipart-parser/src/lib/multipart.ts:298— MultipartParser.write has cyclomatic complexity 46 (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.
publish.main (cyclomatic 44) scripts/publish.ts:399— publish.main has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MultipartScanner.write (cyclomatic 42) packages/multipart-parser/src/lib/future/multipart.ts:136— MultipartScanner.write has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compiler.createFileCompiler (cyclomatic 41) packages/assets/src/lib/files/compiler.ts:122— compiler.createFileCompiler has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 12 of the 41 points are its own statements and the rest belongs to 11 function items inside it that branch (applyTransforms, a function literal at line 272, 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.
config.normalizeFilesOptions (cyclomatic 40) packages/assets/src/lib/files/config.ts:183— config.normalizeFilesOptions 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.
changes.parsePackageChanges (cyclomatic 39) scripts/utils/changes.ts:188— changes.parsePackageChanges has cyclomatic complexity 39 (threshold 15). Of this number, 38 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.
navigation.startNavigationListenerImpl (cyclomatic 36) packages/component/src/runtime/navigation.ts:337— navigation.startNavigationListenerImpl has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 364, 420). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into 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-shell.startDocsShellBehavior (cyclomatic 35) docs/shared/ui/public/docs-shell.tsx:32— docs-shell.startDocsShellBehavior 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 items inside it that branch (syncMobileNavigation, setMobilePanel, setNavigationCollapsed, …). 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.
optimize-barrel-file-imports.getExportAnalysis (cyclomatic 35) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:414— optimize-barrel-file-imports.getExportAnalysis has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cjs-check.collectScopeBindings (cyclomatic 33) packages/assets/src/lib/scripts/cjs-check.ts:160— cjs-check.collectScopeBindings has cyclomatic complexity 33 (threshold 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, 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.
scheduler.createScheduler (cyclomatic 33) packages/component/src/runtime/scheduler.ts:61— scheduler.createScheduler has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (flush, ancestorIsScheduled, trackCascadingUpdate, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
props.patchHostProps (cyclomatic 33) REDACTED:57— props.patchHostProps 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.
file.createFileResponse (cyclomatic 33) packages/response/src/lib/file.ts:129— file.createFileResponse 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.
program.matchPart (cyclomatic 33) packages/route-pattern/src/lib/match/program.ts:252— program.matchPart 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.
toggle.toggleMixin.<returned closure> (cyclomatic 33) packages/ui/src/toggle.ts:110— toggle.toggleMixin.<returned closure> has cyclomatic complexity 33 (threshold 15). Of this number, 25 points are the body's own statements and 8 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.
cjs-check.walkForCommonJS (cyclomatic 32) packages/assets/src/lib/scripts/cjs-check.ts:49— cjs-check.walkForCommonJS has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolve.resolveModule (cyclomatic 31) packages/assets/src/lib/scripts/resolve.ts:135— resolve.resolveModule has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
link-mixin.link.<returned closure> (cyclomatic 31) packages/component/src/runtime/mixins/link-mixin.ts:32— link-mixin.link.<returned closure> has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 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.
stream.buildElementSegment (cyclomatic 31) packages/component/src/server/stream.ts:663— stream.buildElementSegment has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
anchor.anchor::updatePosition (cyclomatic 31) packages/ui/src/anchor.ts:746— anchor.anchor::updatePosition has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
select.SelectProvider (cyclomatic 30) packages/ui/src/select.tsx:95— select.SelectProvider has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 13 function items inside it that branch (settleSelectedOption, syncPopoverMinWidth, selectTypeaheadMatch, …). 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.
generate-remix.outputExportsChangeFiles (cyclomatic 30) scripts/generate-remix.ts:804— generate-remix.outputExportsChangeFiles has cyclomatic complexity 30 (threshold 15). 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, 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.
navigation.updateUrl (cyclomatic 29) packages/component/src/runtime/navigation.ts:213— navigation.updateUrl has cyclomatic complexity 29 (threshold 15). Of this number, 26 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.
runner.runMigrationsUnlocked (cyclomatic 28) packages/data-table/src/lib/migrations/runner.ts:160— runner.runMigrationsUnlocked 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.
program.compilePart (cyclomatic 28) packages/route-pattern/src/lib/match/program.ts:48— program.compilePart 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.
accordion.AccordionProvider (cyclomatic 28) packages/ui/src/accordion.tsx:129— accordion.AccordionProvider has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 3 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (toggleItem, focusItem, getSingleValue, …). 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.
completion.completeTest (cyclomatic 27) packages/cli/src/lib/completion.ts:294— completion.completeTest has cyclomatic complexity 27 (threshold 15). Of this number, 24 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.
diff-dom.diffNode (cyclomatic 27) packages/component/src/runtime/diff-dom.ts:55— diff-dom.diffNode 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.
prefetch.createAssetPrefetch (cyclomatic 27) packages/component/src/runtime/prefetch.ts:413— prefetch.createAssetPrefetch has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
prefetch.startPrefetching (cyclomatic 26) packages/component/src/runtime/prefetch.ts:47— prefetch.startPrefetching has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 140, trigger, leave, …). 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.
href.hrefPart (cyclomatic 25) packages/route-pattern/src/lib/href.ts:156— href.hrefPart 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.
generate-remix.updateRemixPackage (cyclomatic 25) scripts/generate-remix.ts:263— generate-remix.updateRemixPackage 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.
html-parser.parseTag (cyclomatic 24) docs/shared/prerender/html-parser.ts:148— html-parser.parseTag has cyclomatic complexity 24 (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.createSetupSource (cyclomatic 24) packages/component-hmr/src/lib/transform.ts:841— transform.createSetupSource 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.
fetch-proxy.createFetchProxy.<returned closure> (cyclomatic 24) packages/fetch-proxy/src/lib/fetch-proxy.ts:99— fetch-proxy.createFetchProxy.<returned closure> 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.
router.createRouter (cyclomatic 24) packages/fetch-router/src/lib/router.ts:362— router.createRouter has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 7 function items inside it that branch (dispatchMatches, mapController, a function literal at line 419, …). 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.
runtime.installNodeHmrRuntime (cyclomatic 24) packages/node-hmr/src/lib/runtime.ts:247— runtime.installNodeHmrRuntime has cyclomatic complexity 24 (threshold 15). Of this number, 17 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.
Trie.search (cyclomatic 24) packages/route-pattern/src/lib/match/trie.ts:125— Trie.search 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.
form-constraints.getConstraints (cyclomatic 24) packages/ui/src/form-constraints.ts:70— form-constraints.getConstraints 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.
preview.publishPreview (cyclomatic 24) scripts/utils/preview.ts:366— preview.publishPreview has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
frame.createFrame::renderContent (cyclomatic 23) packages/component/src/runtime/frame.ts:411— frame.createFrame::renderContent has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
prefetch.startViewportPrefetching (cyclomatic 23) packages/component/src/runtime/prefetch.ts:170— prefetch.startViewportPrefetching has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 180, a function literal at line 211, update, …). 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.
html-parser.parse (cyclomatic 21) docs/shared/prerender/html-parser.ts:205— html-parser.parse has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
registry.buildRegistry (cyclomatic 21) docs/site/app/data/registry.ts:60— registry.buildRegistry has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cjs-check.isReferenceIdentifier (cyclomatic 21) packages/assets/src/lib/scripts/cjs-check.ts:382— cjs-check.isReferenceIdentifier has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
cors.cors.<returned closure> (cyclomatic 21) REDACTED:138— cors.cors.<returned closure> 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.
CacheControl.from (cyclomatic 21) packages/headers/src/lib/cache-control.ts:315— CacheControl.from has cyclomatic complexity 21 (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.
combobox.ComboboxProvider::closePopover (cyclomatic 21) packages/ui/src/combobox.tsx:347— combobox.ComboboxProvider::closePopover has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
form-control.validateInput (cyclomatic 21) packages/ui/src/form-control.ts:328— form-control.validateInput 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.
tabs.TabsProvider (cyclomatic 21) packages/ui/src/tabs.ts:90— tabs.TabsProvider has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (activateTabInDirection, activateTab, registerTab, …). 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.
optimize-barrel-file-imports.createBarrelFileImportOptimizer.optimizeBarrelFileImports (cyclomatic 20) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:77— optimize-barrel-file-imports.createBarrelFileImportOptimizer.optimizeBarrelFileImports has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 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.
help.getCommandHelpText (cyclomatic 20) packages/cli/src/lib/commands/help.ts:84— help.getCommandHelpText has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
navigation.resyncWebKitScrollAfterNavigation (cyclomatic 20) packages/component/src/runtime/navigation.ts:62— navigation.resyncWebKitScrollAfterNavigation has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 112, undoRestoration, a function literal at line 122, …). 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.
stream.buildSegment (cyclomatic 20) packages/component/src/server/stream.ts:543— stream.buildSegment 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.
SetCookie.from (cyclomatic 20) packages/headers/src/lib/set-cookie.ts:191— SetCookie.from 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.
menu.listMixin.<returned closure> (cyclomatic 20) packages/ui/src/menu.tsx:954— menu.listMixin.<returned closure> has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 984, 968). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
menu.submenuTriggerMixin.<returned closure> (cyclomatic 20) packages/ui/src/menu.tsx:1163— menu.submenuTriggerMixin.<returned closure> has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
emit.rewriteImports (cyclomatic 19) packages/assets/src/lib/scripts/emit.ts:86— emit.rewriteImports 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.
module-store.createModuleStore (cyclomatic 19) packages/node-hmr/src/lib/module-store.ts:29— module-store.createModuleStore has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (findPropagationFromImporters, visit, findPropagation, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
compress.compressStream (cyclomatic 19) packages/response/src/lib/compress.ts:260— compress.compressStream has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
specificity.comparePathname (cyclomatic 19) packages/route-pattern/src/lib/specificity.ts:151— specificity.comparePathname 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.
static.staticFiles.<returned closure> (cyclomatic 19) packages/static-middleware/src/lib/static.ts:106— static.staticFiles.<returned closure> 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.
changes.parseAllChangeFiles (cyclomatic 19) scripts/utils/changes.ts:427— changes.parseAllChangeFiles 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.
table-of-contents.startTableOfContentsBehavior (cyclomatic 18) docs/shared/ui/public/table-of-contents.tsx:24— table-of-contents.startTableOfContentsBehavior has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 51, scheduleUpdate, a function literal at line 26, …). 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.
api-nav.ApiNav::slide (cyclomatic 18) docs/site/app/actions/public/api-nav.tsx:78— api-nav.ApiNav::slide has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cache.readRecord (cyclomatic 18) packages/assets/src/lib/files/cache.ts:187— cache.readRecord has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
remix-config.parseTestConfig (cyclomatic 18) REDACTED:403— remix-config.parseTestConfig 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.
transform.shouldRewriteIdentifier (cyclomatic 18) packages/component-hmr/src/lib/transform.ts:1011— transform.shouldRewriteIdentifier 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.
props.patchHostProp (cyclomatic 18) REDACTED:118— props.patchHostProp 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.
form.parseSafe (cyclomatic 18) packages/data-schema/src/lib/form.ts:376— form.parseSafe has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
query.cloneQueryPlan (cyclomatic 18) packages/data-table/src/lib/query.ts:770— query.cloneQueryPlan has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
runner.createHmrSupervisor::handleChildMessage (cyclomatic 18) REDACTED:359— runner.createHmrSupervisor::handleChildMessage 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.
directory-listing.generateDirectoryListing (cyclomatic 18) packages/static-middleware/src/lib/directory-listing.ts:14— directory-listing.generateDirectoryListing has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
preview.buildPreview (cyclomatic 18) scripts/utils/preview.ts:179— preview.buildPreview has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
prompt-button.PromptButton.<returned closure> (cyclomatic 18) template/app/actions/public/prompt-button.tsx:12— prompt-button.PromptButton.<returned closure> has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
crawl.crawl (cyclomatic 17) docs/shared/prerender/crawl.ts:19— crawl.crawl has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (fetchOne, a function literal at line 57). 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.
validate-guides.exportsHandler (cyclomatic 17) docs/site/scripts/validate-guides.ts:126— validate-guides.exportsHandler 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.
parse-args.parseArgs (cyclomatic 17) packages/cli/src/lib/parse-args.ts:32— parse-args.parseArgs 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.
diff-dom.shouldPreserveLiveAttribute (cyclomatic 17) packages/component/src/runtime/diff-dom.ts:173— diff-dom.shouldPreserveLiveAttribute 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.
reconcile.remove (cyclomatic 17) REDACTED:1536— reconcile.remove has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
schema.object.objectSchema (cyclomatic 17) packages/data-schema/src/lib/schema.ts:893— schema.object.objectSchema 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.
relations.loadHasManyThroughValues (cyclomatic 17) packages/data-table/src/lib/database/relations.ts:110— relations.loadHasManyThroughValues 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.
cli.runRemixDb (cyclomatic 17) packages/data-table/src/cli.ts:88— cli.runRemixDb 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.
CacheControl.toString (cyclomatic 17) packages/headers/src/lib/cache-control.ts:254— CacheControl.toString 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.
Range.canSatisfy (cyclomatic 17) packages/headers/src/lib/range.ts:89— Range.canSatisfy 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.
Range.from (cyclomatic 17) packages/headers/src/lib/range.ts:216— Range.from 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.
specificity.compareHostname (cyclomatic 17) packages/route-pattern/src/lib/specificity.ts:108— specificity.compareHostname 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.
anchor.calculatePosition (cyclomatic 17) packages/ui/src/anchor.ts:192— anchor.calculatePosition 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.
form-control.getNativeIssue (cyclomatic 17) packages/ui/src/form-control.ts:375— form-control.getNativeIssue 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.
assert.checkError (cyclomatic 16) packages/assert/src/lib/assert.ts:777— assert.checkError 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.
config.normalizeAssetTransformInvocation (cyclomatic 16) packages/assets/src/lib/files/config.ts:405— config.normalizeAssetTransformInvocation 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.
completion.completeRoutes (cyclomatic 16) packages/cli/src/lib/completion.ts:478— completion.completeRoutes 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.
transform.getScopeBindings (cyclomatic 16) packages/component-hmr/src/lib/transform.ts:1119— transform.getScopeBindings 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.
import-map-manager.installImportMap (cyclomatic 16) packages/component/src/runtime/import-map-manager.ts:152— import-map-manager.installImportMap 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.
reconcile.diffChildren (cyclomatic 16) REDACTED:1629— reconcile.diffChildren has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: reconcile.diffVNodes (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
prefetch.createDefaultPrefetch (cyclomatic 16) packages/component/src/runtime/prefetch.ts:315— prefetch.createDefaultPrefetch has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (discover, prefetchAsset, discoverAssets). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
stream.collectAuthoredImportMap (cyclomatic 16) packages/component/src/server/stream.ts:793— stream.collectAuthoredImportMap 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.
stream.hoistClientEntryResourcesFromFrameHead (cyclomatic 16) packages/component/src/server/stream.ts:1481— stream.hoistClientEntryResourcesFromFrameHead 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.
cop.matchesBypassPattern (cyclomatic 16) packages/cop-middleware/src/lib/cop.ts:312— cop.matchesBypassPattern 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.
query.assertWriteState (cyclomatic 16) packages/data-table/src/lib/query.ts:850— query.assertWriteState has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
parse.parsePart (cyclomatic 16) packages/route-pattern/src/lib/route-pattern/parse.ts:42— parse.parsePart has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TarParser.#parseHeader (cyclomatic 16) REDACTED:609— TarParser.#parseHeader has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: releases pending hydration metadata when its frame is disposed packages/component/src/test/frame.test.ts:1028— This test starts work it did not wait for (`frame`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
compiler.createScriptCompiler (cognitive 168) packages/assets/src/lib/scripts/compiler.ts:148— compiler.createScriptCompiler has cognitive complexity 168 (threshold 15). Drivers by points: if/else 69 (105 pts), loops 20 (41 pts), boolean chains 15, ternaries 5 (6 pts), error handling 1 (nesting depth added 58). Of this number, 71 points are the body's own statements and 97 belong to 23 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.
reconcile.insert (cognitive 123) REDACTED:1162— reconcile.insert has cognitive complexity 123 (threshold 15). Drivers by points: if/else 33 (91 pts), loops 3 (13 pts), boolean chains 10, ternaries 3 (9 pts) (nesting depth added 74). 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.
asset-server.createAssetServer (cognitive 118) packages/assets/src/lib/asset-server.ts:413— asset-server.createAssetServer has cognitive complexity 118 (threshold 15). Drivers by points: if/else 53 (81 pts), ternaries 12 (18 pts), boolean chains 9, loops 4 (5 pts), error handling 4, match/switch 1 (nesting depth added 35). Of this number, 91 points are the body's own statements and 27 belong to 12 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.
MultipartParser.write (cognitive 115) packages/multipart-parser/src/lib/multipart.ts:298— MultipartParser.write has cognitive complexity 115 (threshold 15). Drivers by points: if/else 38 (98 pts), boolean chains 8, ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 66). 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.
MultipartScanner.write (cognitive 99) packages/multipart-parser/src/lib/future/multipart.ts:136— MultipartScanner.write has cognitive complexity 99 (threshold 15). Drivers by points: if/else 34 (82 pts), boolean chains 8, ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 54). 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.
menu.MenuProvider (cognitive 77) packages/ui/src/menu.tsx:235— menu.MenuProvider has cognitive complexity 77 (threshold 15). Drivers by points: if/else 53 (57 pts), boolean chains 13, ternaries 3 (4 pts), loops 2, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 77 points are its own statements and the rest belongs to 16 function items inside it that branch (closeAll, activateItem, openMenu, …). 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.
module-store.createModuleStore (cognitive 74) packages/assets/src/lib/module-store.ts:94— module-store.createModuleStore has cognitive complexity 74 (threshold 15). Drivers by points: if/else 32 (55 pts), loops 13 (15 pts), boolean chains 4 (nesting depth added 25). Of this number, 21 points are the body's own statements and 53 belong to 10 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.
compiler.createStyleCompiler (cognitive 71) packages/assets/src/lib/styles/compiler.ts:94— compiler.createStyleCompiler has cognitive complexity 71 (threshold 15). Drivers by points: if/else 33 (44 pts), loops 12 (18 pts), ternaries 4 (5 pts), boolean chains 4 (nesting depth added 18). Of this number, 23 points are the body's own statements and 48 belong to 13 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
combobox.ComboboxProvider (cognitive 69) packages/ui/src/combobox.tsx:152— combobox.ComboboxProvider has cognitive complexity 69 (threshold 15). Drivers by points: if/else 43 (49 pts), boolean chains 17, ternaries 3 (nesting depth added 6). Most of this is not in the body itself: 1 of the 69 points is its own statement and the rest belongs to 19 function items inside it that branch (closePopover, resolveOpenOption, setInputText, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
publish.main (cognitive 69) scripts/publish.ts:399— publish.main has cognitive complexity 69 (threshold 15). Drivers by points: if/else 23 (33 pts), loops 10 (17 pts), ternaries 6 (11 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 24). 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.
optimize-barrel-file-imports.getExportAnalysis (cognitive 68) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:414— optimize-barrel-file-imports.getExportAnalysis has cognitive complexity 68 (threshold 15). Drivers by points: if/else 19 (47 pts), loops 5 (14 pts), boolean chains 7 (nesting depth added 37). 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.
form-context.control.<returned closure> (cognitive 65) packages/ui/src/form-context.ts:241— form-context.control.<returned closure> has cognitive complexity 65 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 20, ternaries 9 (11 pts) (nesting depth added 10). Of this number, 25 points are the body's own statements and 40 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
documented-api.processApiComment (cognitive 63) docs/site/scripts/generate/documented-api.ts:767— documented-api.processApiComment has cognitive complexity 63 (threshold 15). Drivers by points: ternaries 6 (39 pts), if/else 10 (23 pts), boolean chains 1 (nesting depth added 46). None of this is in the body itself: all 63 points belong to one function literal inside it that branches (line 768). 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.
program.matchPart (cognitive 63) packages/route-pattern/src/lib/match/program.ts:252— program.matchPart has cognitive complexity 63 (threshold 15). Drivers by points: if/else 15 (42 pts), loops 5 (10 pts), boolean chains 6, ternaries 2 (5 pts) (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.
transform.createSetupSource (cognitive 59) packages/component-hmr/src/lib/transform.ts:841— transform.createSetupSource has cognitive complexity 59 (threshold 15). Drivers by points: if/else 11 (37 pts), loops 5 (10 pts), ternaries 2 (9 pts), boolean chains 3 (nesting depth added 38). 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.
deep-equal.compare (cognitive 58) packages/assert/src/lib/deep-equal.ts:278— deep-equal.compare has cognitive complexity 58 (threshold 15). Drivers by points: if/else 24 (29 pts), boolean chains 27, ternaries 1 (2 pts) (nesting depth added 6). 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.
runner.runMigrationsUnlocked (cognitive 58) packages/data-table/src/lib/migrations/runner.ts:160— runner.runMigrationsUnlocked has cognitive complexity 58 (threshold 15). Drivers by points: if/else 21 (43 pts), error handling 2 (6 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 29). 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.
changes.parsePackageChanges (cognitive 58) scripts/utils/changes.ts:188— changes.parsePackageChanges has cognitive complexity 58 (threshold 15). Drivers by points: if/else 25 (46 pts), boolean chains 11, loops 1 (nesting depth added 21). Of this number, 57 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.
form-control.fieldValidity.<returned closure> (cognitive 55) packages/ui/src/form-control.ts:155— form-control.fieldValidity.<returned closure> has cognitive complexity 55 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 16, ternaries 5 (8 pts), loops 1 (4 pts) (nesting depth added 14). Most of this is not in the body itself: 5 of the 55 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 159, updateFeedback, getFeedbackProps, …). 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.
optimize-barrel-file-imports.createBarrelFileImportOptimizer.optimizeBarrelFileImports (cognitive 53) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:77— optimize-barrel-file-imports.createBarrelFileImportOptimizer.optimizeBarrelFileImports has cognitive complexity 53 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 8 (21 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 34). Of this number, 48 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resolve.resolveModule (cognitive 52) packages/assets/src/lib/scripts/resolve.ts:135— resolve.resolveModule has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (40 pts), loops 5 (6 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 23). 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-dom.diffNode (cognitive 52) packages/component/src/runtime/diff-dom.ts:55— diff-dom.diffNode has cognitive complexity 52 (threshold 15). Drivers by points: if/else 19 (46 pts), boolean chains 6 (nesting depth added 27). 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.
completion.completeTest (cognitive 51) packages/cli/src/lib/completion.ts:294— completion.completeTest has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 4 (7 pts), boolean chains 6, loops 2 (5 pts) (nesting depth added 25). Of this number, 48 points are the body's own statements and 3 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.
props.patchHostProps (cognitive 51) REDACTED:57— props.patchHostProps has cognitive complexity 51 (threshold 15). Drivers by points: if/else 22 (40 pts), boolean chains 8, loops 2, ternaries 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.
program.compilePart (cognitive 51) packages/route-pattern/src/lib/match/program.ts:48— program.compilePart has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (35 pts), loops 5 (7 pts), boolean chains 6, ternaries 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.
compiler.createFileCompiler (cognitive 49) packages/assets/src/lib/files/compiler.ts:122— compiler.createFileCompiler has cognitive complexity 49 (threshold 15). Drivers by points: if/else 29 (36 pts), boolean chains 5, error handling 2 (4 pts), loops 2, ternaries 2 (nesting depth added 9). Most of this is not in the body itself: 14 of the 49 points are its own statements and the rest belongs to 11 function items inside it that branch (applyTransforms, a function literal at line 272, 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.
SetCookie.from (cognitive 49) packages/headers/src/lib/set-cookie.ts:191— SetCookie.from has cognitive complexity 49 (threshold 15). Drivers by points: if/else 9 (39 pts), match/switch 1 (5 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 37). 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.
file.createFileResponse (cognitive 47) packages/response/src/lib/file.ts:129— file.createFileResponse has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (37 pts), boolean chains 8, ternaries 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.normalizeFilesOptions (cognitive 46) packages/assets/src/lib/files/config.ts:183— config.normalizeFilesOptions has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (35 pts), boolean chains 8, loops 3 (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.
navigation.startNavigationListenerImpl (cognitive 44) packages/component/src/runtime/navigation.ts:337— navigation.startNavigationListenerImpl has cognitive complexity 44 (threshold 15). Drivers by points: if/else 24 (33 pts), boolean chains 7, ternaries 4 (nesting depth added 9). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 364, 420). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Range.from (cognitive 44) packages/headers/src/lib/range.ts:216— Range.from has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (37 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Trie.search (cognitive 43) packages/route-pattern/src/lib/match/trie.ts:125— Trie.search has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (32 pts), loops 6 (10 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
html-parser.parse (cognitive 41) docs/shared/prerender/html-parser.ts:205— html-parser.parse has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (38 pts), loops 2, boolean chains 1 (nesting depth added 21). Of this number, 36 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.
href.hrefPart (cognitive 41) packages/route-pattern/src/lib/href.ts:156— href.hrefPart has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (33 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
generate-remix.outputExportsChangeFiles (cognitive 40) scripts/generate-remix.ts:804— generate-remix.outputExportsChangeFiles has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 5 (9 pts), error handling 2 (4 pts), boolean chains 3, ternaries 2 (nesting depth added 17). Of this number, 39 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.
anchor.anchor::updatePosition (cognitive 39) packages/ui/src/anchor.ts:746— anchor.anchor::updatePosition has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (30 pts), boolean chains 7, ternaries 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.
cjs-check.collectScopeBindings (cognitive 38) packages/assets/src/lib/scripts/cjs-check.ts:160— cjs-check.collectScopeBindings has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 4 (8 pts), boolean chains 2, ternaries 1 (2 pts), match/switch 1 (nesting depth added 19). Of this number, 35 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
ContentRange.from (cognitive 38) packages/headers/src/lib/content-range.ts:106— ContentRange.from has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (26 pts), ternaries 3 (12 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.
generate-remix.updateRemixPackage (cognitive 38) scripts/generate-remix.ts:263— generate-remix.updateRemixPackage has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (25 pts), loops 8 (10 pts), boolean chains 3 (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.
docs-shell.startDocsShellBehavior (cognitive 37) docs/shared/ui/public/docs-shell.tsx:32— docs-shell.startDocsShellBehavior has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17, boolean chains 10, ternaries 5 (6 pts), loops 3 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 11 function items inside it that branch (syncMobileNavigation, setMobilePanel, setNavigationCollapsed, …). 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.
html-parser.parseTag (cognitive 36) docs/shared/prerender/html-parser.ts:148— html-parser.parseTag has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (15 pts), if/else 7 (13 pts), boolean chains 8 (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.
registry.buildRegistry (cognitive 36) docs/site/app/data/registry.ts:60— registry.buildRegistry has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 8 (12 pts), ternaries 2 (6 pts), boolean chains 3 (nesting depth added 17). Of this number, 30 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate-guides.exportsHandler (cognitive 36) docs/site/scripts/validate-guides.ts:126— validate-guides.exportsHandler has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 3 (8 pts), boolean chains 4 (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.
link-mixin.link.<returned closure> (cognitive 36) packages/component/src/runtime/mixins/link-mixin.ts:32— link-mixin.link.<returned closure> has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 7, ternaries 2 (6 pts), loops 1 (2 pts) (nesting depth added 9). Of this number, 19 points are the body's own statements and 17 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.
stream.buildElementSegment (cognitive 36) packages/component/src/server/stream.ts:663— stream.buildElementSegment has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 13, ternaries 4 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
toggle.toggleMixin.<returned closure> (cognitive 36) packages/ui/src/toggle.ts:110— toggle.toggleMixin.<returned closure> has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 19 (22 pts), boolean chains 8, if/else 5 (6 pts) (nesting depth added 4). Of this number, 27 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
transform.findMatches (cognitive 35) packages/component-hmr/src/lib/transform.ts:497— transform.findMatches has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 5 (13 pts), loops 2 (3 pts), boolean chains 1 (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.
transform.getScopeBindings (cognitive 35) packages/component-hmr/src/lib/transform.ts:1119— transform.getScopeBindings has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 3 (8 pts), boolean chains 3 (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.
cjs-check.walkForCommonJS (cognitive 34) packages/assets/src/lib/scripts/cjs-check.ts:49— cjs-check.walkForCommonJS has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 4 (8 pts), boolean chains 5, loops 2 (3 pts), match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
emit.rewriteImports (cognitive 34) packages/assets/src/lib/scripts/emit.ts:86— emit.rewriteImports has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 5 (8 pts), ternaries 4 (6 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reconcile.remove (cognitive 33) REDACTED:1536— reconcile.remove has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (31 pts), loops 1 (2 pts) (nesting depth added 16). 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.
router.createRouter (cognitive 33) packages/fetch-router/src/lib/router.ts:362— router.createRouter has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 5, loops 3, ternaries 2 (nesting depth added 9). None of this is in the body itself: all 33 points belong to 7 function items inside it that branch (dispatchMatches, mapController, a function literal at line 419, …). 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.
href.hrefSearch (cognitive 33) packages/route-pattern/src/lib/href.ts:234— href.hrefSearch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4 (10 pts), boolean chains 2, ternaries 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.
punycode.decode (cognitive 33) packages/route-pattern/src/lib/match/punycode.ts:107— punycode.decode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (20 pts), ternaries 3 (9 pts), loops 3 (4 pts) (nesting depth added 19). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
form-constraints.getConstraints (cognitive 33) packages/ui/src/form-constraints.ts:70— form-constraints.getConstraints has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 8, ternaries 2 (5 pts), match/switch 1 (2 pts), loops 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.
changes.parseAllChangeFiles (cognitive 33) scripts/utils/changes.ts:427— changes.parseAllChangeFiles has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 6 (7 pts), boolean chains 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.
navigation.updateUrl (cognitive 32) packages/component/src/runtime/navigation.ts:213— navigation.updateUrl has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 10, ternaries 4 (5 pts), error handling 1 (nesting depth added 2). Of this number, 27 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
stream.buildSegment (cognitive 32) packages/component/src/server/stream.ts:543— stream.buildSegment has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.object.objectSchema (cognitive 32) packages/data-schema/src/lib/schema.ts:893— schema.object.objectSchema has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 3, loops 2 (3 pts) (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.
Accept.from (cognitive 32) packages/headers/src/lib/accept.ts:199— Accept.from has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (13 pts) (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.
AcceptEncoding.from (cognitive 32) packages/headers/src/lib/accept-encoding.ts:195— AcceptEncoding.from has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (13 pts) (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.
AcceptLanguage.from (cognitive 32) packages/headers/src/lib/accept-language.ts:201— AcceptLanguage.from has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (13 pts) (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.
parse-args.parseArgs (cognitive 31) packages/cli/src/lib/parse-args.ts:32— parse-args.parseArgs has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (23 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cors.cors.<returned closure> (cognitive 30) REDACTED:138— cors.cors.<returned closure> has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form.parseSafe (cognitive 30) packages/data-schema/src/lib/form.ts:376— form.parseSafe has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetch-proxy.createFetchProxy.<returned closure> (cognitive 30) packages/fetch-proxy/src/lib/fetch-proxy.ts:99— fetch-proxy.createFetchProxy.<returned closure> has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parse.parsePart (cognitive 30) packages/route-pattern/src/lib/route-pattern/parse.ts:42— parse.parsePart has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 1, ternaries 1 (nesting depth added 14). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, 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.
assert.checkError (cognitive 29) packages/assert/src/lib/assert.ts:777— assert.checkError has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
github.createRelease (cognitive 29) scripts/utils/github.ts:177— github.createRelease has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 3 (6 pts), ternaries 2 (6 pts), loops 2 (3 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.
prefetch.startViewportPrefetching (cognitive 28) packages/component/src/runtime/prefetch.ts:170— prefetch.startViewportPrefetching has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 5 (7 pts), boolean chains 5 (nesting depth added 6). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 180, a function literal at line 211, update, …). 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.
prefetch.createAssetPrefetch (cognitive 28) packages/component/src/runtime/prefetch.ts:413— prefetch.createAssetPrefetch has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, ternaries 2, error handling 1, 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.
program.compareSolutions (cognitive 28) packages/route-pattern/src/lib/match/program.ts:471— program.compareSolutions has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (10 pts), boolean chains 2 (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.
diff-dom.matchKeyedSiblingUnits (cognitive 27) packages/component/src/runtime/diff-dom.ts:312— diff-dom.matchKeyedSiblingUnits has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 3 (5 pts), boolean chains 3 (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.
fs.createFsFileStorage.list (cognitive 27) packages/file-storage/src/lib/backends/fs.ts:162— fs.createFsFileStorage.list has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 2 (3 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.
param-values.parseParams (cognitive 27) packages/headers/src/lib/param-values.ts:1— param-values.parseParams has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 2 (5 pts), boolean chains 1, ternaries 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.
request-listener.sendResponse (cognitive 27) packages/node-fetch-server/src/lib/request-listener.ts:712— request-listener.sendResponse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compress.compressStream (cognitive 27) packages/response/src/lib/compress.ts:260— compress.compressStream has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 4, error handling 1, loops 1 (nesting depth added 8). Of this number, 14 points are the body's own statements and 13 belong to 5 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.
static.staticFiles.<returned closure> (cognitive 27) packages/static-middleware/src/lib/static.ts:106— static.staticFiles.<returned closure> has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), error handling 3 (5 pts), boolean chains 3, 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.
select.SelectProvider (cognitive 27) packages/ui/src/select.tsx:95— select.SelectProvider has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 5, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 13 function items inside it that branch (settleSelectedOption, selectTypeaheadMatch, open, …). 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.
api-nav.ApiNav::slide (cognitive 26) docs/site/app/actions/public/api-nav.tsx:78— api-nav.ApiNav::slide has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 5 (8 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
frame.createSubFrames (cognitive 26) packages/component/src/runtime/frame.ts:1733— frame.createSubFrames has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
write-lifecycle.applyAfterReadHooksToLoadedRows (cognitive 26) packages/data-table/src/lib/database/write-lifecycle.ts:133— write-lifecycle.applyAfterReadHooksToLoadedRows has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 2 (5 pts), boolean chains 2 (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.
ContentSecurityPolicy.constructor (cognitive 26) packages/headers/src/lib/content-security-policy.ts:64— ContentSecurityPolicy.constructor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (7 pts), loops 3 (6 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.
Cookie.from (cognitive 26) packages/headers/src/lib/cookie.ts:177— Cookie.from has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (9 pts), ternaries 1 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vary.from (cognitive 26) packages/headers/src/lib/vary.ts:118— Vary.from has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 3 (9 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runner.isChildMessage (cognitive 26) REDACTED:1261— runner.isChildMessage has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, if/else 12. 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.
specificity.comparePathname (cognitive 26) packages/route-pattern/src/lib/specificity.ts:151— specificity.comparePathname has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, 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.
scheduler.createScheduler::flush (cognitive 25) packages/component/src/runtime/scheduler.ts:138— scheduler.createScheduler::flush has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 1 (4 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
diff-dom.diffElementAttributes (cognitive 25) packages/component/src/runtime/diff-dom.ts:135— diff-dom.diffElementAttributes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 3 (7 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mix.composeMixedProps (cognitive 25) packages/component/src/runtime/core/mix.ts:26— mix.composeMixedProps has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (6 pts), ternaries 2 (5 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.
reconcile.matchKeyedChildren (cognitive 25) REDACTED:1821— reconcile.matchKeyedChildren has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (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.
form-control.validateInput (cognitive 25) packages/ui/src/form-control.ts:328— form-control.validateInput has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 5 (6 pts), loops 3 (4 pts), boolean chains 3, 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.
preview.buildPreview (cognitive 25) scripts/utils/preview.ts:179— preview.buildPreview has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (6 pts), ternaries 2 (nesting depth added 7). Of this number, 23 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
crawl.crawl (cognitive 24) docs/shared/prerender/crawl.ts:19— crawl.crawl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (nesting depth added 7). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (fetchOne, a function literal at line 57). 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.visitBindingPattern (cognitive 24) packages/component-hmr/src/lib/transform.ts:971— transform.visitBindingPattern has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (4 pts), boolean chains 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.
frame.findHydrationMarkers::visit (cognitive 24) packages/component/src/runtime/frame.ts:2179— frame.findHydrationMarkers::visit has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 1, loops 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.
reconcile.diffChildren (cognitive 24) REDACTED:1629— reconcile.diffChildren has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (9 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
specificity.compareHostname (cognitive 24) packages/route-pattern/src/lib/specificity.ts:108— specificity.compareHostname has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (6 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
directory-listing.generateDirectoryListing (cognitive 24) packages/static-middleware/src/lib/directory-listing.ts:14— directory-listing.generateDirectoryListing has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 5, if/else 4 (5 pts), error handling 2 (4 pts), loops 2 (nesting depth added 7). Of this number, 20 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
accordion.AccordionProvider (cognitive 24) packages/ui/src/accordion.tsx:129— accordion.AccordionProvider has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (15 pts), ternaries 4 (5 pts), boolean chains 3, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (toggleItem, getSingleValue, getMultipleValue, …). 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.
code-blocks.addLineNumbers (cognitive 23) docs/shared/markdown/code-blocks.ts:172— code-blocks.addLineNumbers has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
import-map-manager.installImportMap (cognitive 23) packages/component/src/runtime/import-map-manager.ts:152— import-map-manager.installImportMap has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, loops 2, 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.
props.patchHostProp (cognitive 23) REDACTED:118— props.patchHostProp has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
relations.loadHasManyThroughValues (cognitive 23) packages/data-table/src/lib/database/relations.ts:110— relations.loadHasManyThroughValues has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 5 (7 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.
cli.runRemixDb (cognitive 23) packages/data-table/src/cli.ts:88— cli.runRemixDb has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (6 pts), ternaries 2 (4 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.
form-data.parseFormData (cognitive 23) packages/form-data-parser/src/lib/form-data.ts:265— form-data.parseFormData has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runtime.installNodeHmrRuntime (cognitive 23) packages/node-hmr/src/lib/runtime.ts:247— runtime.installNodeHmrRuntime has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17, loops 3, ternaries 2, error handling 1. Of this number, 16 points are the body's own statements and 7 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.
form-control.getNativeIssue (cognitive 23) packages/ui/src/form-control.ts:375— form-control.getNativeIssue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 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.
utils.rewriteExtensionsToJs (cognitive 22) docs/shared/prerender/utils.ts:47— utils.rewriteExtensionsToJs has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 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.
form-data.parseFormData (cognitive 22) packages/form-data-parser/src/lib/future/form-data.ts:308— form-data.parseFormData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
preview.publishPreview (cognitive 22) scripts/utils/preview.ts:366— preview.publishPreview has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, boolean chains 8, loops 2, ternaries 1. Of this number, 20 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
table-of-contents.startTableOfContentsBehavior (cognitive 21) docs/shared/ui/public/table-of-contents.tsx:24— table-of-contents.startTableOfContentsBehavior has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 3, loops 2 (nesting depth added 2). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 51, setCurrent, scheduleUpdate, …). 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.
demos.extractDemoMetadata (cognitive 21) docs/site/app/data/demos.tsx:145— demos.extractDemoMetadata has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
access.createPackageRootPaths (cognitive 21) packages/assets/src/lib/access.ts:181— access.createPackageRootPaths has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 5 (8 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform.collectBindingNames (cognitive 21) packages/component-hmr/src/lib/transform.ts:1164— transform.collectBindingNames has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nonce.getResponseNonce (cognitive 21) packages/component/src/runtime/nonce.ts:102— nonce.getResponseNonce has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prefetch.createDefaultPrefetch (cognitive 21) packages/component/src/runtime/prefetch.ts:315— prefetch.createDefaultPrefetch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, error handling 2 (3 pts), loops 2 (nesting depth added 5). None of this is in the body itself: all 21 points belong to 3 function items inside it that branch (discover, discoverAssets, prefetchAsset). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Range.canSatisfy (cognitive 21) packages/headers/src/lib/range.ts:89— Range.canSatisfy has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 5, loops 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.
parse.validateTokenGrammar (cognitive 21) packages/route-pattern/src/lib/route-pattern/parse.ts:147— parse.validateTokenGrammar has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form-control.getControlValue (cognitive 21) packages/ui/src/form-control.ts:399— form-control.getControlValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 3 (7 pts), boolean chains 2 (nesting depth added 10). Of this number, 20 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.
changes.getNextVersion (cognitive 21) scripts/utils/changes.ts:117— changes.getNextVersion has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 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.
documented-api.getApiParameters (cognitive 20) docs/site/scripts/generate/documented-api.ts:699— documented-api.getApiParameters has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
examples.highlightSource (cognitive 20) docs/ui/app/data/examples.tsx:43— examples.highlightSource has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 9). 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.
config.normalizeAssetTransformInvocation (cognitive 20) packages/assets/src/lib/files/config.ts:405— config.normalizeAssetTransformInvocation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
help.getCommandHelpText (cognitive 20) packages/cli/src/lib/commands/help.ts:84— help.getCommandHelpText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, boolean chains 8, ternaries 1 (2 pts) (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.
diff-dom.shouldPreserveLiveAttribute (cognitive 20) packages/component/src/runtime/diff-dom.ts:173— diff-dom.shouldPreserveLiveAttribute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5 (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.
reconcile.patchKeyedChildren (cognitive 20) REDACTED:1750— reconcile.patchKeyedChildren has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (6 pts), ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prefetch.startPrefetching (cognitive 20) packages/component/src/runtime/prefetch.ts:47— prefetch.startPrefetching has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 8, ternaries 1. Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (trigger, leave, a function literal at line 140, …). 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.
cors.resolveAllowedOrigin (cognitive 20) REDACTED:268— cors.resolveAllowedOrigin has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (4 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.
module-store.createModuleStore (cognitive 20) packages/node-hmr/src/lib/module-store.ts:29— module-store.createModuleStore has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 3, boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (findPropagationFromImporters, visit, findPropagation, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
file-matcher.createFileMatcher (cognitive 19) packages/assets/src/lib/file-matcher.ts:8— file-matcher.createFileMatcher has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 2 (5 pts), boolean chains 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.
remix-config.parseTestConfig (cognitive 19) REDACTED:403— remix-config.parseTestConfig has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
project.hasOnlyWhitespaceAndComments (cognitive 19) packages/cli/src/lib/doctor/project.ts:165— project.hasOnlyWhitespaceAndComments has cognitive complexity 19 (threshold 15). Drivers by points: loops 3 (7 pts), boolean chains 6, if/else 3 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform.shouldRewriteIdentifier (cognitive 19) packages/component-hmr/src/lib/transform.ts:1011— transform.shouldRewriteIdentifier has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
stream.hoistClientEntryResourcesFromFrameHead (cognitive 19) packages/component/src/server/stream.ts:1481— stream.hoistClientEntryResourcesFromFrameHead has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cop.matchesBypassPattern (cognitive 19) packages/cop-middleware/src/lib/cop.ts:312— cop.matchesBypassPattern has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, ternaries 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
request-listener.createRequestListener (cognitive 19) packages/node-fetch-server/src/lib/request-listener.ts:99— request-listener.createRequestListener has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 4 (8 pts) (nesting depth added 9). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 131, 108, 156). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TarParser.#write (cognitive 19) REDACTED:568— TarParser.#write has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workspaces.getAffectedWorkspaceDirs (cognitive 19) scripts/utils/workspaces.ts:61— workspaces.getAffectedWorkspaceDirs has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 4 (7 pts), boolean chains 1 (nesting depth added 7). 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, 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.
prompt-button.PromptButton.<returned closure> (cognitive 19) template/app/actions/public/prompt-button.tsx:12— prompt-button.PromptButton.<returned closure> has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 5 (7 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 8 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.
deep-equal.compareBytes (cognitive 18) packages/assert/src/lib/deep-equal.ts:41— deep-equal.compareBytes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 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.
optimize-barrel-file-imports.getReplacementImportPaths (cognitive 18) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:267— optimize-barrel-file-imports.getReplacementImportPaths has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3, boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (visit, markEvaluated). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
resolve.resolveStyle (cognitive 18) packages/assets/src/lib/styles/resolve.ts:75— resolve.resolveStyle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
completion.completeRoutes (cognitive 18) packages/cli/src/lib/completion.ts:478— completion.completeRoutes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
props.patchStyleObject (cognitive 18) REDACTED:163— props.patchStyleObject has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), ternaries 1 (2 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.
navigation.resyncWebKitScrollAfterNavigation (cognitive 18) packages/component/src/runtime/navigation.ts:62— navigation.resyncWebKitScrollAfterNavigation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, loops 2 (nesting depth added 1). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (undoRestoration, a function literal at line 112, a function literal at line 122, …). 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.
stream.streamPendingFrames (cognitive 18) packages/component/src/server/stream.ts:1891— stream.streamPendingFrames has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 1905). 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.
form-data.readUrlEncodedBody (cognitive 18) packages/form-data-parser/src/lib/form-data.ts:144— form-data.readUrlEncodedBody has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContentDisposition.from (cognitive 18) packages/headers/src/lib/content-disposition.ts:112— ContentDisposition.from has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
join.joinPathname (cognitive 18) packages/route-pattern/src/lib/join.ts:52— join.joinPathname has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 2 (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TarParser.#parseHeader (cognitive 18) REDACTED:609— TarParser.#parseHeader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
preview.publishPrPreview (cognitive 18) scripts/utils/preview.ts:479— preview.publishPrPreview has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate-package-meta.validateConsistentConsumerDependencyRanges (cognitive 18) scripts/validate-package-meta.ts:199— validate-package-meta.validateConsistentConsumerDependencyRanges has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 4 (7 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.
page.readPageHeadings::visit (cognitive 17) docs/ui/app/pages/page.tsx:87— page.readPageHeadings::visit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cjs-check.collectPatternScopeBindings (cognitive 17) packages/assets/src/lib/scripts/cjs-check.ts:295— cjs-check.collectPatternScopeBindings has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1, match/switch 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.getHmrAnalysis (cognitive 17) packages/assets/src/lib/scripts/transform.ts:299— transform.getHmrAnalysis has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 321). 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.
completion.completeNew (cognitive 17) packages/cli/src/lib/completion.ts:418— completion.completeNew has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2, boolean chains 1, 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-dom.matchShiftedHeadUnits (cognitive 17) packages/component/src/runtime/diff-dom.ts:397— diff-dom.matchShiftedHeadUnits has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reconcile.findEdgeDomNode (cognitive 17) REDACTED:2060— reconcile.findEdgeDomNode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stream.collectAuthoredImportMap (cognitive 17) packages/component/src/server/stream.ts:793— stream.collectAuthoredImportMap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (4 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.
stream.renderAttributes (cognitive 17) packages/component/src/server/stream.ts:922— stream.renderAttributes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, 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.
sql-compiler.rewriteRawPlaceholders (cognitive 17) packages/data-table-postgres/src/lib/sql-compiler.ts:269— sql-compiler.rewriteRawPlaceholders has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, 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.
query.cloneQueryPlan (cognitive 17) packages/data-table/src/lib/query.ts:770— query.cloneQueryPlan has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (16 pts), match/switch 1 (nesting depth added 9). 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.
ContentType.from (cognitive 17) packages/headers/src/lib/content-type.ts:85— ContentType.from has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (4 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SuperHeaders.#applyHeaderValue (cognitive 17) packages/headers/src/lib/super-headers.ts:447— SuperHeaders.#applyHeaderValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tar.validatePaths (cognitive 17) REDACTED:211— tar.validatePaths has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
anchor.calculatePosition (cognitive 17) packages/ui/src/anchor.ts:192— anchor.calculatePosition has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16 (17 pts) (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.
changes.generateChangelogContent (cognitive 17) scripts/utils/changes.ts:787— changes.generateChangelogContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
detect-changed-packages.getSelectedPackageNames (cognitive 17) scripts/detect-changed-packages.ts:178— detect-changed-packages.getSelectedPackageNames has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (7 pts), boolean chains 1 (nesting depth added 7). 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.
release-pr.main (cognitive 17) scripts/release-pr.ts:21— release-pr.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (3 pts), ternaries 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
api-nav.ApiNav.<returned closure> (cognitive 16) docs/site/app/actions/public/api-nav.tsx:148— api-nav.ApiNav.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (5 pts), loops 2 (4 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 5). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body 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.
cjs-check.isReferenceIdentifier (cognitive 16) packages/assets/src/lib/scripts/cjs-check.ts:382— cjs-check.isReferenceIdentifier has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. 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.
resolve.batchResolveSpecifiers (cognitive 16) packages/assets/src/lib/scripts/resolve.ts:677— resolve.batchResolveSpecifiers has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (5 pts), boolean chains 2, error handling 1, 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.
cache.createFsFileCache.initialize (cognitive 16) packages/assets/src/lib/files/cache.ts:57— cache.createFsFileCache.initialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
completion.completeTopLevel (cognitive 16) packages/cli/src/lib/completion.ts:174— completion.completeTopLevel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, 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.
completion.completeDbOptions (cognitive 16) packages/cli/src/lib/completion.ts:597— completion.completeDbOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (4 pts), boolean chains 1, 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.
cli.extractGlobalOptions (cognitive 16) packages/cli/src/lib/cli.ts:142— cli.extractGlobalOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform.getTrackedExports (cognitive 16) packages/component-hmr/src/lib/transform.ts:1280— transform.getTrackedExports has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 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.
import-map-manager.installImports (cognitive 16) packages/component/src/runtime/import-map-manager.ts:204— import-map-manager.installImports has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
frame.reviveSerializedValue (cognitive 16) packages/component/src/runtime/frame.ts:1585— frame.reviveSerializedValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, ternaries 2 (4 pts), boolean chains 2 (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.
stream.renderToStream (cognitive 16) packages/component/src/server/stream.ts:320— stream.renderToStream has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), error handling 1, loops 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs to one function item 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.
stream.parseAuthoredImportMap (cognitive 16) packages/component/src/server/stream.ts:1736— stream.parseAuthoredImportMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (2 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.record (cognitive 16) packages/data-schema/src/lib/schema.ts:995— schema.record has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 999). 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.
form-data.parseField (cognitive 16) packages/data-schema/src/lib/form-data.ts:212— form-data.parseField has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 6). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
CacheControl.toString (cognitive 16) packages/headers/src/lib/cache-control.ts:254— CacheControl.toString has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. 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.
CacheControl.from (cognitive 16) packages/headers/src/lib/cache-control.ts:315— CacheControl.from has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 1 (5 pts), loops 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lazy-file.streamContentArray (cognitive 16) packages/lazy-file/src/lib/lazy-file.ts:468— lazy-file.streamContentArray has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (pushPart, pushChunk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
program.canonicalizeText (cognitive 16) packages/route-pattern/src/lib/match/program.ts:202— program.canonicalizeText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 2, loops 2, error handling 1 (nesting depth added 4). Of this number, 8 points are the body's own statements and 8 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.
program.matchLinearPart (cognitive 16) packages/route-pattern/src/lib/match/program.ts:383— program.matchLinearPart has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 3, loops 2 (3 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.
combobox.inputMixin.<returned closure> (cognitive 16) packages/ui/src/combobox.tsx:755— combobox.inputMixin.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3, boolean chains 1, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 785, 775). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Change coupling clique: driver.ts, driver.ts, driver.ts packages/data-table-mysql/src/lib/driver.ts— 3 files — `packages/data-table-mysql/src/lib/driver.ts`, `packages/data-table-postgres/src/lib/driver.ts`, `packages/data-table-sqlite/src/lib/driver.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Unstable project remix — remix has instability 0.92 with 4 dependents.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to packages/node-hmr/src/register.ts:141— The guard above `return source;` also returns `source`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
No structured logging — No logging call was found in the 819 JavaScript/TypeScript production file(s) this check read across 82 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 21 sibling directories (42 clone groups) packages/data-table-mysql/src/lib/driver.ts:78— 42 duplicated blocks under packages/ have copies in at least two of the sibling directories assets, cli, component, component-hmr, data-table-mysql, data-table-postgres (+15 more sibling(s) not listed) — 37 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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 3 sibling directories (23 clone groups) packages/assets/src/lib/scripts/compiler.ts:1106— 23 duplicated blocks under packages/assets/src/lib/ have copies in at least two of the sibling directories files, scripts, styles — 13 of them are reported below, and 10 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (305 matched lines × 2 locations) · ×1
Duplicated block with local edits (305 matched lines × 2 locations) packages/data-table-mysql/src/lib/driver.ts:78— packages/data-table-mysql/src/lib/driver.ts:78 · packages/data-table-postgres/src/lib/driver.ts:72 — the two spans are one implementation copied and then locally edited — 1707 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (224 matched lines × 2 locations) · ×1
Duplicated block with local edits (224 matched lines × 2 locations) packages/ui/src/accordion.tsx:13— packages/ui/src/accordion.tsx:13 · packages/ui/src/tabs.ts:14 — the two spans are one implementation copied and then locally edited — 1043 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 (192 identical lines × 2 files) packages/data-table-mysql/src/lib/sql-compiler.ts:1— packages/data-table-mysql/src/lib/sql-compiler.ts:1 · packages/data-table-sqlite/src/lib/sql-compiler.ts:1 — these 2 files are line-for-line copies of one another — 192 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 (115 lines × 2 locations) packages/headers/src/lib/accept-language.ts:8— packages/headers/src/lib/accept-language.ts:8 · packages/headers/src/lib/accept.ts:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (86 lines × 3 locations) packages/headers/src/lib/accept-encoding.ts:70— packages/headers/src/lib/accept-encoding.ts:70 · packages/headers/src/lib/accept-language.ts:75 · packages/headers/src/lib/accept.ts:74 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (78 lines × 2 locations) packages/data-table-postgres/src/lib/sql-compiler.ts:545— packages/data-table-postgres/src/lib/sql-compiler.ts:545 · packages/data-table-sqlite/src/lib/sql-compiler.ts:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (68 matched lines × 2 locations) · ×1
Duplicated block with local edits (68 matched lines × 2 locations) packages/fetch-router/src/lib/route-helpers/resource.ts:21— packages/fetch-router/src/lib/route-helpers/resource.ts:21 · packages/fetch-router/src/lib/route-helpers/resources.ts:28 — the two spans are one implementation copied and then locally edited — 459 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (62 lines × 2 locations) packages/assets/src/lib/scripts/resolve.ts:174— packages/assets/src/lib/scripts/resolve.ts:174 · packages/assets/src/lib/scripts/resolve.ts:331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (62 matched lines × 2 locations) · ×1
Duplicated block with local edits (62 matched lines × 2 locations) packages/auth/src/lib/providers/facebook.ts:52— packages/auth/src/lib/providers/facebook.ts:52 · packages/auth/src/lib/providers/x.ts:54 — the two spans are one implementation copied and then locally edited — 314 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) packages/form-data-parser/src/lib/form-data.ts:232— packages/form-data-parser/src/lib/form-data.ts:232 · packages/form-data-parser/src/lib/future/form-data.ts:271 — the two spans are one implementation copied and then locally edited — 263 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (45 lines × 2 locations) packages/multipart-parser/src/lib/future/multipart.ts:341— packages/multipart-parser/src/lib/future/multipart.ts:341 · packages/multipart-parser/src/lib/multipart.ts:511 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×1
Duplicated block with local edits (42 matched lines × 2 locations) packages/node-tsx/src/lib/loader.ts:30— packages/node-tsx/src/lib/loader.ts:30 · packages/node-tsx/src/lib/register-hooks.ts:21 — the two spans are one implementation copied and then locally edited — 230 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) packages/session-storage-memcache/src/lib/memcache-storage.ts:62— packages/session-storage-memcache/src/lib/memcache-storage.ts:62 · packages/session/src/lib/session-storage/fs.ts:130 — the two spans are one implementation copied and then locally edited — 223 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (35 lines × 2 locations) packages/data-table-postgres/src/lib/sql-compiler.ts:48— packages/data-table-postgres/src/lib/sql-compiler.ts:48 · packages/data-table-sqlite/src/lib/sql-compiler.ts:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 2 locations) packages/assets/src/lib/scripts/transform.ts:200— packages/assets/src/lib/scripts/transform.ts:200 · packages/assets/src/lib/styles/transform.ts:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) packages/headers/src/lib/if-match.ts:7— packages/headers/src/lib/if-match.ts:7 · packages/headers/src/lib/if-none-match.ts:7 — the two spans are one implementation copied and then locally edited — 217 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (29 lines × 2 locations) packages/data-table-postgres/src/lib/sql-compiler.ts:151— packages/data-table-postgres/src/lib/sql-compiler.ts:151 · packages/data-table-sqlite/src/lib/sql-compiler.ts:150 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (27 lines × 2 locations) packages/assets/src/lib/styles/resolve.ts:183— packages/assets/src/lib/styles/resolve.ts:183 · packages/assets/src/lib/styles/resolve.ts:246 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) scripts/detect-changed-packages.ts:188— scripts/detect-changed-packages.ts:188 · scripts/utils/workspaces.ts:78 — the two spans are one implementation copied and then locally edited — 160 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (25 lines × 3 locations) packages/data-table-mysql/src/lib/driver.ts:705— packages/data-table-mysql/src/lib/driver.ts:705 · packages/data-table-postgres/src/lib/driver.ts:652 · packages/data-table-sqlite/src/lib/driver.ts:539 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Boundary violation [package:relative-cross-package] scripts/postinstall.ts:9— scripts/postinstall.ts:9 reaches into another package with a relative path (../packages/component/node_modules/playwright/cli.js) — import the package by name instead.
Complex function (top-level) (cyclomatic 87, cognitive 86) packages/route-pattern/src/lib/types/parse.ts:1— (top-level) has cyclomatic complexity 87 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 insert (cyclomatic 59, cognitive 127) REDACTED:1162— insert has cyclomatic complexity 59 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 compare (cyclomatic 59, cognitive 58) packages/assert/src/lib/deep-equal.ts:278— compare has cyclomatic complexity 59 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 isChildMessage (cyclomatic 57, cognitive 53) REDACTED:1261— isChildMessage has cyclomatic complexity 57 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 write (cyclomatic 46, cognitive 118) packages/multipart-parser/src/lib/multipart.ts:298— write has cyclomatic complexity 46 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 main (cyclomatic 45, cognitive 70) · ×1
Complex function main (cyclomatic 45, cognitive 70) scripts/publish.ts:399— main has cyclomatic complexity 45 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 executeRun (cyclomatic 43, cognitive 62) packages/test/src/cli.ts:146— executeRun has cyclomatic complexity 43 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 normalizeFilesOptions (cyclomatic 43, cognitive 54) packages/assets/src/lib/files/config.ts:183— normalizeFilesOptions has cyclomatic complexity 43 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 onResult (cyclomatic 42, cognitive 103) packages/test/src/lib/reporters/spec.ts:20— onResult has cyclomatic complexity 42 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function write (cyclomatic 42, cognitive 102) packages/multipart-parser/src/lib/future/multipart.ts:136— write has cyclomatic complexity 42 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 runTests (cyclomatic 42, cognitive 80) packages/test/src/lib/executor.ts:43— runTests has cyclomatic complexity 42 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 parsePackageChanges (cyclomatic 39, cognitive 58) scripts/utils/changes.ts:188— parsePackageChanges has cyclomatic complexity 39 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getExportAnalysis (cyclomatic 35, cognitive 68) packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:414— getExportAnalysis has cyclomatic complexity 35 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 34, cognitive 50) packages/multiple-import-maps-polyfill/src/lib/core.ts:271— (anonymous) has cyclomatic complexity 34 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 buildElementSegment (cyclomatic 34, cognitive 39) packages/component/src/server/stream.ts:663— buildElementSegment has cyclomatic complexity 34 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function matchPart (cyclomatic 33, cognitive 73) packages/route-pattern/src/lib/match/program.ts:252— matchPart has cyclomatic complexity 33 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 patchHostProps (cyclomatic 33, cognitive 52) REDACTED:57— patchHostProps has cyclomatic complexity 33 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 createFileResponse (cyclomatic 33, cognitive 48) packages/response/src/lib/file.ts:129— createFileResponse has cyclomatic complexity 33 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 walkForCommonJS (cyclomatic 33, cognitive 35) packages/assets/src/lib/scripts/cjs-check.ts:49— walkForCommonJS has cyclomatic complexity 33 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveModule (cyclomatic 32, cognitive 54) packages/assets/src/lib/scripts/resolve.ts:135— resolveModule has cyclomatic complexity 32 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/component/src/runtime/dom.ts · ×1
packages/component/src/runtime/dom.ts: 3970 lines of code packages/component/src/runtime/dom.ts:1— packages/component/src/runtime/dom.ts has 3970 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/component/src/runtime/frame.ts · ×1
packages/component/src/runtime/frame.ts: 2006 lines of code packages/component/src/runtime/frame.ts:1— packages/component/src/runtime/frame.ts has 2006 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: 1901 lines of code REDACTED:1— REDACTED has 1901 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/component/src/server/stream.ts · ×1
packages/component/src/server/stream.ts: 1781 lines of code packages/component/src/server/stream.ts:1— packages/component/src/server/stream.ts has 1781 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/assets/src/lib/asset-server.ts · ×1
packages/assets/src/lib/asset-server.ts: 1255 lines of code packages/assets/src/lib/asset-server.ts:1— packages/assets/src/lib/asset-server.ts has 1255 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/component-hmr/src/lib/transform.ts · ×1
packages/component-hmr/src/lib/transform.ts: 1248 lines of code packages/component-hmr/src/lib/transform.ts:1— packages/component-hmr/src/lib/transform.ts has 1248 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: 1248 lines of code REDACTED:1— REDACTED has 1248 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/data-schema/src/lib/schema.ts · ×1
packages/data-schema/src/lib/schema.ts: 1199 lines of code packages/data-schema/src/lib/schema.ts:1— packages/data-schema/src/lib/schema.ts has 1199 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/data-table/src/lib/table.ts · ×1
packages/data-table/src/lib/table.ts: 1159 lines of code packages/data-table/src/lib/table.ts:1— packages/data-table/src/lib/table.ts has 1159 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/ui/src/menu.tsx: 1096 lines of code packages/ui/src/menu.tsx:1— packages/ui/src/menu.tsx has 1096 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/assets/src/lib/scripts/compiler.ts · ×1
packages/assets/src/lib/scripts/compiler.ts: 986 lines of code packages/assets/src/lib/scripts/compiler.ts:1— packages/assets/src/lib/scripts/compiler.ts has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/headers/src/lib/super-headers.ts · ×1
packages/headers/src/lib/super-headers.ts: 931 lines of code packages/headers/src/lib/super-headers.ts:1— packages/headers/src/lib/super-headers.ts has 931 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/data-table/src/lib/query.ts · ×1
packages/data-table/src/lib/query.ts: 873 lines of code packages/data-table/src/lib/query.ts:1— packages/data-table/src/lib/query.ts has 873 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/data-table/src/lib/database.ts · ×1
packages/data-table/src/lib/database.ts: 861 lines of code packages/data-table/src/lib/database.ts:1— packages/data-table/src/lib/database.ts has 861 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/assets/src/lib/scripts/transform.ts · ×1
packages/assets/src/lib/scripts/transform.ts: 860 lines of code packages/assets/src/lib/scripts/transform.ts:1— packages/assets/src/lib/scripts/transform.ts has 860 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/ui/src/anchor.ts: 858 lines of code packages/ui/src/anchor.ts:1— packages/ui/src/anchor.ts has 858 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/component/src/runtime/diff-dom.ts · ×1
packages/component/src/runtime/diff-dom.ts: 833 lines of code packages/component/src/runtime/diff-dom.ts:1— packages/component/src/runtime/diff-dom.ts has 833 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
scripts/utils/changes.ts: 810 lines of code scripts/utils/changes.ts:1— scripts/utils/changes.ts has 810 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/ui/src/combobox.tsx · ×1
packages/ui/src/combobox.tsx: 795 lines of code packages/ui/src/combobox.tsx:1— packages/ui/src/combobox.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.
scripts/generate-remix.ts: 795 lines of code scripts/generate-remix.ts:1— scripts/generate-remix.ts 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· packages/assert/src/lib/assert.ts · ×1
packages/assert/src/lib/assert.ts: 788 lines of code packages/assert/src/lib/assert.ts:1— packages/assert/src/lib/assert.ts has 788 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/component/src/runtime/navigation.ts · ×1
packages/component/src/runtime/navigation.ts: 774 lines of code packages/component/src/runtime/navigation.ts:1— packages/component/src/runtime/navigation.ts has 774 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: 761 lines of code REDACTED:1— REDACTED has 761 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/assets/src/lib/scripts/resolve.ts · ×1
packages/assets/src/lib/scripts/resolve.ts: 749 lines of code packages/assets/src/lib/scripts/resolve.ts:1— packages/assets/src/lib/scripts/resolve.ts has 749 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/assets/src/lib/files/compiler.ts · ×1
packages/assets/src/lib/files/compiler.ts: 748 lines of code packages/assets/src/lib/files/compiler.ts:1— packages/assets/src/lib/files/compiler.ts has 748 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: 741 lines of code REDACTED:1— REDACTED has 741 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/node-fetch-server/src/lib/request-listener.ts · ×1
packages/node-fetch-server/src/lib/request-listener.ts: 683 lines of code packages/node-fetch-server/src/lib/request-listener.ts:1— packages/node-fetch-server/src/lib/request-listener.ts has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
scripts/utils/preview.ts: 668 lines of code scripts/utils/preview.ts:1— scripts/utils/preview.ts has 668 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/multipart-parser/src/lib/future/multipart.ts · ×1
packages/multipart-parser/src/lib/future/multipart.ts: 667 lines of code packages/multipart-parser/src/lib/future/multipart.ts:1— packages/multipart-parser/src/lib/future/multipart.ts has 667 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: 663 lines of code REDACTED:1— REDACTED has 663 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/data-table-mysql/src/lib/driver.ts · ×1
packages/data-table-mysql/src/lib/driver.ts: 641 lines of code packages/data-table-mysql/src/lib/driver.ts:1— packages/data-table-mysql/src/lib/driver.ts has 641 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/data-table-postgres/src/lib/driver.ts · ×1
packages/data-table-postgres/src/lib/driver.ts: 637 lines of code packages/data-table-postgres/src/lib/driver.ts:1— packages/data-table-postgres/src/lib/driver.ts has 637 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/cli/src/lib/completion.ts · ×1
packages/cli/src/lib/completion.ts: 635 lines of code packages/cli/src/lib/completion.ts:1— packages/cli/src/lib/completion.ts has 635 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/multipart-parser/src/lib/multipart.ts · ×1
packages/multipart-parser/src/lib/multipart.ts: 614 lines of code packages/multipart-parser/src/lib/multipart.ts:1— packages/multipart-parser/src/lib/multipart.ts has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 606 lines of code REDACTED:1— REDACTED has 606 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/assets/src/lib/scripts/optimize-barrel-file-imports.ts · ×1
packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts: 602 lines of code packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts:1— packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts has 602 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/data-table/src/lib/database/query-execution.ts · ×1
packages/data-table/src/lib/database/query-execution.ts: 599 lines of code packages/data-table/src/lib/database/query-execution.ts:1— packages/data-table/src/lib/database/query-execution.ts has 599 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/data-table-postgres/src/lib/sql-compiler.ts · ×1
packages/data-table-postgres/src/lib/sql-compiler.ts: 584 lines of code packages/data-table-postgres/src/lib/sql-compiler.ts:1— packages/data-table-postgres/src/lib/sql-compiler.ts has 584 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/data-table-sqlite/src/lib/driver.ts · ×1
packages/data-table-sqlite/src/lib/driver.ts: 582 lines of code packages/data-table-sqlite/src/lib/driver.ts:1— packages/data-table-sqlite/src/lib/driver.ts has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
scripts/publish.ts: 580 lines of code scripts/publish.ts:1— scripts/publish.ts has 580 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts:2— This repository declares test tooling, and the ✓ above records that declaration — but packages/multiple-import-maps-polyfill/test/base-href.test.browser.ts and 7 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~119 LoC) packages/cli/src/lib/load-route-map-worker.ts— no import path from any entry point (276 application, 22 tooling, 516 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~34 LoC) scripts/node-test-reporter.ts— no import path from any entry point (276 application, 22 tooling, 516 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 (~13 LoC) packages/node-fetch-server/src/lib/read-stream.ts— no import path from any entry point (276 application, 22 tooling, 516 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 · ×1
Async function without AbortSignal: s3Fetch REDACTED:96— `s3Fetch` 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/multiple-import-maps-polyfill/src/lib/native-resolve.ts:50— `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.
Disabled test packages/component/src/runtime/mixins/on-mixin.test.tsx:372— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:108— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:121— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:127— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:151— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:207— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:334— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:347— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:391— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:425— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:471— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/data-table/src/lib/type-safety.test.ts:519— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.browser.ts:54— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.browser.ts:61— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:81— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:86— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:92— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:103— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:117— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:130— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:145— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:260— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:269— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:279— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/test/src/test/framework.test.ts:280— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Duplicated predicate docs/site/app/actions/public/entry.tsx:56— `!formData || method?.toLowerCase() === 'get'` appears character-identically in 2 files — docs/site/app/actions/public/entry.tsx, docs/ui/app/actions/public/entry.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 docs/site/app/actions/guides/markdown/render.tsx:95— `!href.startsWith('/') || href.startsWith('//')` appears character-identically in 2 files — docs/site/app/actions/guides/markdown/render.tsx, docs/site/app/routes.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/assets/src/lib/scripts/compiler.ts:744— `!identityPath || reachable.has(identityPath)` appears character-identically in 2 files — packages/assets/src/lib/scripts/compiler.ts, packages/assets/src/lib/scripts/optimize-barrel-file-imports.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/data-table-mysql/src/lib/driver.ts:736— `!isInsertOperationKind(kind) || !isInsertOperation(operation)` appears character-identically in 3 files — packages/data-table-mysql/src/lib/driver.ts, packages/data-table-postgres/src/lib/driver.ts, packages/data-table-sqlite/src/lib/driver.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/headers/src/lib/header-names.ts:14— `HeaderWordCasingExceptions[word] || word.charAt(0).toUpperCase() + word.slice(1)` appears character-identically in 2 files — packages/headers/src/lib/header-names.ts, scripts/oxlint-plugins/canonical-header-names-plugin.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate .agents/skills/supersede-pr/scripts/close_superseded_pr.ts:88— `argv.includes('-h') || argv.includes('--help')` appears character-identically in 7 files — .agents/skills/supersede-pr/scripts/close_superseded_pr.ts, packages/cli/src/lib/commands/assets.ts, packages/cli/src/lib/commands/completion.ts, packages/cli/src/lib/commands/doctor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/cli/src/lib/commands/db.ts:39— `argv.length === 0 || argv.includes('-h') || argv.includes('--help')` appears character-identically in 2 files — packages/cli/src/lib/commands/db.ts, packages/cli/src/lib/commands/new.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/assets/src/lib/scripts/transform.ts:359— `callee.computed || !isIdentifierNode(callee.property, 'accept')` appears character-identically in 2 files — packages/assets/src/lib/scripts/transform.ts, packages/node-hmr/src/lib/hmr-analysis.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/multipart-parser/src/lib/future/multipart.ts:247— `chunk[index] !== 13 || chunk[index + 1] !== 10` appears character-identically in 2 files — packages/multipart-parser/src/lib/future/multipart.ts, packages/multipart-parser/src/lib/multipart.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/multipart-parser/src/lib/future/multipart.ts:238— `chunk[index] === 32 || chunk[index] === 9` appears character-identically in 2 files — packages/multipart-parser/src/lib/future/multipart.ts, packages/multipart-parser/src/lib/multipart.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/multipart-parser/src/lib/future/multipart.ts:221— `chunk[index] === 45 && chunk[index + 1] === 45` appears character-identically in 2 files — packages/multipart-parser/src/lib/future/multipart.ts, packages/multipart-parser/src/lib/multipart.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/ui/src/form-context.ts:313— `control instanceof HTMLInputElement && control.checked && !control.matches(':disabled')` appears character-identically in 2 files — packages/ui/src/form-context.ts, packages/ui/src/form-control.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 docs/site/app/actions/public/entry.tsx:111— `current.hash !== '' || destination.hash !== ''` appears character-identically in 2 files — docs/site/app/actions/public/entry.tsx, docs/ui/app/actions/public/entry.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/auth/src/lib/providers/oidc.ts:190— `currentTokens.refreshToken == null || currentTokens.refreshToken.length === 0` appears character-identically in 2 files — packages/auth/src/lib/providers/oidc.ts, packages/auth/src/lib/providers/x.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/component/src/runtime/client-entries.ts:148— `cursor && cursor.nodeType === Node.COMMENT_NODE` appears character-identically in 2 files — packages/component/src/runtime/client-entries.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate docs/site/scripts/generate/packages.ts:320— `error instanceof Error && 'code' in error` appears character-identically in 4 files — docs/site/scripts/generate/packages.ts, REDACTED, packages/session/src/lib/session-storage/fs.ts, scripts/utils/remix-readmes.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/assets/src/lib/access.ts:455— `error instanceof Error && 'code' in error && ((error as NodeJS.ErrnoException).code === 'ENOENT' || (error as NodeJS.ErrnoException).code ==…` appears character-identically in 5 files — packages/assets/src/lib/access.ts, packages/assets/src/lib/file-matcher.ts, packages/assets/src/lib/files/compiler.ts, packages/assets/src/lib/scripts/compiler.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/assets/src/lib/scripts/transform.ts:969— `error instanceof Error && 'code' in error && (error as NodeJS.ErrnoException).code === 'ENOENT'` appears character-identically in 4 files — packages/assets/src/lib/scripts/transform.ts, packages/assets/src/lib/styles/resolve.ts, packages/assets/src/lib/styles/transform.ts, packages/session/src/lib/session-storage/fs.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 docs/site/app/actions/controller.tsx:102— `error instanceof Error && 'code' in error && (error.code === 'ENOENT' || error.code === 'ENOTDIR')` appears character-identically in 3 files — docs/site/app/actions/controller.tsx, docs/ui/app/actions/controller.tsx, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/form-data-parser/src/lib/form-data.ts:125— `error instanceof FormDataParseError || isParserLimitError(error)` appears character-identically in 2 files — packages/form-data-parser/src/lib/form-data.ts, packages/form-data-parser/src/lib/future/form-data.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/ui/src/lib/typeahead.ts:43— `event.key.length === 1 && !event.ctrlKey && !event.altKey && !event.metaKey` appears character-identically in 2 files — packages/ui/src/lib/typeahead.ts, packages/ui/src/menu.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/ui/src/lib/typeahead.ts:34— `event.relatedTarget instanceof Node && event.currentTarget.contains(event.relatedTarget)` appears character-identically in 2 files — packages/ui/src/lib/typeahead.ts, packages/ui/src/menu.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/node-tsx/src/lib/loader.ts:93— `filePath.endsWith('.ts') || filePath.endsWith('.tsx') || filePath.endsWith('.jsx')` appears character-identically in 2 files — packages/node-tsx/src/lib/loader.ts, packages/node-tsx/src/lib/register-hooks.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/assets/src/lib/scripts/transform.ts:367— `hot.computed || !isIdentifierNode(hot.property, 'hot')` appears character-identically in 2 files — packages/assets/src/lib/scripts/transform.ts, packages/node-hmr/src/lib/hmr-analysis.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/multipart-parser/src/lib/future/multipart.ts:242— `index === chunkLength || (chunk[index] === 13 && chunkLength - index === 1)` appears character-identically in 2 files — packages/multipart-parser/src/lib/future/multipart.ts, packages/multipart-parser/src/lib/multipart.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.
redundant comment docs/shared/prerender/utils.ts:38— "Write all script files to disk as JS files" repeats the code it sits on: 4 of its 5 words (write, script, files, js) are already in `await fs.writeFile(outputPath, content.replace(SCRIPT_EXT_IN_JS_IMPORT, '.js'), 'utf-8')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment docs/site/scripts/generate/documented-api.ts:53— 5 comments in this file only repeat the code they sit on (lines 53, 62, 73, 89, 101), for example "Documented function API". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/component/bench/runner.ts:554— "Load previous remix results if they exist" repeats the code it sits on: 4 of its 5 words (load, previous, remix, results) are already in `function loadPreviousRemixResults(): BenchmarkResult[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:335— "When innerHTML is set, ignore children" repeats the code it sits on: 4 of its 5 words (inner, html, set, children) are already in `let children = props.innerHTML != null ? [] : flatMapChildrenToVNodes(props)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/component/src/test/frame.test.tsx:5172— "Render middle content (pending inner frame with fallback)." repeats the code it sits on: 6 of its 7 words (render, middle, content, inner, frame, fallback) are already in `let middleStream = renderToStream(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/component/src/test/frame.test.tsx:5186— "Render outer content (pending middle frame with fallback)." repeats the code it sits on: 6 of its 7 words (render, outer, content, middle, frame, fallback) are already in `let outerStream = renderToStream(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/component/src/test/frame.test.tsx:5299— "Render page with a blocking outer frame that resolves to the outer content." repeats the code it sits on: 6 of its 7 words (render, page, outer, frame, resolves, content) are already in `let pageStream = renderToStream(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/mime/scripts/codegen.ts:119— "Generate compressible-mime-types.ts" repeats the code it sits on: 4 of its 5 words (compressible, mime, types, ts) are already in `let compressibleOutputPath = join(__dirname, '../src/generated/compressible-mime-types.ts')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/node-fetch-server/src/lib/request-listener.ts:16— ""Internal Server Error"" repeats the code it sits on: 3 of its 3 words (internal, server, error) are already in `const internalServerErrorBody = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/response/src/lib/html.ts:84— "Check if the first chunk starts with DOCTYPE" repeats the code it sits on: 5 of its 5 words (check, first, chunk, starts, doctype) are already in `if (startsWithDoctypeBytes(firstChunk.value))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/changes-version.ts:122— "Update REDACTED" repeats the code it sits on: 3 of its 3 words (update, package, json) are already in `updatePackageJson(release.packageDirName, release.nextVersion)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/changes-version.ts:129— "Delete change files" repeats the code it sits on: 3 of its 3 words (delete, change, files) are already in `deleteChangeFiles(release.packageDirName)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/publish.ts:433— "Publish packages to npm" repeats the code it sits on: 3 of its 3 words (publish, packages, npm) are already in `console.log('Publishing packages to npm...\n')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/release-pr.ts:96— "Reset to base branch" repeats the code it sits on: 3 of its 3 words (reset, base, branch) are already in `logAndExec('git', ['reset', '--hard', `origin/${baseBranch}`])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/utils/changes.ts:246— "Config has prerelease channel" repeats the code it sits on: 3 of its 3 words (config, prerelease, channel) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/utils/changes.ts:548— "Sort dependency bumps alphabetically by package name" repeats the code it sits on: 5 of its 6 words (sort, dependency, bumps, package, name) are already in `dependencyBumps.sort((a, b) => a.packageName.localeCompare(b.packageName))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Classify ADR enforcement: RoutePattern vs. URLPattern decisions/001-route-pattern-vs-url-pattern.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Branching and Releasing in Remix 3 decisions/002-branching-and-releasing.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Why `remix-test` owns its TypeScript transform for coverage decisions/003-coverage-transform-determinism.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: V8-native coverage vs. Istanbul instrumentation decisions/004-v8-vs-istanbul-instrumentation.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Use only trie-based matching for `route-pattern decisions/005-trie-based-matching.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Use `.sql` files for migrations decisions/006-sql-migrations.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Discover prefetch assets from HTML and use the browser cache decisions/007-frame-prefetch-assets.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: Form schemas with native validation and context-scoped feedback decisions/007-model-backed-forms.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Documentation: no build, run or usage example packages/fetch-router/demos/bun/README.md:1— `bun` is runnable (a `start` script in `REDACTED`) and neither `packages/fetch-router/demos/bun/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/fetch-router/demos/node/README.md:1— `node` is runnable (a `start` script in `REDACTED`) and neither `packages/fetch-router/demos/node/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/form-data-parser/demos/node/README.md:1— `node` is runnable (a `start` script in `REDACTED`) and neither `packages/form-data-parser/demos/node/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/multipart-parser/demos/bun/README.md:1— `bun` is runnable (a `start` script in `REDACTED`) and neither `packages/multipart-parser/demos/bun/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/multipart-parser/demos/cf-workers/README.md:1— `cf-workers` is runnable (a `start` script in `REDACTED`) and neither `packages/multipart-parser/demos/cf-workers/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/multipart-parser/demos/deno/README.md:1— `deno` is runnable (a `start` script in `REDACTED`) and neither `packages/multipart-parser/demos/deno/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/multipart-parser/demos/node/README.md:1— `node` is runnable (a `start` script in `REDACTED`) and neither `packages/multipart-parser/demos/node/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
No app-layer HTTPS enforcement detected docs/shared/hmr/run.ts:26— `http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected docs/shared/server.ts:30— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:1133— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected template/server.ts:15— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 31 significant file(s) lose their only recent owner: packages/assets/src/lib/scripts/optimize-barrel-file-imports.ts, packages/fetch-router/src/lib/router.ts, packages/lazy-file/src/lib/lazy-file.ts, packages/terminal/src/lib/styles.ts, packages/data-table/src/lib/database/relations.ts, demos/bookstore/app/data/schema.ts, packages/data-table/src/lib/driver.ts, demos/social-auth/app/ui/styles.ts (+23 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 13 significant file(s) lose their only recent owner: demos/lazy-frames/app/actions/home.tsx, packages/ui/src/demos/animation/spring.demo.tsx, scripts/utils/remix-readmes.ts, packages/component/src/style/style.ts, demos/frames/app/actions/public/scroll-restoration.tsx, demos/lazy-frames/app/ui/document.tsx, demos/timeboxer/app/actions/auth/pages.tsx, demos/lazy-frames/app/actions/frames/controller.tsx (+5 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 6 significant file(s) lose their only recent owner: packages/assets/bench/runner.ts, packages/assets/src/lib/styles/resolve.ts, packages/assets/src/lib/scripts/emit.ts, packages/assets/src/lib/styles/emit.ts, packages/assets/bench/fixture.ts, packages/assets/src/lib/styles/transform.ts. Pair on, review, or document these before any departure.
Silent fallback default in catch packages/cookie/src/lib/cookie-signing.ts:29— `unsign` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/route-pattern/bench/src/href.bench.ts:26— `getBenchName` swallows every exception into `return 'bench'` — 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/test/src/lib/watcher.ts:6— `getFileModTime` swallows every exception into `return 0` — 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.
D21 · Naming Consistency· `itemID` spells `ID` where 108 names in the project spell it `Id` · ×2
`itemID` spells `ID` where 108 names in the project spell it `Id` packages/component/src/runtime/dom.ts:1602— 108 of 111 names in project remix-the-web spell the token `Id` (108 of 111; unit: names in project remix-the-web containing `Id`). Peers: AdminUsersIndexPageProps.currentUserId (demos/bookstore/app/actions/admin/users/index-page.tsx:11); BookstoreAuthSession.userId (demos/bookstore/app/middleware/auth.ts:18); CartItem.bookId (demos/bookstore/app/utils/cart.ts:2); cart.addToCart(bookId) (demos/bookstore/app/utils/cart.ts:23); cart.updateCartItem(bookId) (demos/bookstore/app/utils/cart.ts:41). Rename to `itemId`. [rule N6]
`itemID` spells `ID` where 108 names in the project spell it `Id` packages/component/src/runtime/dom.ts:1730— 108 of 111 names in project remix-the-web spell the token `Id` (108 of 111; unit: names in project remix-the-web containing `Id`). Peers: AdminUsersIndexPageProps.currentUserId (demos/bookstore/app/actions/admin/users/index-page.tsx:11); BookstoreAuthSession.userId (demos/bookstore/app/middleware/auth.ts:18); CartItem.bookId (demos/bookstore/app/utils/cart.ts:2); cart.addToCart(bookId) (demos/bookstore/app/utils/cart.ts:23); cart.updateCartItem(bookId) (demos/bookstore/app/utils/cart.ts:41). Rename to `itemId`. [rule N6]
R7 · Dead Code· Unused module-local declaration 'Tests' · ×2
Unused module-local declaration 'Tests' packages/fetch-router/src/lib/route-helpers/method.test.ts:129— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Unused module-local declaration 'Tests' packages/fetch-router/src/lib/route-map.test.ts:123— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies packages/auth-middleware/src/lib/require-auth.ts:57— 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.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 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 (55 single-owned of 403 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; 403 of the 932 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/assets/src/lib/files/cache.ts, packages/spa/src/lib/spa.ts, packages/node-tsx/src/lib/transform.ts, packages/assets/src/lib/virtual-store.ts, packages/multiple-import-maps-polyfill/src/lib/features.ts.
D21 · Naming Consistency· `classID` spells `ID` where 108 names in the project spell it `Id` · ×1
`classID` spells `ID` where 108 names in the project spell it `Id` packages/component/src/runtime/dom.ts:3156— 108 of 111 names in project remix-the-web spell the token `Id` (108 of 111; unit: names in project remix-the-web containing `Id`). Peers: AdminUsersIndexPageProps.currentUserId (demos/bookstore/app/actions/admin/users/index-page.tsx:11); BookstoreAuthSession.userId (demos/bookstore/app/middleware/auth.ts:18); CartItem.bookId (demos/bookstore/app/utils/cart.ts:2); cart.addToCart(bookId) (demos/bookstore/app/utils/cart.ts:23); cart.updateCartItem(bookId) (demos/bookstore/app/utils/cart.ts:41). Rename to `classId`. [rule N6]
D21 · Naming Consistency· `RoutePatternJSON` spells `JSON` where 62 names in the project spell it `Json` · ×1
`RoutePatternJSON` spells `JSON` where 62 names in the project spell it `Json` packages/route-pattern/src/lib/route-pattern.ts:39— 62 of 64 names in project remix-the-web spell the token `Json` (62 of 64; unit: names in project remix-the-web containing `Json`). Peers: schema.isJsonObject (demos/bookstore/app/data/schema.ts:326); controller.parseJsonRequest (demos/timeboxer/app/actions/schedules/controller.tsx:188); controller.wantsJson (demos/timeboxer/app/actions/schedules/controller.tsx:230); mock-fetch.loadFixtureJson (demos/unpkg/test/mock-fetch.ts:94); packages.discoverPackageSubpathOverviews(packageJson) (docs/site/scripts/generate/packages.ts:75). Rename to `RoutePatternJson`. [rule N6]
D21 · Naming Consistency· `toJSON` spells `JSON` where 62 names in the project spell it `Json` · ×1
`toJSON` spells `JSON` where 62 names in the project spell it `Json` packages/route-pattern/src/lib/route-pattern.ts:127— 62 of 64 names in project remix-the-web spell the token `Json` (62 of 64; unit: names in project remix-the-web containing `Json`). Peers: schema.isJsonObject (demos/bookstore/app/data/schema.ts:326); controller.parseJsonRequest (demos/timeboxer/app/actions/schedules/controller.tsx:188); controller.wantsJson (demos/timeboxer/app/actions/schedules/controller.tsx:230); mock-fetch.loadFixtureJson (demos/unpkg/test/mock-fetch.ts:94); packages.discoverPackageSubpathOverviews(packageJson) (docs/site/scripts/generate/packages.ts:75). Rename to `toJson`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 55 project(s) overshoot their size bounds, lowering Project Cohesion to 8.6/10. The most over is `packages/component` (18243 LoC, 238 module-visible types across 6 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 403 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 403 of the 932 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/route-pattern/src/lib/route-pattern/split.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file packages/route-pattern/src/lib/route-pattern/split.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body packages/terminal/src/lib/terminal.ts:139— `write` has an empty body — confirm it's an intentional no-op and not an unfinished method.
README/code drift packages/remix/src/route-pattern/README.md:418— packages/remix/src/route-pattern/README.md links to `./bench/`, but `packages/remix/src/route-pattern/bench` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST REDACTED:71— 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 911197 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:6— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code· Unused export 'resolveRedirectTarget' · ×1
Unused export 'resolveRedirectTarget' packages/auth/src/lib/utils.ts:59— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'fetchUnavailable' · ×1
Unused export 'fetchUnavailable' packages/cli/src/lib/errors.ts:234— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'remoteSkillDataMissing' · ×1
Unused export 'remoteSkillDataMissing' packages/cli/src/lib/errors.ts:300— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'isChildlessElement' · ×1
Unused export 'isChildlessElement' packages/component/src/runtime/core/attributes.ts:67— Nothing imports this binding — it is safe to review for removal.
Unused export 'resolve' packages/node-tsx/src/lib/loader.ts:51— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'encodePathnameVariable' · ×1
Unused export 'encodePathnameVariable' packages/route-pattern/src/lib/href.ts:360— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getPrComments' · ×1
Unused export 'getPrComments' scripts/utils/github.ts:354— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'createPrComment' · ×1
Unused export 'createPrComment' scripts/utils/github.ts:368— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'updatePrComment' · ×1
Unused export 'updatePrComment' scripts/utils/github.ts:383— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'deletePrComment' · ×1
Unused export 'deletePrComment' scripts/utils/github.ts:396— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'FingerprintOptions' · ×1
Unused module-local declaration 'FingerprintOptions' packages/assets/src/lib/asset-server.test.ts:33— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'SessionAuthContext' · ×1
Unused module-local declaration 'SessionAuthContext' packages/auth-middleware/src/lib/auth-types.test.ts:151— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'ignoreAbortedNavigation' · ×1
Unused module-local declaration 'ignoreAbortedNavigation' packages/component-hmr/test/hmr.test.e2e.tsx:2820— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'p' · ×1
Unused module-local declaration 'p' packages/multiple-import-maps-polyfill/test/fixtures/es-modules/es6-file.js:11— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_RequiredHrefArgs' · ×1
Unused module-local declaration '_RequiredHrefArgs' packages/route-pattern/src/lib/types/params.test.ts:8— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_MissingRequiredHrefArgs' · ×1
Unused module-local declaration '_MissingRequiredHrefArgs' packages/route-pattern/src/lib/types/params.test.ts:14— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_InvalidSearchParamValue' · ×1
Unused module-local declaration '_InvalidSearchParamValue' packages/route-pattern/src/lib/types/params.test.ts:31— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'isRecord' · ×1
Unused module-local declaration 'isRecord' scripts/validate-package-meta.ts:275— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene· Type-only dependency '@standard-schema/spec' in production deps · ×1
Type-only dependency '@standard-schema/spec' in production deps packages/data-schema/src/lib/schema.ts:1— Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene· Test-only dependency 'semver' in production deps · ×1
Test-only dependency 'semver' in production deps scripts/package.json:14— Only test files import it (first: scripts/utils/preview.test.ts:3) — move it to devDependencies.
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 5/6 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) reduce the strict null checking score — ~0.8 `!` null assertions per 1k TypeScript source lines — 93 assertion(s) across the 119041 source line(s) of the 594 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/multiple-import-maps-polyfill/src/lib/core.ts (16), REDACTED (15), docs/site/scripts/generate/documented-api.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Skipped (documented): arrow down/up selects first last when there is no selection packages/ui/src/select.test.tsx:585— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): aria-activedescendant is correctly on open packages/ui/src/select.test.tsx:586— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): todo: can mark tests as todo packages/test/src/test/framework.test.browser.ts:58— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): todo test packages/test/src/test/framework.test.ts:304— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): todo test packages/test/src/test/framework.test.ts:314— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): orphan packages/test/src/test/framework.test.ts:321— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): same name packages/test/src/test/framework.test.ts:375— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): same name packages/test/src/test/framework.test.ts:376— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): todo: can mark tests as todo packages/test/src/test/framework.test.ts:520— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): warns when render is called after component is removed packages/component/src/test/vdom.components.test.tsx:41— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): className packages/component/src/test/vdom.props.test.tsx:13— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): htmlFor packages/component/src/test/vdom.props.test.tsx:14— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): acceptCharset packages/component/src/test/vdom.props.test.tsx:15— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): httpEquiv packages/component/src/test/vdom.props.test.tsx:16— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): xlinkHref packages/component/src/test/vdom.props.test.tsx:17— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): xmlLang packages/component/src/test/vdom.props.test.tsx:18— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): xmlSpace packages/component/src/test/vdom.props.test.tsx:19— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): data-* packages/component/src/test/vdom.props.test.tsx:20— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): aria-* packages/component/src/test/vdom.props.test.tsx:21— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): style packages/component/src/test/vdom.props.test.tsx:25— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): value packages/component/src/test/vdom.props.test.tsx:26— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): defaultValue packages/component/src/test/vdom.props.test.tsx:27— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): checked packages/component/src/test/vdom.props.test.tsx:28— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): defaultChecked packages/component/src/test/vdom.props.test.tsx:29— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): disabled packages/component/src/test/vdom.props.test.tsx:30— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
doc comments repeat the names packages/component/src/runtime/render.ts:5— 0 of 101 documented parameters and 1 of 1505 summaries in `@remix-run/component` only repeat the member or parameter name (e.g. "Options for ." for `RenderOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/cookie/src/lib/cookie.ts:251— 0 of 7 documented parameters and 1 of 18 summaries in `@remix-run/cookie` only repeat the member or parameter name (e.g. "Creates a new cookie object." for `createCookie`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/data-table/src/lib/table.ts:504— 0 of 114 documented parameters and 1 of 277 summaries in `@remix-run/data-table` only repeat the member or parameter name (e.g. "Cardinality of a relation." for `RelationCardinality`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/fetch-proxy/src/lib/fetch-proxy.ts:19— 0 of 4 documented parameters and 1 of 8 summaries in `@remix-run/fetch-proxy` only repeat the member or parameter name (e.g. "Options for ." for `FetchProxyOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/fetch-router/src/lib/router.ts:357— 0 of 32 documented parameters and 1 of 95 summaries in `@remix-run/fetch-router` only repeat the member or parameter name (e.g. "Create a new router." for `createRouter`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/node-hmr/src/index.ts:104— 0 of 8 documented parameters and 1 of 63 summaries in `@remix-run/node-hmr` only repeat the member or parameter name (e.g. "Options for ." for `HmrReadyFetchOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/response/src/lib/file.ts:116— 1 of 18 documented parameters and 0 of 34 summaries in `@remix-run/response` only repeat the member or parameter name (e.g. "The request object" for `request`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/route-pattern/src/lib/match/punycode.ts:86— 1 of 35 documented parameters and 0 of 102 summaries in `@remix-run/route-pattern` only repeat the member or parameter name (e.g. "The current delta." for `delta`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/session/src/lib/session.ts:179— 0 of 17 documented parameters and 1 of 25 summaries in `@remix-run/session` only repeat the member or parameter name (e.g. "Create a new session." for `createSession`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names scripts/utils/github.ts:294— 0 of 0 documented parameters and 5 of 60 summaries in `remix-the-scripts` only repeat the member or parameter name (e.g. "Create a new PR" for `createPr`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 83 file(s) — `demos/i18n/app/i18n/config.ts`, `demos/i18n/app/i18n/locales/ar.ts`, `demos/i18n/app/i18n/locales/es.ts`, `demos/i18n/app/i18n/locales/fr.ts`, `demos/i18n/app/i18n/locales/ja.ts`, … (+78 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 01a1b725-8cab-7c5f-b457-eed2eadf3c1a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 177 · Warnings: 843 · Recommendations: 147 · Info: 41 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 07-11-2026 @ 17:54 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.