Public report of ionic-team/ionic-framework, published 14 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.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 13:28 UTC · Survey ID cd_2db78735b4744f50951ff74fef7b301d
ionic-team/ionic-framework
Measured 14 November 2026, 13:26 UTC, at code version a79e1a1
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 medium codebase: 71,618 lines of product code in 14 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Production Readiness, 42
Findings by how serious they are
60 critical956 serious232 minor
6 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
14 November 2026, 13:26 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 ▸
76of 76 dimensions measured by tools.
1200of 1248 findings point to an exact file and line, so you can open each one in the code. The other 48 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 71,618 lines of product code in 14 projects.
ionic-team/ionic-framework is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no logging, tracing or health checks in the code, and it has uses of packages that aren't listed. It scores 52 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first steps are adopting a logging library and tidying the declared packages, each worth about 6 points. Raising Production Readiness to 70 would lift the score to about 60.
Twelve pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Nine secrets can leak from the build pipeline, and eight known security holes in the packages the code depends on can be used by attackers. Passing outside input through environment variables, limiting each secret to its own step and updating the vulnerable packages would close these risks. The password or key in the code's history needs replacing, with the old one switched off. The nine uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 71,618 lines, about €170,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 52 to about 60.
Code composition: what the lines of code are
Product code 40%Tests 60%
Rebuild cost: about €170,000 · Estimate
Cost to rebuild
€57,000 to €280,000, for 943 to 2,991 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 52. 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
Medium: 71,618 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
Adopt pino (or winston) and log at meaningful points in the services you run.
Raises the score by about 6 points · Medium effort · Observability
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with hooks.spec.tsx, overlay-hook-types.spec.tsx.
Raises the score by about 3 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €170,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 42 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Adopt pino (or winston) and log at meaningful points in the services you run. Of all the actions in this report, it raises the score most for the work it takes: about 6 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 7.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 6% on every change. The history of the code shows how much it changes: about 25,992 lines over the last 90 days, which is about 105,412 lines a year. At that pace, the extra work comes to an estimated 6.5 to 38.9 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.
477 modules, with 374 dependencies between them. 2 loops run through 5 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 437 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.
core.src.components.menu.menu-interface uses core.src.utils.animation.animation-interface, so a change to core.src.utils.animation.animation-interface can break core.src.components.menu.menu-interface, while a change to core.src.components.menu.menu-interface can't break core.src.utils.animation.animation-interface.
Position
Below the diagonal: core.src.components.menu.menu-interface uses a module listed above it, which is the healthy direction.
core.src.global.config uses core.src.utils.config, so a change to core.src.utils.config can break core.src.global.config, while a change to core.src.global.config can't break core.src.utils.config.
Position
Below the diagonal: core.src.global.config uses a module listed above it, which is the healthy direction.
packages.migrate.src.ast uses packages.migrate.src.types, so a change to packages.migrate.src.types can break packages.migrate.src.ast, while a change to packages.migrate.src.ast can't break packages.migrate.src.types.
Position
Below the diagonal: packages.migrate.src.ast uses a module listed above it, which is the healthy direction.
18→27 packages.react.src.components.react-component-lib.interfaces uses core.src.utils.overlays-interfacepart of a loop✕
Connections
1 pair of types, where a type in packages.react.src.components.react-component-lib.interfaces uses a type in core.src.utils.overlays-interface.
packages.react.src.components.react-component-lib.interfaces uses core.src.utils.overlays-interface, so a change to core.src.utils.overlays-interface can break packages.react.src.components.react-component-lib.interfaces, while a change to packages.react.src.components.react-component-lib.interfaces can't break core.src.utils.overlays-interface.
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.react.src.models.RouteInfo uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break packages.react.src.models.RouteInfo, while a change to packages.react.src.models.RouteInfo can't break core.src.components.router.utils.interface.
Position
Below the diagonal: packages.react.src.models.RouteInfo uses a module listed above it, which is the healthy direction.
packages.react.src.models.RouteInfo uses packages.migrate.src.migrations.v9.react-router-6-routes, so a change to packages.migrate.src.migrations.v9.react-router-6-routes can break packages.react.src.models.RouteInfo, while a change to packages.react.src.models.RouteInfo can't break packages.migrate.src.migrations.v9.react-router-6-routes.
Position
Below the diagonal: packages.react.src.models.RouteInfo uses a module listed above it, which is the healthy direction.
packages.vue-router.src.types uses packages.migrate.src.migrations.v9.react-router-6-routes, so a change to packages.migrate.src.migrations.v9.react-router-6-routes can break packages.vue-router.src.types, while a change to packages.vue-router.src.types can't break packages.migrate.src.migrations.v9.react-router-6-routes.
Position
Below the diagonal: packages.vue-router.src.types uses a module listed above it, which is the healthy direction.
core.src.components.menu.menu uses core.src.utils.animation.animation-interface, so a change to core.src.utils.animation.animation-interface can break core.src.components.menu.menu, while a change to core.src.components.menu.menu can't break core.src.utils.animation.animation-interface.
Position
Below the diagonal: core.src.components.menu.menu uses a module listed above it, which is the healthy direction.
core.src.components.menu.menu uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.menu.menu, while a change to core.src.components.menu.menu can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.menu.menu uses a module listed above it, which is the healthy direction.
core.src.components.menu.menu uses core.src.components.menu.menu-interface, so a change to core.src.components.menu.menu-interface can break core.src.components.menu.menu, while a change to core.src.components.menu.menu can't break core.src.components.menu.menu-interface.
Position
Below the diagonal: core.src.components.menu.menu uses a module listed above it, which is the healthy direction.
core.src.components.menu.menu uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.menu.menu, while a change to core.src.components.menu.menu can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.menu.menu uses a module listed above it, which is the healthy direction.
core.src.components.nav.nav uses core.src.components.nav.nav-interface, so a change to core.src.components.nav.nav-interface can break core.src.components.nav.nav, while a change to core.src.components.nav.nav can't break core.src.components.nav.nav-interface.
Position
Below the diagonal: core.src.components.nav.nav uses a module listed above it, which is the healthy direction.
core.src.components.nav.nav uses core.src.utils.animation.animation-interface, so a change to core.src.utils.animation.animation-interface can break core.src.components.nav.nav, while a change to core.src.components.nav.nav can't break core.src.utils.animation.animation-interface.
Position
Below the diagonal: core.src.components.nav.nav uses a module listed above it, which is the healthy direction.
core.src.components.nav.nav uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.nav.nav, while a change to core.src.components.nav.nav can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.nav.nav uses a module listed above it, which is the healthy direction.
core.src.components.nav.nav uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.nav.nav, while a change to core.src.components.nav.nav can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.nav.nav uses a module listed above it, which is the healthy direction.
core.src.components.range.range uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.range.range, while a change to core.src.components.range.range can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.range.range uses a module listed above it, which is the healthy direction.
core.src.components.range.range uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.range.range, while a change to core.src.components.range.range can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.range.range uses a module listed above it, which is the healthy direction.
core.src.components.reorder-group.reorder-group uses core.src.utils.element-interface, so a change to core.src.utils.element-interface can break core.src.components.reorder-group.reorder-group, while a change to core.src.components.reorder-group.reorder-group can't break core.src.utils.element-interface.
Position
Below the diagonal: core.src.components.reorder-group.reorder-group uses a module listed above it, which is the healthy direction.
core.src.components.reorder-group.reorder-group uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.reorder-group.reorder-group, while a change to core.src.components.reorder-group.reorder-group can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.reorder-group.reorder-group uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in core.src.components.reorder-group.reorder-group uses a type in packages.react.src.components.react-component-lib.interfaces.
core.src.components.reorder-group.reorder-group uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.reorder-group.reorder-group, while a change to core.src.components.reorder-group.reorder-group can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.reorder-group.reorder-group uses a module listed above it, which is the healthy direction.
core.src.components.router-outlet.router-outlet uses core.src.components.nav.nav-interface, so a change to core.src.components.nav.nav-interface can break core.src.components.router-outlet.router-outlet, while a change to core.src.components.router-outlet.router-outlet can't break core.src.components.nav.nav-interface.
Position
Below the diagonal: core.src.components.router-outlet.router-outlet uses a module listed above it, which is the healthy direction.
core.src.components.router-outlet.router-outlet uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break core.src.components.router-outlet.router-outlet, while a change to core.src.components.router-outlet.router-outlet can't break core.src.components.router.utils.interface.
Position
Below the diagonal: core.src.components.router-outlet.router-outlet uses a module listed above it, which is the healthy direction.
core.src.components.router-outlet.router-outlet uses core.src.utils.animation.animation-interface, so a change to core.src.utils.animation.animation-interface can break core.src.components.router-outlet.router-outlet, while a change to core.src.components.router-outlet.router-outlet can't break core.src.utils.animation.animation-interface.
Position
Below the diagonal: core.src.components.router-outlet.router-outlet uses a module listed above it, which is the healthy direction.
core.src.components.router-outlet.router-outlet uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.router-outlet.router-outlet, while a change to core.src.components.router-outlet.router-outlet can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.router-outlet.router-outlet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in core.src.components.router-outlet.router-outlet uses a type in packages.react.src.components.react-component-lib.interfaces.
core.src.components.router-outlet.router-outlet uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.router-outlet.router-outlet, while a change to core.src.components.router-outlet.router-outlet can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.router-outlet.router-outlet uses a module listed above it, which is the healthy direction.
core.src.components.router.router uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break core.src.components.router.router, while a change to core.src.components.router.router can't break core.src.components.router.utils.interface.
Position
Below the diagonal: core.src.components.router.router uses a module listed above it, which is the healthy direction.
core.src.components.router.router uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.router.router, while a change to core.src.components.router.router can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.router.router uses a module listed above it, which is the healthy direction.
core.src.utils.overlays-interface uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.utils.overlays-interface, while a change to core.src.utils.overlays-interface can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.utils.overlays-interface uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter uses packages.react.src.routing.ViewItem, so a change to packages.react.src.routing.ViewItem can break packages.react-router.src.ReactRouter, while a change to packages.react-router.src.ReactRouter can't break packages.react.src.routing.ViewItem.
Position
Below the diagonal: packages.react-router.src.ReactRouter uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter uses packages.react.src.models.RouteInfo, so a change to packages.react.src.models.RouteInfo can break packages.react-router.src.ReactRouter, while a change to packages.react-router.src.ReactRouter can't break packages.react.src.models.RouteInfo.
Position
Below the diagonal: packages.react-router.src.ReactRouter uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter uses packages.vue-router.src.types, so a change to packages.vue-router.src.types can break packages.react-router.src.ReactRouter, while a change to packages.react-router.src.ReactRouter can't break packages.vue-router.src.types.
Position
Below the diagonal: packages.react-router.src.ReactRouter uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter.utils uses packages.react.src.routing.ViewItem, so a change to packages.react.src.routing.ViewItem can break packages.react-router.src.ReactRouter.utils, while a change to packages.react-router.src.ReactRouter.utils can't break packages.react.src.routing.ViewItem.
Position
Below the diagonal: packages.react-router.src.ReactRouter.utils uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter.utils uses packages.react.src.models.RouteInfo, so a change to packages.react.src.models.RouteInfo can break packages.react-router.src.ReactRouter.utils, while a change to packages.react-router.src.ReactRouter.utils can't break packages.react.src.models.RouteInfo.
Position
Below the diagonal: packages.react-router.src.ReactRouter.utils uses a module listed above it, which is the healthy direction.
packages.react-router.src.ReactRouter.utils uses packages.vue-router.src.types, so a change to packages.vue-router.src.types can break packages.react-router.src.ReactRouter.utils, while a change to packages.react-router.src.ReactRouter.utils can't break packages.vue-router.src.types.
Position
Below the diagonal: packages.react-router.src.ReactRouter.utils uses a module listed above it, which is the healthy direction.
packages.react.src.routing.NavManager uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break packages.react.src.routing.NavManager, while a change to packages.react.src.routing.NavManager can't break core.src.components.router.utils.interface.
Position
Below the diagonal: packages.react.src.routing.NavManager uses a module listed above it, which is the healthy direction.
packages.react.src.routing.NavManager uses packages.migrate.src.migrations.v9.react-router-6-routes, so a change to packages.migrate.src.migrations.v9.react-router-6-routes can break packages.react.src.routing.NavManager, while a change to packages.react.src.routing.NavManager can't break packages.migrate.src.migrations.v9.react-router-6-routes.
Position
Below the diagonal: packages.react.src.routing.NavManager uses a module listed above it, which is the healthy direction.
packages.react.src.routing.NavManager uses packages.react.src.models.RouteInfo, so a change to packages.react.src.models.RouteInfo can break packages.react.src.routing.NavManager, while a change to packages.react.src.routing.NavManager can't break packages.react.src.models.RouteInfo.
Position
Below the diagonal: packages.react.src.routing.NavManager uses a module listed above it, which is the healthy direction.
packages.vue.src.hooks uses packages.migrate.src.migrations.v9.react-router-6-routes, so a change to packages.migrate.src.migrations.v9.react-router-6-routes can break packages.vue.src.hooks, while a change to packages.vue.src.hooks can't break packages.migrate.src.migrations.v9.react-router-6-routes.
Position
Below the diagonal: packages.vue.src.hooks uses a module listed above it, which is the healthy direction.
packages.vue.src.hooks uses packages.vue-router.src.types, so a change to packages.vue-router.src.types can break packages.vue.src.hooks, while a change to packages.vue.src.hooks can't break packages.vue-router.src.types.
Position
Below the diagonal: packages.vue.src.hooks uses a module listed above it, which is the healthy direction.
core.src.components.action-sheet.action-sheet uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.action-sheet.action-sheet, while a change to core.src.components.action-sheet.action-sheet can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.action-sheet.action-sheet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in core.src.components.action-sheet.action-sheet uses a type in packages.react.src.components.react-component-lib.interfaces.
core.src.components.action-sheet.action-sheet uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.action-sheet.action-sheet, while a change to core.src.components.action-sheet.action-sheet can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.action-sheet.action-sheet uses a module listed above it, which is the healthy direction.
core.src.components.action-sheet.action-sheet uses core.src.utils.overlays-interface, so a change to core.src.utils.overlays-interface can break core.src.components.action-sheet.action-sheet, while a change to core.src.components.action-sheet.action-sheet can't break core.src.utils.overlays-interface.
Position
Below the diagonal: core.src.components.action-sheet.action-sheet uses a module listed above it, which is the healthy direction.
core.src.components.alert.alert uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.alert.alert, while a change to core.src.components.alert.alert can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.alert.alert uses a module listed above it, which is the healthy direction.
core.src.components.alert.alert uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.alert.alert, while a change to core.src.components.alert.alert can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.alert.alert uses a module listed above it, which is the healthy direction.
core.src.components.alert.alert uses core.src.utils.overlays-interface, so a change to core.src.utils.overlays-interface can break core.src.components.alert.alert, while a change to core.src.components.alert.alert can't break core.src.utils.overlays-interface.
Position
Below the diagonal: core.src.components.alert.alert uses a module listed above it, which is the healthy direction.
core.src.components.modal.modal uses core.src.components.modal.modal-interface, so a change to core.src.components.modal.modal-interface can break core.src.components.modal.modal, while a change to core.src.components.modal.modal can't break core.src.components.modal.modal-interface.
Position
Below the diagonal: core.src.components.modal.modal uses a module listed above it, which is the healthy direction.
core.src.components.modal.modal uses core.src.utils.animation.animation-interface, so a change to core.src.utils.animation.animation-interface can break core.src.components.modal.modal, while a change to core.src.components.modal.modal can't break core.src.utils.animation.animation-interface.
Position
Below the diagonal: core.src.components.modal.modal uses a module listed above it, which is the healthy direction.
core.src.components.modal.modal uses core.src.utils.gesture, so a change to core.src.utils.gesture can break core.src.components.modal.modal, while a change to core.src.components.modal.modal can't break core.src.utils.gesture.
Position
Below the diagonal: core.src.components.modal.modal uses a module listed above it, which is the healthy direction.
core.src.components.modal.modal uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.components.modal.modal, while a change to core.src.components.modal.modal can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.components.modal.modal uses a module listed above it, which is the healthy direction.
core.src.components.modal.modal uses core.src.utils.overlays-interface, so a change to core.src.utils.overlays-interface can break core.src.components.modal.modal, while a change to core.src.components.modal.modal can't break core.src.utils.overlays-interface.
Position
Below the diagonal: core.src.components.modal.modal uses a module listed above it, which is the healthy direction.
core.src.utils uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break core.src.utils, while a change to core.src.utils can't break core.src.components.router.utils.interface.
Position
Below the diagonal: core.src.utils uses a module listed above it, which is the healthy direction.
core.src.utils uses core.src.utils.config, so a change to core.src.utils.config can break core.src.utils, while a change to core.src.utils can't break core.src.utils.config.
Position
Below the diagonal: core.src.utils uses a module listed above it, which is the healthy direction.
core.src.utils uses core.src.components.menu.menu-interface, so a change to core.src.components.menu.menu-interface can break core.src.utils, while a change to core.src.utils can't break core.src.components.menu.menu-interface.
Position
Below the diagonal: core.src.utils uses a module listed above it, which is the healthy direction.
core.src.utils uses packages.react.src.components.react-component-lib.interfaces, so a change to packages.react.src.components.react-component-lib.interfaces can break core.src.utils, while a change to core.src.utils can't break packages.react.src.components.react-component-lib.interfaces.
Position
Below the diagonal: core.src.utils uses a module listed above it, which is the healthy direction.
core.src.utils uses core.src.utils.overlays-interface, so a change to core.src.utils.overlays-interface can break core.src.utils, while a change to core.src.utils can't break core.src.utils.overlays-interface.
Position
Below the diagonal: core.src.utils uses a module listed above it, which is the healthy direction.
packages.angular.src.common.providers.nav-controller uses core.src.components.nav.nav-interface, so a change to core.src.components.nav.nav-interface can break packages.angular.src.common.providers.nav-controller, while a change to packages.angular.src.common.providers.nav-controller can't break core.src.components.nav.nav-interface.
Position
Below the diagonal: packages.angular.src.common.providers.nav-controller uses a module listed above it, which is the healthy direction.
packages.angular.src.common.providers.nav-controller uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break packages.angular.src.common.providers.nav-controller, while a change to packages.angular.src.common.providers.nav-controller can't break core.src.components.router.utils.interface.
Position
Below the diagonal: packages.angular.src.common.providers.nav-controller uses a module listed above it, which is the healthy direction.
packages.angular.src.common.providers.nav-controller uses core.src.components.router.router, so a change to core.src.components.router.router can break packages.angular.src.common.providers.nav-controller, while a change to packages.angular.src.common.providers.nav-controller can't break core.src.components.router.router.
Position
Below the diagonal: packages.angular.src.common.providers.nav-controller uses a module listed above it, which is the healthy direction.
36→39 packages.angular.src.common.providers.nav-controller uses packages.angular.src.common.directives.navigation.router-outletpart of a loop✕
Connections
1 pair of types, where a type in packages.angular.src.common.providers.nav-controller uses a type in packages.angular.src.common.directives.navigation.router-outlet.
packages.angular.src.common.providers.nav-controller uses packages.angular.src.common.directives.navigation.router-outlet, so a change to packages.angular.src.common.directives.navigation.router-outlet can break packages.angular.src.common.providers.nav-controller, while a change to packages.angular.src.common.providers.nav-controller can't break packages.angular.src.common.directives.navigation.router-outlet.
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.vue-router.src uses packages.migrate.src.migrations.v9.react-router-6-routes, so a change to packages.migrate.src.migrations.v9.react-router-6-routes can break packages.vue-router.src, while a change to packages.vue-router.src can't break packages.migrate.src.migrations.v9.react-router-6-routes.
Position
Below the diagonal: packages.vue-router.src uses a module listed above it, which is the healthy direction.
packages.vue-router.src uses packages.react.src.routing.ViewItem, so a change to packages.react.src.routing.ViewItem can break packages.vue-router.src, while a change to packages.vue-router.src can't break packages.react.src.routing.ViewItem.
Position
Below the diagonal: packages.vue-router.src uses a module listed above it, which is the healthy direction.
packages.vue-router.src uses packages.react.src.models.RouteInfo, so a change to packages.react.src.models.RouteInfo can break packages.vue-router.src, while a change to packages.vue-router.src can't break packages.react.src.models.RouteInfo.
Position
Below the diagonal: packages.vue-router.src uses a module listed above it, which is the healthy direction.
packages.vue-router.src uses packages.vue-router.src.types, so a change to packages.vue-router.src.types can break packages.vue-router.src, while a change to packages.vue-router.src can't break packages.vue-router.src.types.
Position
Below the diagonal: packages.vue-router.src uses a module listed above it, which is the healthy direction.
packages.vue-router.src uses core.src.components.router.router, so a change to core.src.components.router.router can break packages.vue-router.src, while a change to packages.vue-router.src can't break core.src.components.router.router.
Position
Below the diagonal: packages.vue-router.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.angular.src.common.directives.navigation.stack-controller uses a type in core.src.components.router.utils.interface.
packages.angular.src.common.directives.navigation.stack-controller uses core.src.components.router.utils.interface, so a change to core.src.components.router.utils.interface can break packages.angular.src.common.directives.navigation.stack-controller, while a change to packages.angular.src.common.directives.navigation.stack-controller can't break core.src.components.router.utils.interface.
Position
Below the diagonal: packages.angular.src.common.directives.navigation.stack-controller uses a module listed above it, which is the healthy direction.
packages.angular.src.common.directives.navigation.stack-controller uses core.src.components.router.router, so a change to core.src.components.router.router can break packages.angular.src.common.directives.navigation.stack-controller, while a change to packages.angular.src.common.directives.navigation.stack-controller can't break core.src.components.router.router.
Position
Below the diagonal: packages.angular.src.common.directives.navigation.stack-controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.angular.src.common.directives.navigation.stack-controller uses a type in packages.angular.src.common.providers.nav-controller.
packages.angular.src.common.directives.navigation.stack-controller uses packages.angular.src.common.providers.nav-controller, so a change to packages.angular.src.common.providers.nav-controller can break packages.angular.src.common.directives.navigation.stack-controller, while a change to packages.angular.src.common.directives.navigation.stack-controller can't break packages.angular.src.common.providers.nav-controller.
Position
Below the diagonal: packages.angular.src.common.directives.navigation.stack-controller uses a module listed above it, which is the healthy direction.
packages.angular.src.common.directives.navigation.router-outlet uses core.src.components.router.router, so a change to core.src.components.router.router can break packages.angular.src.common.directives.navigation.router-outlet, while a change to packages.angular.src.common.directives.navigation.router-outlet can't break core.src.components.router.router.
Position
Below the diagonal: packages.angular.src.common.directives.navigation.router-outlet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.angular.src.common.directives.navigation.router-outlet uses a type in packages.angular.src.common.directives.navigation.stack-controller.
packages.angular.src.common.directives.navigation.router-outlet uses packages.angular.src.common.directives.navigation.stack-controller, so a change to packages.angular.src.common.directives.navigation.stack-controller can break packages.angular.src.common.directives.navigation.router-outlet, while a change to packages.angular.src.common.directives.navigation.router-outlet can't break packages.angular.src.common.directives.navigation.stack-controller.
Position
Below the diagonal: packages.angular.src.common.directives.navigation.router-outlet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.react.src.components.navigation.IonTabs uses a type in packages.angular.src.common.directives.navigation.router-outlet.
packages.react.src.components.navigation.IonTabs uses packages.angular.src.common.directives.navigation.router-outlet, so a change to packages.angular.src.common.directives.navigation.router-outlet can break packages.react.src.components.navigation.IonTabs, while a change to packages.react.src.components.navigation.IonTabs can't break packages.angular.src.common.directives.navigation.router-outlet.
Position
Below the diagonal: packages.react.src.components.navigation.IonTabs uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
48
High / Critical
A05:2025 — Injection
24
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
A02:2025 — Security Misconfiguration
1
Medium
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Enable Dependabot/Renovate or a dependency-review gate.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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 — 60
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 — 956
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 — 232
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
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 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 76 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, 1200 of 1248 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. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — 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 declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their 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.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/vue/types/proxies.d.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 145 further occurrence(s) are not listed individually; the score already reflects all 185.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 63 further occurrence(s) are not listed individually; the score already reflects all 103.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 56 further occurrence(s) are not listed individually; the score already reflects all 96.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala 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: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
62 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was animation.createAnimation at 86. A further 2 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 Refresher.setupiOSNativeRefresher at 21 — they are counted neither in the figure above nor in this dimension's score.
+ 56 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with animation.createAnimation (cyclomatic 86), ReactRouterViewStack.renderViewItem (cyclomatic 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 81 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 60 down to 60 or less in Cognitive Complexity — start with animation.createAnimation (cognitive 107), StackManager.transitionPage (cognitive 102), ios.transition.iosTransitionAnimation (cognitive 93). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 5.3 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 13 FunctionTooLong finding(s) in God Classes — start with index.ts (2), animation.ts, IonRouter.tsx. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 10 FileTooLong finding(s) in God Classes — start with datetime.tsx, StackManager.tsx, select.tsx. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with datetime.tsx, modal.tsx, nav.tsx. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.4 / 10Stronggated by 1 serious finding✓ 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.
14 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 9 of the 14 (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: @ionic/core
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with input-password-toggle.tsx, inputs.component.ts, providers.component.ts. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d6_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 the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Resolve the 2 Low coverage finding(s) in Code Coverage — start with NavContext.ts, LocationHistory.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.0 / 10Adequategated by 2 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.
21 skipped (1 with a documented reason), 269 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4404 tests.
No assertions (empty test): should pass · ×2packages/react/src/hooks/__tests__/hooks.spec.tsx:5
No assertions: should correctly go back to Tab 1 · ×267packages/vue/test/base/tests/e2e/specs/hbb.cy.js:2
Skipped test: should correctly go back to the root tab after switching pages · ×20packages/vue/test/base/tests/e2e/specs/hbb.cy.js:63
Fixed-sleep synchronisation: should make a later setActive wait for the in-flight attachcore/src/components/tab/test/tab.spec.ts:42
Mock-dominated test: should fire lifecycle events on inner tab page · ×3packages/vue/test/base/tests/unit/lifecycle.spec.ts:101
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with hooks.spec.tsx, overlay-hook-types.spec.tsx. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 267 No assertions finding(s) in Test Quality — start with routing.cy.js (54), tabs.cy.js (27), datetime.e2e.ts (27). — One of this dimension's main actionable groups (267 warning-level).
Resolve the 20 Skipped test finding(s) in Test Quality — start with tabs.cy.js (3), select-popover.e2e.ts (3), select-modal.e2e.ts (3). — One of this dimension's main actionable groups (20 warning-level).
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 / 10Adequategated by 2 critical findings✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in packages/migrate/ (308 tests); jest via `npm ci --ignore-scripts` in packages/react/ (83 tests); vitest via `npm ci --ignore-scripts` in packages/react/test/apps/react18/ (0 tests); vitest via `npm ci --ignore-scripts` in packages/react/test/apps/react19/ (0 tests)): measured (0 flaky).
Test suite declares a test script but contains no test files: packages/react/test/apps/react18/ · ×2
What to do
Resolve the 2 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Top hotspots: packages/react-router/src/ReactRouter/StackManager.tsx (5×49=245); packages/vue-router/src/router.ts (4×52=208); packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx (3×64=192) Repeated repair below the complexity floor: core/src/components/select/select.tsx (4 of 4 changes were fixes); core/src/utils/helpers.ts (4 of 4 changes were fixes); core/src/components/button/button.tsx (3 of 3 changes were fixes)
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with StackManager.tsx, router.ts, ReactRouterViewStack.tsx. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with select.tsx, helpers.ts, button.tsx. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx. Counted over 210 of the 543 production source files in this repository: 332 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
162 deducted task-comment markers across 70244 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment repeated across 13 filespackages/react/src/framework-delegate.tsx:6
TodoComment repeated across 28 filescore/src/utils/config.ts:236
TodoComment repeated across 11 filescore/src/utils/focus-visible.ts:49
What to do
Resolve the 108 TodoComment finding(s) in Explicit Debt — start with select.e2e.ts (13), index.ts (5), select-popover.tsx (5). — One of this dimension's main actionable groups (108 warning-level).
Resolve the 1 TodoComment repeated across 13 files finding(s) in Explicit Debt — start with framework-delegate.tsx. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TodoComment repeated across 28 files finding(s) in Explicit Debt — start with config.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 40 document(s) read across 13 unit(s).
Documentation: no build, run or usage example · ×3packages/angular-server/readme.md:1
What to do
Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (2), readme.md. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 22 declarations measured against a convention their peers follow.
`configFromURL` spells `URL` where 20 names in the project spell it `Url`core/src/global/config.ts:57
`openURL` spells `URL` where 20 names in the project spell it `Url`core/src/utils/theme.ts:40
What to do
Resolve the 1 `configFromURL` spells `URL` where 20 names in the project spell it… finding(s) in Naming Consistency — start with config.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `openURL` spells `URL` where 20 names in the project spell it `Url` finding(s) in Naming Consistency — start with theme.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 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 · ×4packages/angular/schematics/add/index.ts:47
What to do
Resolve the 53 redundant comment finding(s) in Comment Value — start with datetime.e2e.ts (4), form.spec.ts (4), nested-tabs-relative-links.cy.js (4). — One of this dimension's main actionable groups (53 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 10 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
16 % of calls cross a namespace and 1 % go through an interface, but 62 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
24 finding(s): 0 critical, 21 high, 3 medium, 0 low. semgrep hit a parse error in 3 file(s) — `core/scripts/vercel-build.sh` (line 78), `packages/vue/types/proxies.d.ts` (line 2, line 3, line 4, …), `scripts/release-patch.sh` (line 256, line 384) — 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 11 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
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
77 of 211 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/utils/transition/ios.transition.ts. Counted over 211 of the 543 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 74 Orphaned file finding(s) in Knowledge Freshness — start with index.ts (6), utils.ts (3), createOverlayComponent.tsx (2). — One of this dimension's main actionable groups (74 recommendation-level).
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with ios.transition.ts, animation.ts, data.ts. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 7 Change coupling finding(s) in Change Coupling — start with nav.tsx (2), modal-interface.ts, dom.ts. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with picker.tsx, loading.tsx. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 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.
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 2 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.
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text 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 & labels10.0 / 10Exemplary○ Nothing flagged
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.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — core/src/components/accordion/accordion.tsx:519, core/src/components/popover/popover.tsx:798
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — core/src/components/checkbox/checkbox.tsx:398, core/src/components/toggle/toggle.tsx:524
This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. — core/src/components/picker-column-option/picker-column-option.tsx:127
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. (×6) — core/src/components/action-sheet/action-sheet.tsx:660, core/src/components/action-sheet/action-sheet.tsx:710, core/src/components/alert/alert.tsx:916, …
aria-labelledby is present but empty, so it references no element and the relationship is lost. Point it at the id(s) of the target element, or remove it. — core/src/components/input/input.tsx:759
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.
`[ion-last-focus]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/css/core.scss:462
`:host(:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×5) — core/src/components/toggle/toggle.scss:75, core/src/components/segment-button/segment-button.scss:171, core/src/components/radio/radio.scss:57, …
`:host` 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. (×6) — core/src/components/toast/toast.scss:52, core/src/components/tab-button/tab-button.scss:31, core/src/components/popover/popover.scss:40, …
`.toast-button` 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. — core/src/components/toast/toast.scss:168
`.native-textarea` 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. — core/src/components/textarea/textarea.scss:134
`.button-native` 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. (×6) — core/src/components/tab-button/tab-button.scss:58, core/src/components/segment-button/segment-button.scss:108, core/src/components/menu-button/menu-button.scss:65, …
`.searchbar-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/components/searchbar/searchbar.scss:81
`.searchbar-cancel-button` 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. — core/src/components/searchbar/searchbar.scss:117
`.searchbar-clear-button` 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. — core/src/components/searchbar/searchbar.scss:143
`.range-knob-handle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/components/range/range.scss:97
`.picker-column-option-button` 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. — core/src/components/picker-column-option/picker-column-option.scss:16
`.assistive-focusable:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/components/picker-column/picker-column.scss:37
`.picker-opts` 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. — core/src/components/picker-column/picker-column.scss:62
`.picker-item-empty` 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. — core/src/components/picker-column/picker-column.scss:97
`:host(:focus) .picker-opts` 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. — core/src/components/picker-column/picker-column.scss:186
`.modal-wrapper` 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. — core/src/components/modal/modal.scss:105
`.item-native` 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. — core/src/components/item/item.scss:224
`:host(.has-focus) .native-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/components/input-otp/input-otp.scss:225
`.native-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/components/input/input.scss:125
`.input-clear-icon` 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. — core/src/components/input/input.scss:212
`:host .calendar-body` 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. — core/src/components/datetime/datetime.scss:276
`.calendar-day` 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. — core/src/components/datetime/datetime.scss:354
`.calendar-month-year-toggle` 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. — core/src/components/datetime/datetime.scss:463
`.card-native` 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. — core/src/components/card/card.scss:68
`.breadcrumb-native` 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. — core/src/components/breadcrumb/breadcrumb.scss:39
`.breadcrumbs-collapsed-indicator` 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. — core/src/components/breadcrumb/breadcrumb.scss:150
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`MenuControllerI` declares 17 required operations: `registerAnimation`, `get`, `getMenus`, `getOpen`, `isEnabled`, `swipeGesture`, `isAnimating`, `isOpen`, `enable`, `toggle`, `close`, `open`, `_getOpenSync`, `_createAnimation`, `_register`, `_unregister`, `_setOpen`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/src/components/menu/menu-interface.ts:28
`Animation` declares 44 required operations: `play`, `pause`, `stop`, `destroy`, `progressStart`, `progressStep`, `progressEnd`, `from`, `to`, `fromTo`, `keyframes`, `addAnimation`, `addElement`, `iterations`, `fill`, `direction`, `duration`, `easing`, `delay`, `getKeyframes`, `getDirection`, `getFill`, `getDelay`, `getIterations`, `getEasing`, `getDuration`, `getWebAnimations`, `afterAddRead`, `afterAddWrite`, `afterClearStyles`, `afterStyles`, `afterAddClass`, `afterRemoveClass`, `beforeAddRead`, `beforeAddWrite`, `beforeClearStyles`, `beforeStyles`, `beforeAddClass`, `beforeRemoveClass`, `onFinish`, and 4 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/src/utils/animation/animation-interface.ts:3
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition. (×4) — core/src/components/select/select.tsx:838, core/src/components/select/select.tsx:864, core/src/components/select/select.tsx:911, …
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/vue/scripts/build-vetur.js:35
`install` 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/vue/src/ionic-vue.ts:6
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×20) — core/src/components/accordion/test/a11y/accordion.e2e.ts:7, core/src/components/fab/test/custom-size/fab.e2e.ts:10, core/src/components/picker-column/test/basic/picker-column.e2e.ts:40, …
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×6) — packages/angular/src/common/utils/proxy.ts:3, packages/angular/src/lazy/directives/angular-component-lib/boolean-attribute.ts:1, packages/angular/src/lazy/directives/angular-component-lib/utils.ts:1, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 543 JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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.
`package.json` 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`. — package.json:4
What to do
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 · 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.
Do you agree with this assessment?
R1 · Type Safety9.7 / 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.
Do you agree with this assessment?
R10 · Code Duplication5.0 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
80 duplicated blocks under core/src/components/ have copies in at least two of the sibling directories action-sheet, alert, back-button, badge, breadcrumb, breadcrumbs (+47 more sibling(s) not listed) — 60 of them are reported below, and 20 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 80 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 80 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 80 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. — core/src/components/input/input.tsx:158
11 duplicated blocks under packages/angular/src/ have copies in at least two of the sibling directories common, lazy, standalone — 9 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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/angular/src/lazy/directives/angular-component-lib/utils.ts:22
10 duplicated blocks under packages/ have copies in at least two of the sibling directories angular, react, react-router, vue, vue-router — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/react/src/routing/LocationHistory.ts:41
core/src/components/input/input.tsx:158 · core/src/components/textarea/textarea.tsx:123 — the two spans are one implementation copied and then locally edited — 1022 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. — core/src/components/input/input.tsx:158
core/src/components/checkbox/checkbox.tsx:88 · core/src/components/toggle/toggle.tsx:106 — the two spans are one implementation copied and then locally edited — 610 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. — core/src/components/checkbox/checkbox.tsx:88
core/src/components/input/input.tsx:811 · core/src/components/textarea/textarea.tsx:626 — the two spans are one implementation copied and then locally edited — 685 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. — core/src/components/input/input.tsx:811
core/src/components/modal/animations/ios.transition.ts:17 · core/src/components/modal/animations/ios.transition.ts:108 — 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. — core/src/components/modal/animations/ios.transition.ts:17
packages/react/src/components/createOverlayComponent.tsx:2 · packages/react/src/components/react-component-lib/createOverlayComponent.tsx:1 — these 2 files are line-for-line copies of one another — 75 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/react/src/components/createOverlayComponent.tsx:2
core/src/components/popover/animations/ios.enter.ts:26 · core/src/components/popover/animations/md.enter.ts:14 — the two spans are one implementation copied and then locally edited — 415 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. — core/src/components/popover/animations/ios.enter.ts:26
core/src/components/select-modal/select-modal.tsx:75 · core/src/components/select-popover/select-popover.tsx:85 — the two spans are one implementation copied and then locally edited — 378 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. — core/src/components/select-modal/select-modal.tsx:75
core/src/components/input/input.tsx:645 · core/src/components/textarea/textarea.tsx:534 — the two spans are one implementation copied and then locally edited — 368 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. — core/src/components/input/input.tsx:645
packages/react/src/routing/OutletPageManager.tsx:10 · packages/react/src/routing/PageManager.tsx:9 — the two spans are one implementation copied and then locally edited — 363 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/react/src/routing/OutletPageManager.tsx:10
core/src/components/searchbar/searchbar.tsx:142 · core/src/components/textarea/textarea.tsx:157 — the two spans are one implementation copied and then locally edited — 368 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. — core/src/components/searchbar/searchbar.tsx:142
core/src/components/select-modal/select-modal.tsx:162 · core/src/components/select-popover/select-popover.tsx:126 — 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. — core/src/components/select-modal/select-modal.tsx:162
packages/react/src/routing/LocationHistory.ts:41 · packages/vue-router/src/locationHistory.ts:30 — the two spans are one implementation copied and then locally edited — 290 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/react/src/routing/LocationHistory.ts:41
core/src/components/loading/loading.tsx:46 · core/src/components/toast/toast.tsx:67 — the two spans are one implementation copied and then locally edited — 437 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. — core/src/components/loading/loading.tsx:46
core/src/components/datetime/datetime.tsx:2019 · core/src/components/datetime/datetime.tsx:2068 — 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. — core/src/components/datetime/datetime.tsx:2019
core/src/components/datetime/datetime.tsx:2151 · core/src/components/datetime/datetime.tsx:2194 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/src/components/datetime/datetime.tsx:2151
core/src/components/button/button.tsx:239 · core/src/components/fab-button/fab-button.tsx:196 — 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. — core/src/components/button/button.tsx:239
packages/angular/src/lazy/directives/angular-component-lib/utils.ts:22 · packages/angular/src/standalone/directives/angular-component-lib/utils.ts:22 — 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/angular/src/lazy/directives/angular-component-lib/utils.ts:22
packages/react-router/src/ReactRouter/IonReactHashRouter.tsx:14 · packages/react-router/src/ReactRouter/IonReactMemoryRouter.tsx:15 · packages/react-router/src/ReactRouter/IonReactRouter.tsx:24 — the 3 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. 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/react-router/src/ReactRouter/IonReactHashRouter.tsx:14
packages/react/eslint.config.js:4 · packages/vue/eslint.config.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react/eslint.config.js:4
packages/react-router/eslint.config.js:4 · packages/vue-router/eslint.config.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react-router/eslint.config.js:4
core/src/components/alert/alert.tsx:418 · core/src/components/toast/toast.tsx:336 — the two spans are one implementation copied and then locally edited — 213 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. — core/src/components/alert/alert.tsx:418
packages/react/src/hooks/useController.ts:8 · packages/react/src/hooks/useOverlay.ts:13 — the two spans are one implementation copied and then locally edited — 291 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/react/src/hooks/useController.ts:8
core/src/components/footer/footer.tsx:55 · core/src/components/tab-bar/tab-bar.tsx:91 — 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. — core/src/components/footer/footer.tsx:55
core/src/utils/transition/ios.transition.ts:76 · core/src/utils/transition/ios.transition.ts:110 — 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. — core/src/utils/transition/ios.transition.ts:76
core/src/components/modal/animations/ios.enter.ts:50 · core/src/components/modal/animations/ios.leave.ts:37 — the two spans are one implementation copied and then locally edited — 196 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. — core/src/components/modal/animations/ios.enter.ts:50
core/src/utils/transition/ios.transition.ts:554 · core/src/utils/transition/ios.transition.ts:720 — 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. — core/src/utils/transition/ios.transition.ts:554
packages/angular/src/common/overlays/modal.ts:110 · packages/angular/src/common/overlays/popover.ts:86 — 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/angular/src/common/overlays/modal.ts:110
packages/react/src/components/createControllerComponent.tsx:12 · packages/react/src/components/createOverlayComponent.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react/src/components/createControllerComponent.tsx:12
packages/react/src/hooks/useIonModal.ts:26 · packages/react/src/hooks/useIonPopover.ts:22 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react/src/hooks/useIonModal.ts:26
core/src/components/card-subtitle/card-subtitle.tsx:12 · core/src/components/card-title/card-title.tsx:12 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/src/components/card-subtitle/card-subtitle.tsx:12
core/src/components/action-sheet/action-sheet.tsx:131 · core/src/components/alert/alert.tsx:144 · core/src/components/loading/loading.tsx:116 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/src/components/action-sheet/action-sheet.tsx:131
core/src/components/back-button/back-button.tsx:26 · core/src/components/menu-button/menu-button.tsx:27 — the two spans are one implementation copied and then locally edited — 140 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. — core/src/components/back-button/back-button.tsx:26
core/src/components/modal/animations/ios.transition.ts:67 · core/src/components/modal/animations/ios.transition.ts:159 — 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. — core/src/components/modal/animations/ios.transition.ts:67
core/src/components/modal/modal.tsx:588 · core/src/components/popover/popover.tsx:456 — 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. — core/src/components/modal/modal.tsx:588
core/src/components/action-sheet/action-sheet.tsx:233 · core/src/components/alert/alert.tsx:455 — 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. — core/src/components/action-sheet/action-sheet.tsx:233
core/src/components/badge/badge.tsx:12 · core/src/components/note/note.tsx:12 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/src/components/badge/badge.tsx:12
core/src/components/loading/animations/ios.enter.ts:8 · core/src/components/loading/animations/md.enter.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. — core/src/components/loading/animations/ios.enter.ts:8
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/react/src/components/IonPage.tsx:4 reaches into another package with a relative path (../routing/PageManager) — import the package by name instead. — packages/react/src/components/IonPage.tsx:4
packages/react/src/components/IonRouterOutlet.tsx:5 reaches into another package with a relative path (../routing/OutletPageManager) — import the package by name instead. — packages/react/src/components/IonRouterOutlet.tsx:5
packages/react/src/components/navigation/IonTabs.tsx:6 reaches into another package with a relative path (../../routing/PageManager) — import the package by name instead. — packages/react/src/components/navigation/IonTabs.tsx:6
packages/react/src/index.ts:5 reaches into another package with a relative path (./routing) — import the package by name instead. — packages/react/src/index.ts:5
packages/react/src/routing/LocationHistory.ts:1 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead. — packages/react/src/routing/LocationHistory.ts:1
packages/react/src/routing/NavManager.tsx:4 reaches into another package with a relative path (../components/IonRouterContext) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:4
packages/react/src/routing/NavManager.tsx:5 reaches into another package with a relative path (../components/IonRouterContext) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:5
packages/react/src/routing/NavManager.tsx:6 reaches into another package with a relative path (../contexts/NavContext) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:6
packages/react/src/routing/NavManager.tsx:7 reaches into another package with a relative path (../contexts/NavContext) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:7
packages/react/src/routing/NavManager.tsx:8 reaches into another package with a relative path (../models/RouteAction) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:8
packages/react/src/routing/NavManager.tsx:9 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:9
packages/react/src/routing/NavManager.tsx:10 reaches into another package with a relative path (../models/RouterDirection) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:10
packages/react/src/routing/NavManager.tsx:11 reaches into another package with a relative path (../models/RouterOptions) — import the package by name instead. — packages/react/src/routing/NavManager.tsx:11
packages/react/src/routing/OutletPageManager.tsx:4 reaches into another package with a relative path (../components/inner-proxies) — import the package by name instead. — packages/react/src/routing/OutletPageManager.tsx:4
packages/react/src/routing/OutletPageManager.tsx:5 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead. — packages/react/src/routing/OutletPageManager.tsx:5
packages/react/src/routing/OutletPageManager.tsx:6 reaches into another package with a relative path (../models) — import the package by name instead. — packages/react/src/routing/OutletPageManager.tsx:6
packages/react/src/routing/PageManager.tsx:3 reaches into another package with a relative path (../components/react-component-lib/utils) — import the package by name instead. — packages/react/src/routing/PageManager.tsx:3
packages/react/src/routing/PageManager.tsx:4 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead. — packages/react/src/routing/PageManager.tsx:4
packages/react/src/routing/PageManager.tsx:5 reaches into another package with a relative path (../models) — import the package by name instead. — packages/react/src/routing/PageManager.tsx:5
packages/react/src/routing/RouteManagerContext.ts:3 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead. — packages/react/src/routing/RouteManagerContext.ts:3
packages/react/src/routing/StackContext.tsx:3 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead. — packages/react/src/routing/StackContext.tsx:3
packages/react/src/routing/ViewLifeCycleManager.tsx:3 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead. — packages/react/src/routing/ViewLifeCycleManager.tsx:3
packages/react/src/routing/ViewStacks.ts:1 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead. — packages/react/src/routing/ViewStacks.ts:1
packages/react/src/routing/__tests__/LocationHistory.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../models/RouteInfo) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/react/src/routing/__tests__/LocationHistory.spec.ts:2
packages/react/src/routing/__tests__/LocationHistory.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../../utils/generateId) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/react/src/routing/__tests__/LocationHistory.spec.ts:3
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.
handleHistoryChange has cyclomatic complexity 55 and cognitive complexity 98; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/vue-router/src/router.ts:458
renderViewItem has cyclomatic complexity 46 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435
handleHistoryChange has cyclomatic complexity 45 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/IonRouter.tsx:165
renderKnob has cyclomatic complexity 43 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/range/range.tsx:1093
(anonymous) has cyclomatic complexity 31 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/utils/computeParentPath.ts:240
main has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/migrate/src/main.ts:108
matchView has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:884
(anonymous) has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/input-otp/input-otp.tsx:634
(anonymous) has cyclomatic complexity 26 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. — core/src/components/datetime/datetime.tsx:2433
(anonymous) has cyclomatic complexity 25 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/input-otp/input-otp.tsx:555
detect has cyclomatic complexity 24 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/migrate/src/migrations/v9/react-router-6-code.ts:111
(anonymous) has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/utils/transition/ios.transition.ts:498
handlePageTransition has cyclomatic complexity 24 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vue/src/components/IonRouterOutlet.ts:279
setDateTimeText has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/datetime-button/datetime-button.tsx:191
(anonymous) has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/datetime/utils/manipulation.ts:343
render has cyclomatic complexity 21 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/item/item.tsx:385
(anonymous) has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:319
verify has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:88
(anonymous) has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/picker-column/picker-column.tsx:482
setNextIndex has cyclomatic complexity 19 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/segment/segment.tsx:506
(anonymous) has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/utils/pathMatching.ts:27
onEnd has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/menu/menu.tsx:618
processValue has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — core/src/components/datetime/datetime.tsx:1419
onMove has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — core/src/components/modal/gestures/sheet.ts:355
callback has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — core/src/components/popover/utils.ts:461
handleNavigate has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-router/src/ReactRouter/IonRouter.tsx:587
postViewInit has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/nav/nav.tsx:665
(anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/react-router/src/ReactRouter/utils/viewItemUtils.ts:15
render has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/range/range.tsx:987
(anonymous) has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/scripts/testing/scripts.js:23
generateTime has cyclomatic complexity 17 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/datetime/utils/data.ts:202
callProblems has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/migrate/src/migrations/v9/react-overlay-hook-props-manual.ts:32
findComponentDeclarations has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:40
checkConfig has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/components/CreateAnimation.tsx:113
render has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/searchbar/searchbar.tsx:643
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/components/createOverlayComponent.tsx:21
render has cyclomatic complexity 17 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/input/input.tsx:864
prepareTI has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/src/components/nav/nav.tsx:564
onMove has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — core/src/components/refresher/refresher.tsx:680
(anonymous) has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/components/react-component-lib/utils/attachProps.ts:44
Do you agree with this assessment?
R3 · Large Files7.0 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
core/src/components/datetime/datetime.tsx has 2575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/datetime/datetime.tsx:1
packages/react-router/src/ReactRouter/StackManager.tsx has 1813 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react-router/src/ReactRouter/StackManager.tsx:1
core/src/components/modal/modal.tsx has 1603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/modal/modal.tsx:1
core/src/components/select/select.tsx has 1532 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/select/select.tsx:1
core/src/components/range/range.tsx has 1132 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/range/range.tsx:1
core/src/utils/overlays.ts has 1015 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/utils/overlays.ts:1
core/src/components/popover/utils.ts has 1000 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/popover/utils.ts:1
packages/vue-router/src/router.ts has 982 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/vue-router/src/router.ts:1
packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx has 977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:1
core/src/components/nav/nav.tsx has 889 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/nav/nav.tsx:1
core/src/components/alert/alert.tsx has 871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/alert/alert.tsx:1
core/src/components/input/input.tsx has 853 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/input/input.tsx:1
core/src/components/refresher/refresher.tsx has 845 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/refresher/refresher.tsx:1
core/src/utils/animation/animation.ts has 818 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/utils/animation/animation.ts:1
core/src/components/input-otp/input-otp.tsx has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/input-otp/input-otp.tsx:1
core/src/components/picker-column/picker-column.tsx has 789 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/picker-column/picker-column.tsx:1
core/src/components/menu/menu.tsx has 779 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/menu/menu.tsx:1
core/src/utils/transition/ios.transition.ts has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/utils/transition/ios.transition.ts:1
core/src/components/popover/popover.tsx has 725 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/popover/popover.tsx:1
core/src/components/textarea/textarea.tsx has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/textarea/textarea.tsx:1
core/src/components/toast/toast.tsx has 696 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/toast/toast.tsx:1
packages/react-router/src/ReactRouter/IonRouter.tsx 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. — packages/react-router/src/ReactRouter/IonRouter.tsx:1
core/src/components/searchbar/searchbar.tsx has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/searchbar/searchbar.tsx:1
core/src/components/modal/gestures/sheet.ts has 653 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/modal/gestures/sheet.ts:1
packages/vue/src/components/IonRouterOutlet.ts has 634 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/vue/src/components/IonRouterOutlet.ts:1
core/src/components/action-sheet/action-sheet.tsx has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/action-sheet/action-sheet.tsx:1
core/src/components/content/content.tsx has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/content/content.tsx:1
core/src/components/segment/segment.tsx has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/segment/segment.tsx:1
packages/angular/src/common/directives/navigation/router-outlet.ts has 608 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/angular/src/common/directives/navigation/router-outlet.ts:1
core/src/components/datetime/utils/data.ts has 601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/datetime/utils/data.ts:1
core/src/components/datetime/utils/manipulation.ts has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/datetime/utils/manipulation.ts:1
core/src/components/picker/picker.tsx has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/picker/picker.tsx:1
core/src/components/item/item.tsx has 486 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/item/item.tsx:1
core/src/components/toggle/toggle.tsx has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/toggle/toggle.tsx:1
core/src/components/accordion/accordion.tsx has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/accordion/accordion.tsx:1
core/src/components/item-sliding/item-sliding.tsx has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/item-sliding/item-sliding.tsx:1
core/src/utils/sanitization/index.ts has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/utils/sanitization/index.ts:1
core/src/components/datetime-button/datetime-button.tsx has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/components/datetime-button/datetime-button.tsx:1
packages/react/src/components/createInlineOverlayComponent.tsx has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/createInlineOverlayComponent.tsx:1
core/src/utils/helpers.ts has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/src/utils/helpers.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 Coverage7.9 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — core/src/components/refresher/refresher.tsx:1, core/src/components/input-otp/input-otp.tsx:1, core/src/components/menu/menu.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code7.3 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
1 file(s) (~2 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: core/scripts/custom-elements/custom-elements.d.ts imports './index', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — core/scripts/custom-elements
4 file(s) (~164 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/angular/test/apps/ng18/src/main.server.ts imports './environments/environment', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/angular/test/apps/ng18
4 file(s) (~120 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/angular/test/apps/ng19
1 file(s) (~65 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/angular/test/apps/ng20
2 file(s) (~65 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/angular/test/apps/ng21
3 file(s) (~103 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/angular/test/apps/ng22
3 file(s) (~114 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/angular/test/apps/ng22-zone
1 file(s) (~9 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/react-router/test/apps/reactrouter6-react18
2 file(s) (~193 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/react-router/test/apps/reactrouter6-react19
3 file(s) (~28 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/react/test/apps/react18/src/index.tsx imports './App', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/react/test/apps/react18
3 file(s) (~30 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/react/test/apps/react19/src/index.tsx imports './App', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/react/test/apps/react19
1 file(s) (~14 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/vue/test/apps/vue3
Unreachable from the 142 application, 55 tooling and 1244 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (142 application, 55 tooling, 1244 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 (×22) — core/src/components/refresher/refresher.tsx, core/src/components/input-otp/input-otp.tsx, core/src/components/menu/menu.tsx, …
no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/utils/input-shims/input-shims.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — core/src/utils/input-shims/hacks/scroll-assist.ts
no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/components/header/header.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — core/src/components/header/header.utils.ts
no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/components/app/app.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — core/src/utils/tap-click/index.ts, core/src/utils/input-shims/input-shims.ts
no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/angular/schematics/add/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/angular/schematics/utils/config.ts
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×9) — core/src/utils/test/playwright/matchers/toHaveReceivedEventDetail.ts:2, packages/angular/test/base/src/app/app.server.module.ts:2, packages/angular/test/base/server.ts:4, …
Declared in packages/angular/test/apps/ng18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/apps/ng19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/apps/ng20/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/apps/ng21/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/apps/ng22/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/apps/ng22-zone/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/angular/test/code-split/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Declared in packages/react-router/test/apps/reactrouter6-react18/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in packages/react-router/test/apps/reactrouter6-react18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/react-router/test/apps/reactrouter6-react19/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in packages/react-router/test/apps/reactrouter6-react19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/react/test/apps/react18/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in packages/react/test/apps/react18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/react/test/apps/react19/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Declared in packages/react/test/apps/react19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/vue/test/apps/vue3/package.json but never imported anywhere in that package or its workspace members — while packages/vue/test/base/tests/unit/deprecations.spec.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
core/src/utils/transition/index.ts → core/src/utils/transition/ios.transition.ts → core/src/utils/transition/index.ts (one verified cycle inside a mutually-dependent group of 3 files) — core/src/utils/transition/index.ts:15
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — core/vercel.json:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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.
`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. — core/src/components/modal/modal.tsx:1398
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 · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`deepReady` is exported and takes `el: any | undefined` from its caller, and it calls itself at line 270 (`deepReady`) with a piece of `el` — and nowhere in `deepReady` 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 `deepReady` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — core/src/utils/transition/index.ts:270
`sanitizeDOMTree` is exported, takes a document from its caller (line 133) and hands it to `sanitizeElement`, which calls itself at line 242 (`sanitizeElement`) with a piece of `element` — and nowhere in `sanitizeElement` 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 `sanitizeElement` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — core/src/utils/sanitization/index.ts:242
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 `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.5 / 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.
`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. (×2) — core/src/components/select/select.tsx:1156, packages/react-router/src/ReactRouter/clonePageElement.ts:10
`untrustedString` 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. — core/src/utils/sanitization/index.ts:58
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. (×3) — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:727, packages/angular/src/common/directives/control-value-accessors/value-accessor.ts:87, core/src/components/popover/utils.ts:489
`.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. (×2) — packages/react-router/src/ReactRouter/StackManager.tsx:1403, core/src/components/router/router.tsx:416
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×3) — packages/migrate/src/migrations/v9/angular-zoneless.ts:89, packages/migrate/src/ast/browserslist.ts:114, core/src/global/config.ts:52
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.
25/28 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~6.7 `!` null assertions per 1k TypeScript source lines — 535 assertion(s) across the 80227 source line(s) of the 519 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: core/src/components/datetime/datetime.tsx (21), core/src/components/modal/modal.tsx (21), core/src/components/nav/nav.tsx (21). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 36 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 13 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×6
aria-hidden on a focusable element core/src/components/action-sheet/action-sheet.tsx:660— 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.
aria-hidden on a focusable element core/src/components/action-sheet/action-sheet.tsx:710— 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.
aria-hidden on a focusable element core/src/components/alert/alert.tsx:916— 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.
aria-hidden on a focusable element core/src/components/alert/alert.tsx:954— 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.
aria-hidden on a focusable element core/src/components/loading/loading.tsx:370— 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.
aria-hidden on a focusable element core/src/components/loading/loading.tsx:382— 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×4
Click handler on a non-interactive <div> core/src/components/accordion/accordion.tsx:519— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> core/src/components/checkbox/checkbox.tsx:398— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> core/src/components/popover/popover.tsx:798— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> core/src/components/toggle/toggle.tsx:524— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Orphaned knowledge core/src/utils/transition/ios.transition.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/src/utils/animation/animation.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/src/components/datetime/utils/data.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): should pass packages/react/src/hooks/__tests__/hooks.spec.tsx:5— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): type checks component props at compile time packages/react/src/hooks/__tests__/overlay-hook-types.spec.tsx:155— Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability· Test suite declares a test script but contains no test files · ×2
Test suite declares a test script but contains no test files: packages/react/test/apps/react18/ — The vitest suite in packages/react/test/apps/react18/ was installed and launched successfully, and the runner then found no test files to run — include: **/__tests__/**/*.?(c|m)[jt]s?(x), **/?(*.){test,spec}.?(c|m)[jt]s?(x). The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
Test suite declares a test script but contains no test files: packages/react/test/apps/react19/ — The vitest suite in packages/react/test/apps/react19/ was installed and launched successfully, and the runner then found no test files to run — include: **/__tests__/**/*.?(c|m)[jt]s?(x), **/?(*.){test,spec}.?(c|m)[jt]s?(x). The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
AC4 · Keyboard semantics· Clickable role="button" that no keyboard user can reach · ×1
Clickable role="button" that no keyboard user can reach core/src/components/picker-column-option/picker-column-option.tsx:127— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Empty aria-labelledby reference core/src/components/input/input.tsx:759— aria-labelledby is present but empty, so it references no element and the relationship is lost. Point it at the id(s) of the target element, or remove it.
Unlisted import 'fast-deep-equal' core/src/utils/test/playwright/matchers/toHaveReceivedEventDetail.ts:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@angular/platform-server' packages/angular/test/base/src/app/app.server.module.ts:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'express' packages/angular/test/base/server.ts:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react-router' packages/react/test/base/src/App.tsx:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@testing-library/jest-dom' packages/react-router/test/base/src/setupTests.ts:5— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@testing-library/react' packages/react-router/test/base/src/App.test.tsx:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'cypress-terminal-report' packages/react-router/test/base/tests/e2e/plugins/index.js:21— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'ionicons' packages/react-router/test/base/src/pages/dynamic-tabs/DynamicTabs.tsx:15— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@vue/test-utils' packages/vue/test/base/tests/unit/deprecations.spec.ts:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
No assertions: should correctly go back to Tab 1 packages/vue/test/base/tests/e2e/specs/hbb.cy.js:2— 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 correctly go back to the root tab from child pages packages/vue/test/base/tests/e2e/specs/hbb.cy.js:33— 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 go to second page packages/vue/test/base/tests/e2e/specs/nested.cy.js:7— 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 go back to first page packages/vue/test/base/tests/e2e/specs/nested.cy.js:13— 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 go navigate across nested outlet contexts packages/vue/test/base/tests/e2e/specs/nested.cy.js:19— 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 replace a route but still be able to go back to main outlet packages/vue/test/base/tests/e2e/specs/nested.cy.js:33— 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 go to sibling page packages/vue/test/base/tests/e2e/specs/routing.cy.js:2— 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 set query params and keep view in stack packages/vue/test/base/tests/e2e/specs/routing.cy.js:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should go back home packages/vue/test/base/tests/e2e/specs/routing.cy.js: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 go back home with default href packages/vue/test/base/tests/e2e/specs/routing.cy.js:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should show back button packages/vue/test/base/tests/e2e/specs/routing.cy.js:39— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle parameterized urls properly packages/vue/test/base/tests/e2e/specs/routing.cy.js:72— 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 show correct view when navigating back from parameterized page to query string page packages/vue/test/base/tests/e2e/specs/routing.cy.js:85— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should correctly replace route in a component packages/vue/test/base/tests/e2e/specs/routing.cy.js:118— 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 show correct view when navigating between parameter urls packages/vue/test/base/tests/e2e/specs/routing.cy.js:131— 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 select correct leaving view when navigating between parameter urls packages/vue/test/base/tests/e2e/specs/routing.cy.js:158— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not show ion-back-button when replacing to root page packages/vue/test/base/tests/e2e/specs/routing.cy.js: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: should push a new instance of a parameterized page so there is a transition packages/vue/test/base/tests/e2e/specs/routing.cy.js:204— 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 select correct view when using router.go() packages/vue/test/base/tests/e2e/specs/routing.cy.js:222— 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 select correct view when traversing backward and forward through history packages/vue/test/base/tests/e2e/specs/routing.cy.js:247— 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 create new stack items when going back then pushing pages packages/vue/test/base/tests/e2e/specs/routing.cy.js:280— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should properly go back using ion-back-button after using router.go() packages/vue/test/base/tests/e2e/specs/routing.cy.js: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: should unmount views skipped over by using router.go with a negative value packages/vue/test/base/tests/e2e/specs/routing.cy.js:334— 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 choose correct view when navigating back packages/vue/test/base/tests/e2e/specs/routing.cy.js:353— 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 correctly replace a route after popping packages/vue/test/base/tests/e2e/specs/routing.cy.js:399— 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.
TodoComment packages/vue-router/src/router.ts:457— // TODO RouteLocationNormalized — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/vue-router/src/viewStacks.ts:155— // TODO(FW-2969): type
TodoComment packages/vue/src/components/IonBackButton.ts:10— // TODO(FW-2969): type
TodoComment packages/vue/src/components/IonRouterOutlet.ts:64— // TODO(FW-2969): type
TodoComment packages/vue/src/components/IonTabButton.ts:29— // TODO(FW-2969): type
TodoComment packages/vue/src/index.ts:86— // TODO(FW-6590): Remove the next two lines once the deprecated event is removed
TodoComment packages/react/src/components/index.ts:51— // TODO(FW-6590): Remove the next two lines once the deprecated event is removed
TodoComment packages/angular/src/standalone/index.ts:90— // TODO(FW-6590): Remove the next two lines once the deprecated event is removed
TodoComment packages/angular/src/lazy/index.ts:97— // TODO(FW-6590): Remove the next two lines once the deprecated event is removed
TodoComment packages/vue/src/components/IonTabs.ts:27— // TODO FW-5904
TodoComment packages/react/src/routing/OutletPageManager.tsx:15— // TODO(FW-2959): type
TodoComment packages/react/src/components/IonOverlayManager.tsx:23— // TODO(FW-2959): type
TodoComment packages/react/src/components/IonRouterContext.tsx:23— // TODO(FW-2959): type
TodoComment packages/react/src/components/utils/index.tsx:12— // TODO(FW-2959): type
TodoComment packages/react/src/hooks/__tests__/hooks.spec.tsx:1— // TODO: Jest does not support ES Modules, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/angular/test/base/src/app/standalone/nav/page-three.component.ts:25— // TODO: This is a workaround to have a working back button. — 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.
+ 83 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×40
Focus outline removed in CSS without a :focus replacement core/src/css/core.scss:462— `[ion-last-focus]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/toggle/toggle.scss:75— `:host(:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/toast/toast.scss:52— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/toast/toast.scss:168— `.toast-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/textarea/textarea.scss:134— `.native-textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/tab-button/tab-button.scss:31— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/tab-button/tab-button.scss:58— `.button-native` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/segment-button/segment-button.scss:108— `.button-native` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/segment-button/segment-button.scss:171— `:host(:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/searchbar/searchbar.scss:81— `.searchbar-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/searchbar/searchbar.scss:117— `.searchbar-cancel-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/searchbar/searchbar.scss:143— `.searchbar-clear-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/range/range.scss:97— `.range-knob-handle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/radio/radio.scss:57— `:host(:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/popover/popover.scss:40— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/picker-column-option/picker-column-option.scss:16— `.picker-column-option-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/picker-column/picker-column.scss:37— `.assistive-focusable:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/picker-column/picker-column.scss:62— `.picker-opts` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/picker-column/picker-column.scss:97— `.picker-item-empty` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/picker-column/picker-column.scss:186— `:host(:focus) .picker-opts` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/modal/modal.scss:53— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/modal/modal.scss:105— `.modal-wrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/menu-button/menu-button.scss:65— `.button-native` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/loading/loading.scss:36— `:host` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement core/src/components/item-option/item-option.scss:38— `.button-native` 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.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file core/src/components/refresher/refresher.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/input-otp/input-otp.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/menu/menu.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/item-sliding/item-sliding.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/datetime-button/datetime-button.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/router/router.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/reorder-group/reorder-group.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/utils/input-shims/hacks/scroll-assist.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 core/src/components/router-outlet/router-outlet.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/header/header.utils.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/vue/src/utils/overlays.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 core/src/components/select-popover/select-popover.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/tabs/tabs.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/header/header.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/infinite-scroll/infinite-scroll.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/select-modal/select-modal.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/angular/schematics/add/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/split-pane/split-pane.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/utils/tap-click/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/scripts/testing/prerender.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/footer/footer.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/react-component-lib/utils/attachProps.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 core/src/components/img/img.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/segment-view/segment-view.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/src/components/tab-bar/tab-bar.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Boundary violation [package:relative-cross-package] packages/react/src/components/IonPage.tsx:4— packages/react/src/components/IonPage.tsx:4 reaches into another package with a relative path (../routing/PageManager) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/components/IonRouterOutlet.tsx:5— packages/react/src/components/IonRouterOutlet.tsx:5 reaches into another package with a relative path (../routing/OutletPageManager) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/components/navigation/IonTabs.tsx:6— packages/react/src/components/navigation/IonTabs.tsx:6 reaches into another package with a relative path (../../routing/PageManager) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/index.ts:5— packages/react/src/index.ts:5 reaches into another package with a relative path (./routing) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/LocationHistory.ts:1— packages/react/src/routing/LocationHistory.ts:1 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:4— packages/react/src/routing/NavManager.tsx:4 reaches into another package with a relative path (../components/IonRouterContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:5— packages/react/src/routing/NavManager.tsx:5 reaches into another package with a relative path (../components/IonRouterContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:6— packages/react/src/routing/NavManager.tsx:6 reaches into another package with a relative path (../contexts/NavContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:7— packages/react/src/routing/NavManager.tsx:7 reaches into another package with a relative path (../contexts/NavContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:8— packages/react/src/routing/NavManager.tsx:8 reaches into another package with a relative path (../models/RouteAction) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:9— packages/react/src/routing/NavManager.tsx:9 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:10— packages/react/src/routing/NavManager.tsx:10 reaches into another package with a relative path (../models/RouterDirection) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/NavManager.tsx:11— packages/react/src/routing/NavManager.tsx:11 reaches into another package with a relative path (../models/RouterOptions) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/OutletPageManager.tsx:4— packages/react/src/routing/OutletPageManager.tsx:4 reaches into another package with a relative path (../components/inner-proxies) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/OutletPageManager.tsx:5— packages/react/src/routing/OutletPageManager.tsx:5 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/OutletPageManager.tsx:6— packages/react/src/routing/OutletPageManager.tsx:6 reaches into another package with a relative path (../models) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/PageManager.tsx:3— packages/react/src/routing/PageManager.tsx:3 reaches into another package with a relative path (../components/react-component-lib/utils) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/PageManager.tsx:4— packages/react/src/routing/PageManager.tsx:4 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/PageManager.tsx:5— packages/react/src/routing/PageManager.tsx:5 reaches into another package with a relative path (../models) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/RouteManagerContext.ts:3— packages/react/src/routing/RouteManagerContext.ts:3 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/StackContext.tsx:3— packages/react/src/routing/StackContext.tsx:3 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/ViewLifeCycleManager.tsx:3— packages/react/src/routing/ViewLifeCycleManager.tsx:3 reaches into another package with a relative path (../contexts/IonLifeCycleContext) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/react/src/routing/ViewStacks.ts:1— packages/react/src/routing/ViewStacks.ts:1 reaches into another package with a relative path (../models/RouteInfo) — import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/react/src/routing/__tests__/LocationHistory.spec.ts:2— packages/react/src/routing/__tests__/LocationHistory.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../models/RouteInfo) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/react/src/routing/__tests__/LocationHistory.spec.ts:3— packages/react/src/routing/__tests__/LocationHistory.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../../utils/generateId) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
D30 · Dependency Vulnerabilities· Medium CVE · ×24
Skipped test: should correctly go back to the root tab after switching pages packages/vue/test/base/tests/e2e/specs/hbb.cy.js:63— Skipped — switched off by it.skip
Skipped test: swipe to go back should work when using router.go() packages/vue/test/base/tests/e2e/specs/routing.cy.js:575— Skipped — switched off by it.skip
Skipped test: should swipe and go back to home packages/vue/test/base/tests/e2e/specs/tabs.cy.js:698— Skipped — switched off by it.skip
Skipped test: should swipe and go back within a tab packages/vue/test/base/tests/e2e/specs/tabs.cy.js:717— Skipped — switched off by it.skip
Skipped test: should swipe and go back to correct tab after switching tabs packages/vue/test/base/tests/e2e/specs/tabs.cy.js:728— Skipped — switched off by it.skip
Skipped test: should show correct tab when clicking the tab button packages/react/test/base/tests/e2e/specs/tabs/tabs.cy.ts:68— Skipped — switched off by it.skip
Skipped test: display modal with context packages/react/test/base/tests/e2e/specs/overlay-hooks/useIonModal.cy.ts:65— Skipped — switched off by it.skip
Skipped test: (unnamed test) core/src/utils/focus-controller/test/ionic/focus-controller.e2e.ts:48— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/utils/focus-controller/test/generic/focus-controller.e2e.ts:48— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-popover/test/basic/select-popover.e2e.ts:23— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-popover/test/basic/select-popover.e2e.ts:58— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-popover/test/basic/select-popover.e2e.ts:87— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-modal/test/basic/select-modal.e2e.ts:23— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-modal/test/basic/select-modal.e2e.ts:58— Skipped — switched off by test.skip
Skipped test: (unnamed test) core/src/components/select-modal/test/basic/select-modal.e2e.ts:87— Skipped — switched off by test.skip
Skipped test: should render no event popover core/src/components/popover/test/basic/popover.e2e.ts:33— Skipped — switched off by test.skip
Skipped test: scrolling should change the active item core/src/components/picker-column/test/basic/picker-column.e2e.ts:40— Skipped — switched off by test.skip
Skipped test: should emit ionChange when the picker is scrolled core/src/components/picker-column/test/basic/picker-column.e2e.ts:66— Skipped — switched off by test.skip
Skipped test: should position fabs correctly with custom sizes core/src/components/fab/test/custom-size/fab.e2e.ts:10— Skipped — switched off by test.skip
Skipped test: accordions should be keyboard navigable core/src/components/accordion/test/a11y/accordion.e2e.ts:7— Skipped — switched off by test.skip
FunctionTooLong: animation.createAnimation core/src/utils/animation/animation.ts:33— FunctionTooLong — createAnimation runs 521 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 421 over it, 5.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: IonRouter.IonRouter packages/react-router/src/ReactRouter/IonRouter.tsx:77— FunctionTooLong — IonRouter 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: ios.transition.iosTransitionAnimation core/src/utils/transition/ios.transition.ts:498— FunctionTooLong — iosTransitionAnimation runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.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: viewStacks.createViewStacks packages/vue-router/src/viewStacks.ts:7— FunctionTooLong — createViewStacks 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.
FunctionTooLong: createInlineOverlayComponent.createInlineOverlayComponent packages/react/src/components/createInlineOverlayComponent.tsx:111— FunctionTooLong — createInlineOverlayComponent runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: overlays.defineOverlayContainer packages/vue/src/utils/overlays.ts:13— FunctionTooLong — defineOverlayContainer runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.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: index.createMenuController core/src/utils/menu-controller/index.ts:14— FunctionTooLong — createMenuController runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.createGesture core/src/utils/gesture/index.ts:7— FunctionTooLong — createGesture runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: locationHistory.createLocationHistory packages/vue-router/src/locationHistory.ts:3— FunctionTooLong — createLocationHistory runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: attribute-controller.createAttributeController core/src/utils/attribute-controller.ts:41— FunctionTooLong — createAttributeController runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ios.enter.iosEnterAnimation core/src/components/popover/animations/ios.enter.ts:32— FunctionTooLong — iosEnterAnimation runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: swipe-to-close.createSwipeToCloseGesture core/src/components/modal/gestures/swipe-to-close.ts:19— FunctionTooLong — createSwipeToCloseGesture runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: range.renderKnob core/src/components/range/range.tsx:1093— FunctionTooLong — renderKnob runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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.
FileTooLong: datetime/datetime.tsx core/src/components/datetime/datetime.tsx— FileTooLong — 1456 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Datetime (118-2889). The bar is 500 significant lines; this is 956 over it, 2.91× 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: ReactRouter/StackManager.tsx packages/react-router/src/ReactRouter/StackManager.tsx— FileTooLong — 1000 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: StackManager (134-1922). The bar is 500 significant lines; this is 500 over it, 2.00× 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: select/select.tsx core/src/components/select/select.tsx— FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: Select (94-1444). The bar is 500 significant lines; this is 349 over it, 1.70× 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: modal/modal.tsx core/src/components/modal/modal.tsx— FileTooLong — 763 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: Modal (80-1800). The bar is 500 significant lines; this is 263 over it, 1.53× 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: range/range.tsx core/src/components/range/range.tsx— FileTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: Range (66-1068). The bar is 500 significant lines; this is 162 over it, 1.32× 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: ReactRouter/ReactRouterViewStack.tsx packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx— FileTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: ReactRouterViewStack (290-1074). The bar is 500 significant lines; this is 83 over it, 1.17× 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: popover/utils.ts core/src/components/popover/utils.ts— FileTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 48 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: animation/animation.ts core/src/utils/animation/animation.ts— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: createAnimation (33-995). The bar is 500 significant lines; this is 40 over it, 1.08× 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: alert/alert.tsx core/src/components/alert/alert.tsx— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Alert (54-958). The bar is 500 significant lines; this is 32 over it, 1.06× 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: transition/ios.transition.ts core/src/utils/transition/ios.transition.ts— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× 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.
TooManyMethods: Datetime core/src/components/datetime/datetime.tsx:110— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× 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: Modal core/src/components/modal/modal.tsx:72— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Nav core/src/components/nav/nav.tsx:25— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: Select core/src/components/select/select.tsx:86— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: Input core/src/components/input/input.tsx:43— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: Range core/src/components/range/range.tsx:58— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: Menu core/src/components/menu/menu.tsx:29— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: Alert core/src/components/alert/alert.tsx:46— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Datetime core/src/components/datetime/datetime.tsx:110— ClassTooLong — 1372 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 400 significant lines; this is 972 over it, 3.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Modal core/src/components/modal/modal.tsx:72— ClassTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 400 significant lines; this is 288 over it, 1.72× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Select core/src/components/select/select.tsx:86— ClassTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 262 over it, 1.66× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Range core/src/components/range/range.tsx:58— ClassTooLong — 484 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 84 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Alert core/src/components/alert/alert.tsx:46— ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 76 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Nav core/src/components/nav/nav.tsx:25— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 65 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Refresher core/src/components/refresher/refresher.tsx:33— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 21 over it, 1.05× 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.
Change coupling: modal-interface.ts ↔ popover-interface.ts core/src/components/modal/modal-interface.ts:1— `core/src/components/modal/modal-interface.ts` and `core/src/components/popover/popover-interface.ts` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7c003516` feat(modal, popover): add ability to temporarily disable focus trappi…; `322a1dbc` refactor(types): remove overlay attribute interfaces (#26181); `9fbaaf95` chore(): simplify overlay attribute types (#25074) — run `git show` on any of them.
Change coupling: dom.ts ↔ path.ts core/src/components/router/utils/dom.ts:1— `core/src/components/router/utils/dom.ts` and `core/src/components/router/utils/path.ts` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a982516a` fix(router): support anchor fragments in href (#31172); `857550a0` chore(router): clean up code and add comments (#23355); `119e0c1f` refactor(all): avoid using export const enum (#16614) — run `git show` on any of them.
Change coupling: modal.tsx ↔ popover.tsx core/src/components/modal/modal.tsx:1— `core/src/components/modal/modal.tsx` and `core/src/components/popover/popover.tsx` change together 58% of the time (62 of the 106 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 62 shared commits counted here, the most recent 3 are `bfff8e13` fix(overlays): restore presented state after a DOM move (#31400); `db915bf6` docs(methods): update component method documentation #4145 (#30495); `92ce563c` fix(overlays): do not overwrite id set in htmlAttributes (#29722) — run `git show` on any of them.
Change coupling: nav.tsx ↔ dom.ts core/src/components/nav/nav.tsx:1— `core/src/components/nav/nav.tsx` and `core/src/components/router/utils/dom.ts` change together 58% of the time (14 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `d7354b58` feat(nav): remove ion-router integration (#31266); `119e0c1f` refactor(all): avoid using export const enum (#16614); `0f4ed816` chore(router): move RouterIntent out of interface — run `git show` on any of them.
Change coupling: action-sheet.tsx ↔ alert.tsx core/src/components/action-sheet/action-sheet.tsx:1— `core/src/components/action-sheet/action-sheet.tsx` and `core/src/components/alert/alert.tsx` change together 56% of the time (51 of the 91 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 51 shared commits counted here, the most recent 3 are `bfff8e13` fix(overlays): restore presented state after a DOM move (#31400); `db915bf6` docs(methods): update component method documentation #4145 (#30495); `c3b58f16` fix(overlays): hide the focus trap div from screen readers (#29970) — run `git show` on any of them.
Change coupling: nav.tsx ↔ router-outlet.tsx core/src/components/nav/nav.tsx:1— `core/src/components/nav/nav.tsx` and `core/src/components/router-outlet/router-outlet.tsx` change together 52% of the time (23 of the 44 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 23 shared commits counted here, the most recent 3 are `5f3f5fca` fix(nav): defer non-animated swipe back until the gesture completes (…; `f9415ef8` fix(nav): custom animation is now used correctly (#23779) (at that commit the file was still `core/src/components/router-outlet/route-outlet.tsx`); `b3b33127` feat(modal): add card-style presentation with swipe to close gesture … (at that commit the file was still `core/src/components/router-outlet/route-outlet.tsx`) — run `git show` on any of them.
Change coupling: action-sheet-interface.ts ↔ alert-interface.ts core/src/components/action-sheet/action-sheet-interface.ts:1— `core/src/components/action-sheet/action-sheet-interface.ts` and `core/src/components/alert/alert-interface.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f6fc22bb` fix(action-sheet, alert, toast): button roles autocomplete with avail…; `322a1dbc` refactor(types): remove overlay attribute interfaces (#26181); `9fbaaf95` chore(): simplify overlay attribute types (#25074) — run `git show` on any of them.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng20/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng21/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng22/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/apps/ng22-zone/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@angular/language-service' — Declared in packages/angular/test/code-split/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng20/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng21/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng22/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'core-js' — Declared in packages/angular/test/apps/ng22-zone/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng20/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng21/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng22/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wait-on' — Declared in packages/angular/test/apps/ng22-zone/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Hotspot: packages/react-router/src/ReactRouter/StackManager.tsx packages/react-router/src/ReactRouter/StackManager.tsx:1569— packages/react-router/src/ReactRouter/StackManager.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in StackManager.transitionPage at line 1569. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- packages/react-router/src/ReactRouter/StackManager.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/vue-router/src/router.ts packages/vue-router/src/router.ts:458— packages/vue-router/src/router.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in router.createIonRouter.handleHistoryChange at line 458. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- packages/vue-router/src/router.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/react-router/src/ReactRouter/ReactRouterViewStack.tsx packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435— packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in ReactRouterViewStack.renderViewItem at line 435. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- packages/react-router/src/ReactRouter/ReactRouterViewStack.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: core/src/components/item/item.tsx core/src/components/item/item.tsx:385— core/src/components/item/item.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in Item.render at line 385. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/components/item/item.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: core/src/components/popover/animations/ios.enter.ts core/src/components/popover/animations/ios.enter.ts:32— core/src/components/popover/animations/ios.enter.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ios.enter.iosEnterAnimation at line 32. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/components/popover/animations/ios.enter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/src/components/select/select.tsx core/src/components/select/select.tsx:1357— core/src/components/select/select.tsx changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is Select.render at line 1357), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(a11y): forward host tabindex to the native element (#31720)”; “fix(input, select, textarea): prevent floating label from overflowing while it floats (#31567)”; “fix(input, select, textarea): emit one click event when slotted content is clicked (#31423)”; “fix(select): derive option text from all child nodes (#31382)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/components/select/select.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/src/utils/helpers.ts core/src/utils/helpers.ts:221— core/src/utils/helpers.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is helpers.onCustomPropertyChange at line 221), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(rtl): respect `dir` of ancestor elements throughout components (#31459)”; “fix(button): sync aria attributes between host and native button (#31264)”; “fix(modal): prevent ion-content collapsing at content-based heights (#31413)”; “fix(menu): respect ion-app dir attribute for menu animation side (#31246)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/utils/helpers.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/src/components/button/button.tsx core/src/components/button/button.tsx:339— core/src/components/button/button.tsx changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is Button.render at line 339), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): clear reflected ARIA attrs from host after sync (#31660)”; “fix(a11y): forward host tabindex to the native element (#31720)”; “fix(button): sync aria attributes between host and native button (#31264)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/components/button/button.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/src/components/card/card.tsx core/src/components/card/card.tsx:138— core/src/components/card/card.tsx changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Card.renderCard at line 138), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): clear reflected ARIA attrs from host after sync (#31660)”; “fix(a11y): forward host tabindex to the native element (#31720)”; “fix(button): sync aria attributes between host and native button (#31264)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/components/card/card.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/src/utils/overlays.ts core/src/utils/overlays.ts:194— core/src/utils/overlays.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is overlays.trapKeyboardFocus at line 194), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(close-watcher): allow back navigation when nothing is open (#31520)”; “fix(modal): prevent ion-content collapsing at content-based heights (#31413)”; “fix(overlays): restore presented state after a DOM move (#31400)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:06:27 +00:00' --until='2026-11-13 17:06:27 +00:00' --full-history --no-merges -- core/src/utils/overlays.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.
MethodTooLong: Datetime.renderMonth core/src/components/datetime/datetime.tsx:2392— MethodTooLong — renderMonth runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ReactRouterViewStack.renderViewItem packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435— MethodTooLong — renderViewItem runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StackManager.transitionPage packages/react-router/src/ReactRouter/StackManager.tsx:1569— MethodTooLong — transitionPage runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Range.renderRangeSlider core/src/components/range/range.tsx:785— MethodTooLong — renderRangeSlider runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Item.render core/src/components/item/item.tsx:385— MethodTooLong — render runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Swallowed exception (empty catch) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:727— 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/react-router/src/ReactRouter/StackManager.tsx:1403— `.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/angular/src/common/directives/control-value-accessors/value-accessor.ts:87— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) core/src/components/router/router.tsx:416— `.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) core/src/components/popover/utils.ts:489— 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.
Low cohesion: InputPasswordToggle (LCOM4 4) core/src/components/input-password-toggle/input-password-toggle.tsx:13— InputPasswordToggle's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InputsComponent (LCOM4 4) packages/angular/test/base/src/app/lazy/inputs/inputs.component.ts:3— InputsComponent's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ProvidersComponent (LCOM4 4) packages/angular/test/base/src/app/lazy/providers/providers.component.ts:18— ProvidersComponent's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: OverlayControllersComponent (LCOM4 4) packages/angular/test/base/src/app/standalone/overlay-controllers/overlay-controllers.component.ts:9— OverlayControllersComponent's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Dead branch — condition is always false core/src/components/select/select.tsx:838— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
Dead branch — condition is always false core/src/components/select/select.tsx:864— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
Dead branch — condition is always false core/src/components/select/select.tsx:911— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
Dead branch — condition is always false core/src/components/select/select.tsx:944— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
Duplicated block (26 lines × 2 locations) core/src/utils/transition/ios.transition.ts:554— core/src/utils/transition/ios.transition.ts:554 · core/src/utils/transition/ios.transition.ts:720 — 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/angular/src/common/overlays/modal.ts:110— packages/angular/src/common/overlays/modal.ts:110 · packages/angular/src/common/overlays/popover.ts:86 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (26 lines × 2 locations) packages/react/src/components/createControllerComponent.tsx:12— packages/react/src/components/createControllerComponent.tsx:12 · packages/react/src/components/createOverlayComponent.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (26 lines × 2 locations) packages/react/src/hooks/useIonModal.ts:26— packages/react/src/hooks/useIonModal.ts:26 · packages/react/src/hooks/useIonPopover.ts:22 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Unused dependency '@testing-library/react' — Declared in packages/react-router/test/apps/reactrouter6-react18/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency '@testing-library/react' — Declared in packages/react-router/test/apps/reactrouter6-react19/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency '@testing-library/react' — Declared in packages/react/test/apps/react18/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency '@testing-library/react' — Declared in packages/react/test/apps/react19/package.json but never imported anywhere in that package or its workspace members — while packages/react-router/test/base/src/App.test.tsx DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency '@testing-library/user-event' — Declared in packages/react-router/test/apps/reactrouter6-react18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@testing-library/user-event' — Declared in packages/react-router/test/apps/reactrouter6-react19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@testing-library/user-event' — Declared in packages/react/test/apps/react18/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@testing-library/user-event' — Declared in packages/react/test/apps/react19/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×3
Untrusted text written into markup unescaped core/src/components/select/select.tsx:1156— `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 core/src/utils/sanitization/index.ts:58— `untrustedString` 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/react-router/src/ReactRouter/clonePageElement.ts:10— `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.
Swallowed exception (caught, then discarded) packages/migrate/src/migrations/v9/angular-zoneless.ts:89— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/migrate/src/ast/browserslist.ts:114— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) core/src/global/config.ts:52— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
IonRouter.IonRouter::handleHistoryChange (cyclomatic 44) packages/react-router/src/ReactRouter/IonRouter.tsx:165— IonRouter.IonRouter::handleHistoryChange 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. This shape REPEATS in the file: one other method here (IonRouter.IonRouter::handleNavigate) 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.
IonRouter.IonRouter::handleNavigate (cyclomatic 17) packages/react-router/src/ReactRouter/IonRouter.tsx:587— IonRouter.IonRouter::handleNavigate has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (IonRouter.IonRouter::handleHistoryChange) 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.
IonRouter.IonRouter::handleHistoryChange (cognitive 74) packages/react-router/src/ReactRouter/IonRouter.tsx:165— IonRouter.IonRouter::handleHistoryChange has cognitive complexity 74 (threshold 15). Drivers by points: if/else 24 (51 pts), boolean chains 19, ternaries 1 (4 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (IonRouter.IonRouter::handleNavigate) 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.
IonRouter.IonRouter::handleNavigate (cognitive 23) packages/react-router/src/ReactRouter/IonRouter.tsx:587— IonRouter.IonRouter::handleNavigate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (IonRouter.IonRouter::handleHistoryChange) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Change-coupling hub: picker.tsx → action-sheet.tsx, alert.tsx, modal.tsx, popover.tsx, toast.tsx core/src/components/picker/picker.tsx— `core/src/components/picker/picker.tsx` changes together with 5 other files — `core/src/components/action-sheet/action-sheet.tsx`, `core/src/components/alert/alert.tsx`, `core/src/components/modal/modal.tsx`, `core/src/components/popover/popover.tsx`, `core/src/components/toast/toast.tsx` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: loading.tsx → action-sheet.tsx, alert.tsx, modal.tsx, picker.tsx, popover.tsx, toast.tsx core/src/components/loading/loading.tsx— `core/src/components/loading/loading.tsx` changes together with 6 other files — `core/src/components/action-sheet/action-sheet.tsx`, `core/src/components/alert/alert.tsx`, `core/src/components/modal/modal.tsx`, `core/src/components/picker/picker.tsx`, `core/src/components/popover/popover.tsx`, `core/src/components/toast/toast.tsx` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
End-of-life runtime: Node.js 16 package.json:9— package.json declares Node.js 16 as this project's engines.node, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: Node.js 18 packages/angular/test/apps/ng19/package.json:69— packages/angular/test/apps/ng19/package.json declares Node.js 18 as this project's engines.node, and Node.js 18, support ended 2025-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Fake-async — async method never awaits packages/vue/scripts/build-vetur.js:35— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/vue/src/ionic-vue.ts:6— `install` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×2
Duplicated block with local edits (30 matched lines × 2 locations) core/src/components/alert/alert.tsx:418— core/src/components/alert/alert.tsx:418 · core/src/components/toast/toast.tsx:336 — the two spans are one implementation copied and then locally edited — 213 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (30 matched lines × 2 locations) packages/react/src/hooks/useController.ts:8— packages/react/src/hooks/useController.ts:8 · packages/react/src/hooks/useOverlay.ts:13 — the two spans are one implementation copied and then locally edited — 291 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) core/src/components/footer/footer.tsx:55— core/src/components/footer/footer.tsx:55 · core/src/components/tab-bar/tab-bar.tsx:91 — 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 (29 lines × 2 locations) core/src/utils/transition/ios.transition.ts:76— core/src/utils/transition/ios.transition.ts:76 · core/src/utils/transition/ios.transition.ts:110 — 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 (23 lines × 2 locations) core/src/components/modal/animations/ios.transition.ts:67— core/src/components/modal/animations/ios.transition.ts:67 · core/src/components/modal/animations/ios.transition.ts:159 — 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 (23 lines × 2 locations) core/src/components/modal/modal.tsx:588— core/src/components/modal/modal.tsx:588 · core/src/components/popover/popover.tsx:456 — 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 (22 lines × 2 locations) core/src/components/action-sheet/action-sheet.tsx:233— core/src/components/action-sheet/action-sheet.tsx:233 · core/src/components/alert/alert.tsx:455 — 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 (22 lines × 2 locations) core/src/components/badge/badge.tsx:12— core/src/components/badge/badge.tsx:12 · core/src/components/note/note.tsx:12 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Dead file (~905 LoC) core/src/components/input-otp/input-otp.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~905 LoC) core/src/components/menu/menu.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~169 LoC) core/src/components/footer/footer.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~169 LoC) packages/react/src/components/react-component-lib/utils/attachProps.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap core/src/utils/transition/index.ts:270— `deepReady` is exported and takes `el: any | undefined` from its caller, and it calls itself at line 270 (`deepReady`) with a piece of `el` — and nowhere in `deepReady` 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 `deepReady` 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 core/src/utils/sanitization/index.ts:242— `sanitizeDOMTree` is exported, takes a document from its caller (line 133) and hands it to `sanitizeElement`, which calls itself at line 242 (`sanitizeElement`) with a piece of `element` — and nowhere in `sanitizeElement` 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 `sanitizeElement` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
animation.createAnimation (cyclomatic 86) core/src/utils/animation/animation.ts:33— animation.createAnimation has cyclomatic complexity 86 (threshold 15). Most of this is not in the body itself: 5 of the 86 points are its own statements and the rest belongs to 39 function items inside it that branch (progressEnd, a function literal at line 830, getDuration, …). 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.
ReactRouterViewStack.renderViewItem (cyclomatic 64) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435— ReactRouterViewStack.renderViewItem has cyclomatic complexity 64 (threshold 15). Of this number, 46 points are the body's own statements and 18 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.
router.createIonRouter.handleHistoryChange (cyclomatic 52) packages/vue-router/src/router.ts:458— router.createIonRouter.handleHistoryChange has cyclomatic complexity 52 (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.
ios.transition.iosTransitionAnimation (cyclomatic 51) core/src/utils/transition/ios.transition.ts:498— ios.transition.iosTransitionAnimation has cyclomatic complexity 51 (threshold 15). Of this number, 23 points are the body's own statements and 28 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.
StackManager.transitionPage (cyclomatic 49) packages/react-router/src/ReactRouter/StackManager.tsx:1569— StackManager.transitionPage has cyclomatic complexity 49 (threshold 15). Of this number, 27 points are the body's own statements and 22 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
range.renderKnob (cyclomatic 47) core/src/components/range/range.tsx:1093— range.renderKnob has cyclomatic complexity 47 (threshold 15). Of this number, 43 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
StackManager.handleReadyEnteringView (cyclomatic 47) packages/react-router/src/ReactRouter/StackManager.tsx:492— StackManager.handleReadyEnteringView has cyclomatic complexity 47 (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.
Datetime.renderMonth (cyclomatic 41) core/src/components/datetime/datetime.tsx:2392— Datetime.renderMonth has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2433, 2540, 2570). 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.
createInlineOverlayComponent.createInlineOverlayComponent (cyclomatic 40) packages/react/src/components/createInlineOverlayComponent.tsx:111— createInlineOverlayComponent.createInlineOverlayComponent has cyclomatic complexity 40 (threshold 15). Of this number, 24 points are the body's own statements and 16 belong to 7 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.
manipulation.getClosestValidDate (cyclomatic 37) core/src/components/datetime/utils/manipulation.ts:428— manipulation.getClosestValidDate has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 9 of the 37 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 538, 492, 523, …). 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.
swipe-to-close.createSwipeToCloseGesture (cyclomatic 35) core/src/components/modal/gestures/swipe-to-close.ts:19— swipe-to-close.createSwipeToCloseGesture has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 6 function items inside it that branch (onEnd, onMove, canStart, …). 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.
StackManager.handlePageTransition (cyclomatic 33) packages/react-router/src/ReactRouter/StackManager.tsx:1140— StackManager.handlePageTransition 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.
StackManager.cleanupOrphanedSiblingViews (cyclomatic 32) packages/react-router/src/ReactRouter/StackManager.tsx:763— StackManager.cleanupOrphanedSiblingViews has cyclomatic complexity 32 (threshold 15). Of this number, 24 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
computeParentPath.computeParentPath (cyclomatic 31) packages/react-router/src/ReactRouter/utils/computeParentPath.ts:240— computeParentPath.computeParentPath 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.
ReactRouterViewStack.findViewItemByPath::matchView (cyclomatic 30) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:884— ReactRouterViewStack.findViewItemByPath::matchView has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.main (cyclomatic 29) packages/migrate/src/main.ts:108— main.main 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.
InputOTP.onInput (cyclomatic 27) core/src/components/input-otp/input-otp.tsx:634— InputOTP.onInput has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 634, 677). 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.
Item.render (cyclomatic 26) core/src/components/item/item.tsx:385— Item.render has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ReactRouterViewStack.createViewItem (cyclomatic 26) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:313— ReactRouterViewStack.createViewItem has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 319). 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.
StackManager.handleWaitingForIonPage (cyclomatic 26) packages/react-router/src/ReactRouter/StackManager.tsx:919— StackManager.handleWaitingForIonPage has cyclomatic complexity 26 (threshold 15). Of this number, 16 points are the body's own statements and 10 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.
InputOTP.onKeyDown (cyclomatic 25) core/src/components/input-otp/input-otp.tsx:555— InputOTP.onKeyDown has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to one function literal inside it that branches (line 555). 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.
overlays.defineOverlayContainer (cyclomatic 24) packages/vue/src/utils/overlays.ts:13— overlays.defineOverlayContainer has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 72, 202, 39, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.startTapClick (cyclomatic 23) core/src/utils/tap-click/index.ts:6— index.startTapClick has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (setActivatedElement, removeActivated, cancelActive, …). 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.
data.generateTime (cyclomatic 22) core/src/components/datetime/utils/data.ts:202— data.generateTime has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RadioGroup.onKeydown (cyclomatic 22) core/src/components/radio-group/radio-group.tsx:232— RadioGroup.onKeydown has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
verify-change-detection.verify (cyclomatic 22) REDACTED:88— verify-change-detection.verify has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
manipulation.validateParts (cyclomatic 21) core/src/components/datetime/utils/manipulation.ts:339— manipulation.validateParts 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.
Datetime.initializeCalendarListener (cyclomatic 21) core/src/components/datetime/datetime.tsx:915— Datetime.initializeCalendarListener has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 953, 1054, 1011, …). 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.
sheet.createSheetGesture.moveSheetToBreakpoint (cyclomatic 21) core/src/components/modal/gestures/sheet.ts:504— sheet.createSheetGesture.moveSheetToBreakpoint has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PickerColumn.initializeScrollListener (cyclomatic 21) core/src/components/picker-column/picker-column.tsx:475— PickerColumn.initializeScrollListener has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 482, 654). 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.
ReactRouterViewStack.getChildrenToRender (cyclomatic 20) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:682— ReactRouterViewStack.getChildrenToRender has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 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.
createOverlayComponent.createOverlayComponent (cyclomatic 20) packages/react/src/components/createOverlayComponent.tsx:21— createOverlayComponent.createOverlayComponent has cyclomatic complexity 20 (threshold 15). Of this number, 17 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.
scroll-assist.jsSetFocus (cyclomatic 19) core/src/utils/input-shims/hacks/scroll-assist.ts:211— scroll-assist.jsSetFocus has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Datetime.processValue (cyclomatic 19) core/src/components/datetime/datetime.tsx:1419— Datetime.processValue has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Menu.onEnd (cyclomatic 19) core/src/components/menu/menu.tsx:618— Menu.onEnd has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sheet.createSheetGesture.onMove (cyclomatic 19) core/src/components/modal/gestures/sheet.ts:355— sheet.createSheetGesture.onMove has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
utils.configureKeyboardInteraction::callback (cyclomatic 19) core/src/components/popover/utils.ts:461— utils.configureKeyboardInteraction::callback 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.
Segment.setNextIndex (cyclomatic 19) core/src/components/segment/segment.tsx:506— Segment.setNextIndex 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.
createOverlayComponent.createOverlayComponent (cyclomatic 19) packages/react/src/components/react-component-lib/createOverlayComponent.tsx:21— createOverlayComponent.createOverlayComponent has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
IonTabs.render (cyclomatic 19) packages/react/src/components/navigation/IonTabs.tsx:119— IonTabs.render has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 130). 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.
IonTabBarUnwrapped.getDerivedStateFromProps (cyclomatic 19) packages/react/src/components/navigation/IonTabBar.tsx:136— IonTabBarUnwrapped.getDerivedStateFromProps has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Range.render (cyclomatic 18) core/src/components/range/range.tsx:987— Range.render 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.
viewItemUtils.compareRouteSpecificity (cyclomatic 18) packages/react-router/src/ReactRouter/utils/viewItemUtils.ts:12— viewItemUtils.compareRouteSpecificity 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.
attachProps.attachProps (cyclomatic 18) packages/react/src/components/react-component-lib/utils/attachProps.ts:35— attachProps.attachProps has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). 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.
ios.enter.iosEnterAnimation (cyclomatic 17) core/src/components/popover/animations/ios.enter.ts:32— ios.enter.iosEnterAnimation has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 153). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Searchbar.render (cyclomatic 17) core/src/components/searchbar/searchbar.tsx:643— Searchbar.render has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
verify-change-detection.findComponentDeclarations (cyclomatic 17) REDACTED:40— verify-change-detection.findComponentDeclarations 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.
react-overlay-hook-props-manual.callProblems (cyclomatic 17) packages/migrate/src/migrations/v9/react-overlay-hook-props-manual.ts:32— react-overlay-hook-props-manual.callProblems has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pathMatching.matchPath (cyclomatic 17) packages/react-router/src/ReactRouter/utils/pathMatching.ts:27— pathMatching.matchPath 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.
CreateAnimation.checkConfig (cyclomatic 17) packages/react/src/components/CreateAnimation.tsx:113— CreateAnimation.checkConfig 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.
ActionSheet.onKeydown (cyclomatic 16) core/src/components/action-sheet/action-sheet.tsx:373— ActionSheet.onKeydown 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.
input-shims.startInputShims::registerInput (cyclomatic 16) core/src/utils/input-shims/input-shims.ts:61— input-shims.startInputShims::registerInput has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DatetimeButton.setDateTimeText (cyclomatic 16) core/src/components/datetime-button/datetime-button.tsx:191— DatetimeButton.setDateTimeText 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.
Input.render (cyclomatic 16) core/src/components/input/input.tsx:864— Input.render has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Modal.initParentRemovalObserver (cyclomatic 16) core/src/components/modal/modal.tsx:1403— Modal.initParentRemovalObserver has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Nav.prepareTI (cyclomatic 16) core/src/components/nav/nav.tsx:564— Nav.prepareTI 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.
Nav.postViewInit (cyclomatic 16) core/src/components/nav/nav.tsx:665— Nav.postViewInit has cyclomatic complexity 16 (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.
Refresher.onMove (cyclomatic 16) core/src/components/refresher/refresher.tsx:680— Refresher.onMove 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. This is NOT this file's highest cyclomatic complexity: Refresher.setupiOSNativeRefresher (cyclomatic 21) 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.
StackManager.findViewItems (cyclomatic 16) packages/react-router/src/ReactRouter/StackManager.tsx:260— StackManager.findViewItems has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
createControllerComponent.createControllerComponent (cyclomatic 16) packages/react/src/components/createControllerComponent.tsx:19— createControllerComponent.createControllerComponent has cyclomatic complexity 16 (threshold 15). Of this number, 13 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: should make a later setActive wait for the in-flight attach core/src/components/tab/test/tab.spec.ts:42— This test starts work it did not wait for (`first`, 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.
TodoComment repeated across 13 files packages/react/src/framework-delegate.tsx:6— The identical TodoComment appears in 13 files (13 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 13 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO(FW-2959): types". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TodoComment repeated across 28 files core/src/utils/config.ts:236— The identical TodoComment appears in 28 files (28 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 28 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO(FW-2832): types". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TodoComment repeated across 11 files core/src/utils/focus-visible.ts:49— The identical TodoComment appears in 11 files (13 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 13 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO(FW-2832): type". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
animation.createAnimation (cognitive 107) core/src/utils/animation/animation.ts:33— animation.createAnimation has cognitive complexity 107 (threshold 15). Drivers by points: if/else 73 (84 pts), boolean chains 11, loops 6 (10 pts), ternaries 2 (nesting depth added 15). Most of this is not in the body itself: 3 of the 107 points are its own statements and the rest belongs to 39 function items inside it that branch (progressEnd, addElement, addAnimation, …). 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.
StackManager.transitionPage (cognitive 102) packages/react-router/src/ReactRouter/StackManager.tsx:1569— StackManager.transitionPage has cognitive complexity 102 (threshold 15). Drivers by points: if/else 31 (85 pts), boolean chains 15, ternaries 2 (nesting depth added 54). Of this number, 61 points are the body's own statements and 41 belong to 7 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ios.transition.iosTransitionAnimation (cognitive 93) core/src/utils/transition/ios.transition.ts:498— ios.transition.iosTransitionAnimation has cognitive complexity 93 (threshold 15). Drivers by points: if/else 35 (59 pts), ternaries 8 (22 pts), boolean chains 11, error handling 1 (nesting depth added 38). Of this number, 31 points are the body's own statements and 62 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.
ReactRouterViewStack.renderViewItem (cognitive 85) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435— ReactRouterViewStack.renderViewItem has cognitive complexity 85 (threshold 15). Drivers by points: if/else 24 (53 pts), boolean chains 23, ternaries 6 (9 pts) (nesting depth added 32). Of this number, 57 points are the body's own statements and 28 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
router.createIonRouter.handleHistoryChange (cognitive 78) packages/vue-router/src/router.ts:458— router.createIonRouter.handleHistoryChange has cognitive complexity 78 (threshold 15). Drivers by points: if/else 26 (48 pts), boolean chains 19, ternaries 3 (11 pts) (nesting depth added 30). 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.
computeParentPath.computeParentPath (cognitive 65) packages/react-router/src/ReactRouter/utils/computeParentPath.ts:240— computeParentPath.computeParentPath has cognitive complexity 65 (threshold 15). Drivers by points: if/else 15 (50 pts), boolean chains 12, loops 1 (3 pts) (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.
StackManager.handleReadyEnteringView (cognitive 50) packages/react-router/src/ReactRouter/StackManager.tsx:492— StackManager.handleReadyEnteringView has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 16, ternaries 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.
Datetime.renderMonth (cognitive 47) core/src/components/datetime/datetime.tsx:2392— Datetime.renderMonth has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 14, ternaries 5 (8 pts), error handling 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 8 of the 47 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 2433, 2540, 2570). 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.
ReactRouterViewStack.findViewItemByPath::matchView (cognitive 40) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:884— ReactRouterViewStack.findViewItemByPath::matchView has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (29 pts), boolean chains 10, ternaries 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.
manipulation.getClosestValidDate (cognitive 38) core/src/components/datetime/utils/manipulation.ts:428— manipulation.getClosestValidDate has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 13 (nesting depth added 10). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 476, 492, 509, …). 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.
StackManager.handlePageTransition (cognitive 38) packages/react-router/src/ReactRouter/StackManager.tsx:1140— StackManager.handlePageTransition has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 12 (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.
core-autocorrect.jsxAutocorrectAttrs (cognitive 37) packages/migrate/src/migrations/v9/core-autocorrect.ts:66— core-autocorrect.jsxAutocorrectAttrs has cognitive complexity 37 (threshold 15). Drivers by points: if/else 5 (25 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 37) packages/migrate/src/main.ts:108— main.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 7, ternaries 3 (6 pts), error handling 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.
swipe-to-close.createSwipeToCloseGesture (cognitive 36) core/src/components/modal/gestures/swipe-to-close.ts:19— swipe-to-close.createSwipeToCloseGesture has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15, boolean chains 12, ternaries 9. None of this is in the body itself: all 36 points belong to 6 function items inside it that branch (onEnd, onMove, canStart, …). 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.
InputOTP.onKeyDown (cognitive 34) core/src/components/input-otp/input-otp.tsx:555— InputOTP.onKeyDown has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 11, loops 2 (6 pts) (nesting depth added 9). None of this is in the body itself: all 34 points belong to one function literal inside it that branches (line 555). 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.
range.renderKnob (cognitive 34) core/src/components/range/range.tsx:1093— range.renderKnob has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 27, ternaries 5, if/else 2. Of this number, 30 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
createInlineOverlayComponent.createInlineOverlayComponent (cognitive 34) packages/react/src/components/createInlineOverlayComponent.tsx:111— createInlineOverlayComponent.createInlineOverlayComponent has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 12, ternaries 2 (nesting depth added 3). Of this number, 17 points are the body's own statements and 17 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
data.generateTime (cognitive 33) core/src/components/datetime/utils/data.ts:202— data.generateTime has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (31 pts), boolean chains 2 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ReactRouterViewStack.createViewItem (cognitive 33) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:313— ReactRouterViewStack.createViewItem has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 11 (nesting depth added 10). Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to one function literal inside it that branches (line 319). 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.
InputOTP.onInput (cognitive 31) core/src/components/input-otp/input-otp.tsx:634— InputOTP.onInput has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 13, if/else 9 (12 pts), loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 6). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 634, 677). 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.
scroll-assist.jsSetFocus (cognitive 30) core/src/utils/input-shims/hacks/scroll-assist.ts:211— scroll-assist.jsSetFocus has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 6 (nesting depth added 11). Of this number, 22 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.
StackManager.cleanupOrphanedSiblingViews (cognitive 30) packages/react-router/src/ReactRouter/StackManager.tsx:763— StackManager.cleanupOrphanedSiblingViews has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 13, loops 2, ternaries 1 (nesting depth added 5). Of this number, 20 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Segment.setNextIndex (cognitive 29) core/src/components/segment/segment.tsx:506— Segment.setNextIndex has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 4, 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.
RadioGroup.onKeydown (cognitive 28) core/src/components/radio-group/radio-group.tsx:232— RadioGroup.onKeydown has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 7 (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.
index.startTapClick (cognitive 27) core/src/utils/tap-click/index.ts:6— index.startTapClick has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 6 function items inside it that branch (setActivatedElement, removeActivated, cancelActive, …). 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.
sheet.createSheetGesture.moveSheetToBreakpoint (cognitive 27) core/src/components/modal/gestures/sheet.ts:504— sheet.createSheetGesture.moveSheetToBreakpoint has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 7, ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 596, 615, 593). 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.
StackManager.findRouteByRouteInfo (cognitive 27) packages/react-router/src/ReactRouter/StackManager.tsx:1978— StackManager.findRouteByRouteInfo has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 5, loops 1 (3 pts), ternaries 1 (nesting depth added 12). 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, 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.
verify-change-detection.verify (cognitive 26) REDACTED:88— verify-change-detection.verify has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 5 (9 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 7). Of this number, 23 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
attachProps.attachProps (cognitive 26) packages/react/src/components/react-component-lib/utils/attachProps.ts:35— attachProps.attachProps has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 4 (nesting depth added 12). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). 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.
ios.leave.iosLeaveAnimation (cognitive 25) core/src/components/modal/animations/ios.leave.ts:21— ios.leave.iosLeaveAnimation has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (11 pts), boolean chains 1 (nesting depth added 12). Of this number, 21 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.createFocusController.setViewFocus (cognitive 25) core/src/utils/focus-controller/index.ts:46— index.createFocusController.setViewFocus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 5, match/switch 1 (3 pts), 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.
overlays.defineOverlayContainer (cognitive 25) packages/vue/src/utils/overlays.ts:13— overlays.defineOverlayContainer has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5, ternaries 3, loops 2 (nesting depth added 2). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 72, 202, 39, …). 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.
overlays.trapKeyboardFocus (cognitive 24) core/src/utils/overlays.ts:194— overlays.trapKeyboardFocus has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (trapScopedFocus, trapShadowFocus). 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.
react-overlay-hooks.propsRead (cognitive 24) packages/migrate/src/ast/react-overlay-hooks.ts:125— react-overlay-hooks.propsRead has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (5 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.
ReactRouterViewStack.getChildrenToRender (cognitive 24) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:682— ReactRouterViewStack.getChildrenToRender has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 764, 743). 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.
ios.enter.iosEnterAnimation (cognitive 23) core/src/components/modal/animations/ios.enter.ts:26— ios.enter.iosEnterAnimation has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 7 (10 pts), boolean chains 2 (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.
angular-zoneless.targetProvidersArrays (cognitive 23) packages/migrate/src/migrations/v9/angular-zoneless.ts:163— angular-zoneless.targetProvidersArrays has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (3 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.
pathMatching.matchPath (cognitive 23) packages/react-router/src/ReactRouter/utils/pathMatching.ts:27— pathMatching.matchPath has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, ternaries 2 (5 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.
input-shims.startInputShims (cognitive 22) core/src/utils/input-shims/input-shims.ts:16— input-shims.startInputShims has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, loops 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (registerInput, unregisterInput). 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.
manipulation.validateParts (cognitive 22) core/src/components/datetime/utils/manipulation.ts:339— manipulation.validateParts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 7 (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.
PickerColumn.initializeScrollListener (cognitive 22) core/src/components/picker-column/picker-column.tsx:475— PickerColumn.initializeScrollListener has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 482, 654). 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.
matching.matchesSegments (cognitive 22) core/src/components/router/utils/matching.ts:95— matching.matchesSegments has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts), boolean chains 2, ternaries 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.
locationHistory.createLocationHistory.findLastLocation (cognitive 22) packages/vue-router/src/locationHistory.ts:229— locationHistory.createLocationHistory.findLastLocation has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (4 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Nav.prepareTI (cognitive 21) core/src/components/nav/nav.tsx:564— Nav.prepareTI has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, 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.
Nav.postViewInit (cognitive 21) core/src/components/nav/nav.tsx:665— Nav.postViewInit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (8 pts), boolean chains 4 (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.
angular-delegate.attachView (cognitive 21) packages/angular/src/common/providers/angular-delegate.ts:127— angular-delegate.attachView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
react-overlay-hook-props-manual.callProblems (cognitive 21) packages/migrate/src/migrations/v9/react-overlay-hook-props-manual.ts:32— react-overlay-hook-props-manual.callProblems has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). 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.
StackManager.handleWaitingForIonPage (cognitive 21) packages/react-router/src/ReactRouter/StackManager.tsx:919— StackManager.handleWaitingForIonPage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 9 (nesting depth added 5). Of this number, 18 points are the body's own statements and 3 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.
AccordionGroup.requestAccordionToggle (cognitive 20) core/src/components/accordion-group/accordion-group.tsx:214— AccordionGroup.requestAccordionToggle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (6 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.
Item.render (cognitive 20) core/src/components/item/item.tsx:385— Item.render has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (7 pts), if/else 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Menu.onEnd (cognitive 20) core/src/components/menu/menu.tsx:618— Menu.onEnd has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 8, if/else 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.
verify-change-detection.findComponentDeclarations (cognitive 20) REDACTED:40— verify-change-detection.findComponentDeclarations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
react-router-6-routes.routeActions (cognitive 20) packages/migrate/src/migrations/v9/react-router-6-routes.ts:56— react-router-6-routes.routeActions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (6 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.
CreateAnimation.checkConfig (cognitive 20) packages/react/src/components/CreateAnimation.tsx:113— CreateAnimation.checkConfig has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5 (6 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
router.createIonRouter.handleNavigateBack (cognitive 20) packages/vue-router/src/router.ts:334— router.createIonRouter.handleNavigateBack has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
viewStacks.createViewStacks.findViewItemByPath (cognitive 20) packages/vue-router/src/viewStacks.ts:91— viewStacks.createViewStacks.findViewItemByPath has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). Of this number, 14 points are the body's own statements and 6 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.
App.componentDidLoad (cognitive 19) core/src/components/app/app.tsx:21— App.componentDidLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). 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.
dom.findFragmentTarget (cognitive 19) core/src/components/router/utils/dom.ts:117— dom.findFragmentTarget has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
angular-zoneless.polyfillsEntries (cognitive 19) packages/migrate/src/migrations/v9/angular-zoneless.ts:39— angular-zoneless.polyfillsEntries has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
react-overlay-hook-props.annotations (cognitive 19) packages/migrate/src/migrations/v9/react-overlay-hook-props.ts:18— react-overlay-hook-props.annotations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (3 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.
IonTabBarUnwrapped.getDerivedStateFromProps (cognitive 19) packages/react/src/components/navigation/IonTabBar.tsx:136— IonTabBarUnwrapped.getDerivedStateFromProps has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (9 pts) (nesting depth added 4). Of this number, 13 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DatetimeButton.setDateTimeText (cognitive 18) core/src/components/datetime-button/datetime-button.tsx:191— DatetimeButton.setDateTimeText has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 1 (4 pts), boolean chains 1, match/switch 1, 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.
Datetime.initializeCalendarListener (cognitive 18) core/src/components/datetime/datetime.tsx:915— Datetime.initializeCalendarListener has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 3, ternaries 2. Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 953, 1011, 1054, …). 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.
ios.enter.iosEnterAnimation (cognitive 18) core/src/components/popover/animations/ios.enter.ts:32— ios.enter.iosEnterAnimation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 153). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Searchbar.positionCancelButton (cognitive 18) core/src/components/searchbar/searchbar.tsx:580— Searchbar.positionCancelButton has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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.
swipe-to-dismiss.createSwipeToDismissGesture (cognitive 18) core/src/components/toast/gestures/swipe-to-dismiss.ts:18— swipe-to-dismiss.createSwipeToDismissGesture has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 6 (7 pts), boolean chains 1, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (onEnd, a function literal at line 247). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.createMenuController.get (cognitive 18) core/src/utils/menu-controller/index.ts:85— index.createMenuController.get has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify-exports.verify (cognitive 18) packages/angular/scripts/verify-exports.js:47— verify-exports.verify has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
angular-zoneless.declaredProjects (cognitive 18) packages/migrate/src/migrations/v9/angular-zoneless.ts:81— angular-zoneless.declaredProjects has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (6 pts), if/else 3 (5 pts), loops 2 (4 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IonTabs.render (cognitive 18) packages/react/src/components/navigation/IonTabs.tsx:119— IonTabs.render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, boolean chains 5, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body: 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.
Datetime.processValue (cognitive 17) core/src/components/datetime/datetime.tsx:1419— Datetime.processValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Picker.onPointerDown (cognitive 17) core/src/components/picker/picker.tsx:153— Picker.onPointerDown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (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.
utils.configureKeyboardInteraction::callback (cognitive 17) core/src/components/popover/utils.ts:461— utils.configureKeyboardInteraction::callback has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, error handling 1, match/switch 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.
Range.render (cognitive 17) core/src/components/range/range.tsx:987— Range.render has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, ternaries 5. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Refresher.onMove (cognitive 17) core/src/components/refresher/refresher.tsx:680— Refresher.onMove has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, ternaries 1 (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.
matching.matchesIDs (cognitive 17) core/src/components/router/utils/matching.ts:37— matching.matchesIDs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (5 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.
Select.open (cognitive 17) core/src/components/select/select.tsx:505— Select.open has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 1 (nesting depth added 5). 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 item inside it that branches (scrollSelectedIntoView). 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.
pathMatching.derivePathnameToMatch (cognitive 17) packages/react-router/src/ReactRouter/utils/pathMatching.ts:115— pathMatching.derivePathnameToMatch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, ternaries 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
viewItemUtils.compareRouteSpecificity (cognitive 17) packages/react-router/src/ReactRouter/utils/viewItemUtils.ts:12— viewItemUtils.compareRouteSpecificity has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 7. 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.
createOverlayComponent.createOverlayComponent (cognitive 17) packages/react/src/components/createOverlayComponent.tsx:21— createOverlayComponent.createOverlayComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 7, ternaries 1. Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.sanitizeElement (cognitive 16) core/src/utils/sanitization/index.ts:154— index.sanitizeElement has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (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.
sheet.createSheetGesture.onMove (cognitive 16) core/src/components/modal/gestures/sheet.ts:355— sheet.createSheetGesture.onMove has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 3 (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.
createOverlayComponent.createOverlayComponent (cognitive 16) packages/react/src/components/react-component-lib/createOverlayComponent.tsx:21— createOverlayComponent.createOverlayComponent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 1. Of this number, 13 points are the body's own statements and 3 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.
LocationHistory.findLastLocation (cognitive 16) packages/react/src/routing/LocationHistory.ts:157— LocationHistory.findLastLocation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 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.
router.createIonRouter (cognitive 16) packages/vue-router/src/router.ts:24— router.createIonRouter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 220, 65, 121, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Off the main sequence: @ionic/core — @ionic/core: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
No structured logging — No logging call was found in the 543 JavaScript/TypeScript production file(s) this check read across 10 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 53 sibling directories (80 clone groups) core/src/components/input/input.tsx:158— 80 duplicated blocks under core/src/components/ have copies in at least two of the sibling directories action-sheet, alert, back-button, badge, breadcrumb, breadcrumbs (+47 more sibling(s) not listed) — 60 of them are reported below, and 20 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 80 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 80 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 80 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 (11 clone groups) packages/angular/src/lazy/directives/angular-component-lib/utils.ts:22— 11 duplicated blocks under packages/angular/src/ have copies in at least two of the sibling directories common, lazy, standalone — 9 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (10 clone groups) packages/react/src/routing/LocationHistory.ts:41— 10 duplicated blocks under packages/ have copies in at least two of the sibling directories angular, react, react-router, vue, vue-router — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (169 matched lines × 2 locations) · ×1
Duplicated block with local edits (169 matched lines × 2 locations) core/src/components/input/input.tsx:158— core/src/components/input/input.tsx:158 · core/src/components/textarea/textarea.tsx:123 — the two spans are one implementation copied and then locally edited — 1022 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 (103 matched lines × 2 locations) · ×1
Duplicated block with local edits (103 matched lines × 2 locations) core/src/components/checkbox/checkbox.tsx:88— core/src/components/checkbox/checkbox.tsx:88 · core/src/components/toggle/toggle.tsx:106 — the two spans are one implementation copied and then locally edited — 610 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (100 matched lines × 2 locations) · ×1
Duplicated block with local edits (100 matched lines × 2 locations) core/src/components/input/input.tsx:811— core/src/components/input/input.tsx:811 · core/src/components/textarea/textarea.tsx:626 — the two spans are one implementation copied and then locally edited — 685 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 (81 lines × 2 locations) core/src/components/modal/animations/ios.transition.ts:17— core/src/components/modal/animations/ios.transition.ts:17 · core/src/components/modal/animations/ios.transition.ts:108 — 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.
Wholesale file copy (75 identical lines × 2 files) packages/react/src/components/createOverlayComponent.tsx:2— packages/react/src/components/createOverlayComponent.tsx:2 · packages/react/src/components/react-component-lib/createOverlayComponent.tsx:1 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) core/src/components/popover/animations/ios.enter.ts:26— core/src/components/popover/animations/ios.enter.ts:26 · core/src/components/popover/animations/md.enter.ts:14 — the two spans are one implementation copied and then locally edited — 415 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 (65 matched lines × 2 locations) · ×1
Duplicated block with local edits (65 matched lines × 2 locations) core/src/components/select-modal/select-modal.tsx:75— core/src/components/select-modal/select-modal.tsx:75 · core/src/components/select-popover/select-popover.tsx:85 — the two spans are one implementation copied and then locally edited — 378 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 (63 matched lines × 2 locations) · ×1
Duplicated block with local edits (63 matched lines × 2 locations) core/src/components/input/input.tsx:645— core/src/components/input/input.tsx:645 · core/src/components/textarea/textarea.tsx:534 — the two spans are one implementation copied and then locally edited — 368 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 (59 matched lines × 2 locations) · ×1
Duplicated block with local edits (59 matched lines × 2 locations) packages/react/src/routing/OutletPageManager.tsx:10— packages/react/src/routing/OutletPageManager.tsx:10 · packages/react/src/routing/PageManager.tsx:9 — the two spans are one implementation copied and then locally edited — 363 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 (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) core/src/components/searchbar/searchbar.tsx:142— core/src/components/searchbar/searchbar.tsx:142 · core/src/components/textarea/textarea.tsx:157 — the two spans are one implementation copied and then locally edited — 368 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 (53 lines × 2 locations) core/src/components/select-modal/select-modal.tsx:162— core/src/components/select-modal/select-modal.tsx:162 · core/src/components/select-popover/select-popover.tsx:126 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) packages/react/src/routing/LocationHistory.ts:41— packages/react/src/routing/LocationHistory.ts:41 · packages/vue-router/src/locationHistory.ts:30 — the two spans are one implementation copied and then locally edited — 290 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) core/src/components/loading/loading.tsx:46— core/src/components/loading/loading.tsx:46 · core/src/components/toast/toast.tsx:67 — the two spans are one implementation copied and then locally edited — 437 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 (49 lines × 2 locations) core/src/components/datetime/datetime.tsx:2019— core/src/components/datetime/datetime.tsx:2019 · core/src/components/datetime/datetime.tsx:2068 — 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 (43 lines × 2 locations) core/src/components/datetime/datetime.tsx:2151— core/src/components/datetime/datetime.tsx:2151 · core/src/components/datetime/datetime.tsx:2194 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (42 lines × 2 locations) core/src/components/button/button.tsx:239— core/src/components/button/button.tsx:239 · core/src/components/fab-button/fab-button.tsx:196 — 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 (37 lines × 2 locations) packages/angular/src/lazy/directives/angular-component-lib/utils.ts:22— packages/angular/src/lazy/directives/angular-component-lib/utils.ts:22 · packages/angular/src/standalone/directives/angular-component-lib/utils.ts:22 — 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 (34 lines × 3 locations) packages/react-router/src/ReactRouter/IonReactHashRouter.tsx:14— packages/react-router/src/ReactRouter/IonReactHashRouter.tsx:14 · packages/react-router/src/ReactRouter/IonReactMemoryRouter.tsx:15 · packages/react-router/src/ReactRouter/IonReactRouter.tsx:24 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (34 lines × 2 locations) packages/react/eslint.config.js:4— packages/react/eslint.config.js:4 · packages/vue/eslint.config.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (32 lines × 2 locations) packages/react-router/eslint.config.js:4— packages/react-router/eslint.config.js:4 · packages/vue-router/eslint.config.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (28 matched lines × 2 locations) · ×1
Duplicated block with local edits (28 matched lines × 2 locations) core/src/components/modal/animations/ios.enter.ts:50— core/src/components/modal/animations/ios.enter.ts:50 · core/src/components/modal/animations/ios.leave.ts:37 — the two spans are one implementation copied and then locally edited — 196 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 × 2 locations) core/src/components/card-subtitle/card-subtitle.tsx:12— core/src/components/card-subtitle/card-subtitle.tsx:12 · core/src/components/card-title/card-title.tsx:12 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (24 lines × 3 locations) core/src/components/action-sheet/action-sheet.tsx:131— core/src/components/action-sheet/action-sheet.tsx:131 · core/src/components/alert/alert.tsx:144 · core/src/components/loading/loading.tsx:116 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (24 matched lines × 2 locations) · ×1
Duplicated block with local edits (24 matched lines × 2 locations) core/src/components/back-button/back-button.tsx:26— core/src/components/back-button/back-button.tsx:26 · core/src/components/menu-button/menu-button.tsx:27 — the two spans are one implementation copied and then locally edited — 140 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 (21 lines × 2 locations) core/src/components/loading/animations/ios.enter.ts:8— core/src/components/loading/animations/ios.enter.ts:8 · core/src/components/loading/animations/md.enter.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.
Complex function handleHistoryChange (cyclomatic 55, cognitive 98) packages/vue-router/src/router.ts:458— handleHistoryChange has cyclomatic complexity 55 and cognitive complexity 98; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 renderViewItem (cyclomatic 46, cognitive 57) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:435— renderViewItem has cyclomatic complexity 46 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleHistoryChange (cyclomatic 45, cognitive 78) packages/react-router/src/ReactRouter/IonRouter.tsx:165— handleHistoryChange has cyclomatic complexity 45 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderKnob (cyclomatic 43, cognitive 30) core/src/components/range/range.tsx:1093— renderKnob has cyclomatic complexity 43 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 66) packages/react-router/src/ReactRouter/utils/computeParentPath.ts:240— (anonymous) has cyclomatic complexity 31 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 31, cognitive 42) · ×1
Complex function main (cyclomatic 31, cognitive 42) packages/migrate/src/main.ts:108— main has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function matchView (cyclomatic 30, cognitive 40) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:884— matchView has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 28, cognitive 31) core/src/components/input-otp/input-otp.tsx:634— (anonymous) has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 26, cognitive 35) core/src/components/datetime/datetime.tsx:2433— (anonymous) has cyclomatic complexity 26 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 (anonymous) (cyclomatic 25, cognitive 33) core/src/components/input-otp/input-otp.tsx:555— (anonymous) has cyclomatic complexity 25 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function detect (cyclomatic 24, cognitive 82) packages/migrate/src/migrations/v9/react-router-6-code.ts:111— detect has cyclomatic complexity 24 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 24, cognitive 32) core/src/utils/transition/ios.transition.ts:498— (anonymous) has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handlePageTransition (cyclomatic 24, cognitive 30) packages/vue/src/components/IonRouterOutlet.ts:279— handlePageTransition has cyclomatic complexity 24 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function setDateTimeText (cyclomatic 21, cognitive 23) core/src/components/datetime-button/datetime-button.tsx:191— setDateTimeText has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 22) core/src/components/datetime/utils/manipulation.ts:343— (anonymous) has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 21, cognitive 19) core/src/components/item/item.tsx:385— render has cyclomatic complexity 21 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 28) packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:319— (anonymous) has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function verify (cyclomatic 20, cognitive 24) REDACTED:88— verify has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 20, cognitive 22) core/src/components/picker-column/picker-column.tsx:482— (anonymous) has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function setNextIndex (cyclomatic 19, cognitive 29) core/src/components/segment/segment.tsx:506— setNextIndex has cyclomatic complexity 19 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 25) packages/react-router/src/ReactRouter/utils/pathMatching.ts:27— (anonymous) has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onEnd (cyclomatic 19, cognitive 18) core/src/components/menu/menu.tsx:618— onEnd has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function processValue (cyclomatic 19, cognitive 17) core/src/components/datetime/datetime.tsx:1419— processValue has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 onMove (cyclomatic 19, cognitive 17) core/src/components/modal/gestures/sheet.ts:355— onMove has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 callback (cyclomatic 19, cognitive 17) core/src/components/popover/utils.ts:461— callback has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 handleNavigate (cyclomatic 18, cognitive 24) packages/react-router/src/ReactRouter/IonRouter.tsx:587— handleNavigate has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 postViewInit (cyclomatic 18, cognitive 22) core/src/components/nav/nav.tsx:665— postViewInit has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 17) packages/react-router/src/ReactRouter/utils/viewItemUtils.ts:15— (anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 render (cyclomatic 18, cognitive 16) core/src/components/range/range.tsx:987— render has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 13) core/scripts/testing/scripts.js:23— (anonymous) has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateTime (cyclomatic 17, cognitive 33) core/src/components/datetime/utils/data.ts:202— generateTime has cyclomatic complexity 17 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function callProblems (cyclomatic 17, cognitive 24) packages/migrate/src/migrations/v9/react-overlay-hook-props-manual.ts:32— callProblems has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 findComponentDeclarations (cyclomatic 17, cognitive 20) REDACTED:40— findComponentDeclarations has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 checkConfig (cyclomatic 17, cognitive 20) packages/react/src/components/CreateAnimation.tsx:113— checkConfig has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 render (cyclomatic 17, cognitive 16) core/src/components/searchbar/searchbar.tsx:643— render has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 16) packages/react/src/components/createOverlayComponent.tsx:21— (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 17, cognitive 13) core/src/components/input/input.tsx:864— render has cyclomatic complexity 17 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function prepareTI (cyclomatic 16, cognitive 21) core/src/components/nav/nav.tsx:564— prepareTI has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onMove (cyclomatic 16, cognitive 17) core/src/components/refresher/refresher.tsx:680— onMove has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 16, cognitive 17) packages/react/src/components/react-component-lib/utils/attachProps.ts:44— (anonymous) has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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· core/src/components/datetime/datetime.tsx · ×1
core/src/components/datetime/datetime.tsx: 2575 lines of code core/src/components/datetime/datetime.tsx:1— core/src/components/datetime/datetime.tsx has 2575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react-router/src/ReactRouter/StackManager.tsx · ×1
packages/react-router/src/ReactRouter/StackManager.tsx: 1813 lines of code packages/react-router/src/ReactRouter/StackManager.tsx:1— packages/react-router/src/ReactRouter/StackManager.tsx has 1813 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· core/src/components/modal/modal.tsx · ×1
core/src/components/modal/modal.tsx: 1603 lines of code core/src/components/modal/modal.tsx:1— core/src/components/modal/modal.tsx has 1603 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· core/src/components/select/select.tsx · ×1
core/src/components/select/select.tsx: 1532 lines of code core/src/components/select/select.tsx:1— core/src/components/select/select.tsx has 1532 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· core/src/components/range/range.tsx · ×1
core/src/components/range/range.tsx: 1132 lines of code core/src/components/range/range.tsx:1— core/src/components/range/range.tsx has 1132 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/src/utils/overlays.ts: 1015 lines of code core/src/utils/overlays.ts:1— core/src/utils/overlays.ts has 1015 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· core/src/components/popover/utils.ts · ×1
core/src/components/popover/utils.ts: 1000 lines of code core/src/components/popover/utils.ts:1— core/src/components/popover/utils.ts has 1000 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/vue-router/src/router.ts · ×1
packages/vue-router/src/router.ts: 982 lines of code packages/vue-router/src/router.ts:1— packages/vue-router/src/router.ts has 982 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx · ×1
packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx: 977 lines of code packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:1— packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx has 977 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· core/src/components/nav/nav.tsx · ×1
core/src/components/nav/nav.tsx: 889 lines of code core/src/components/nav/nav.tsx:1— core/src/components/nav/nav.tsx has 889 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· core/src/components/alert/alert.tsx · ×1
core/src/components/alert/alert.tsx: 871 lines of code core/src/components/alert/alert.tsx:1— core/src/components/alert/alert.tsx has 871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/src/components/input/input.tsx · ×1
core/src/components/input/input.tsx: 853 lines of code core/src/components/input/input.tsx:1— core/src/components/input/input.tsx has 853 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· core/src/components/refresher/refresher.tsx · ×1
core/src/components/refresher/refresher.tsx: 845 lines of code core/src/components/refresher/refresher.tsx:1— core/src/components/refresher/refresher.tsx has 845 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· core/src/utils/animation/animation.ts · ×1
core/src/utils/animation/animation.ts: 818 lines of code core/src/utils/animation/animation.ts:1— core/src/utils/animation/animation.ts has 818 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· core/src/components/input-otp/input-otp.tsx · ×1
core/src/components/input-otp/input-otp.tsx: 796 lines of code core/src/components/input-otp/input-otp.tsx:1— core/src/components/input-otp/input-otp.tsx has 796 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· core/src/components/picker-column/picker-column.tsx · ×1
core/src/components/picker-column/picker-column.tsx: 789 lines of code core/src/components/picker-column/picker-column.tsx:1— core/src/components/picker-column/picker-column.tsx has 789 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· core/src/components/menu/menu.tsx · ×1
core/src/components/menu/menu.tsx: 779 lines of code core/src/components/menu/menu.tsx:1— core/src/components/menu/menu.tsx has 779 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· core/src/utils/transition/ios.transition.ts · ×1
core/src/utils/transition/ios.transition.ts: 734 lines of code core/src/utils/transition/ios.transition.ts:1— core/src/utils/transition/ios.transition.ts has 734 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· core/src/components/popover/popover.tsx · ×1
core/src/components/popover/popover.tsx: 725 lines of code core/src/components/popover/popover.tsx:1— core/src/components/popover/popover.tsx has 725 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· core/src/components/textarea/textarea.tsx · ×1
core/src/components/textarea/textarea.tsx: 724 lines of code core/src/components/textarea/textarea.tsx:1— core/src/components/textarea/textarea.tsx has 724 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· core/src/components/toast/toast.tsx · ×1
core/src/components/toast/toast.tsx: 696 lines of code core/src/components/toast/toast.tsx:1— core/src/components/toast/toast.tsx has 696 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react-router/src/ReactRouter/IonRouter.tsx · ×1
packages/react-router/src/ReactRouter/IonRouter.tsx: 668 lines of code packages/react-router/src/ReactRouter/IonRouter.tsx:1— packages/react-router/src/ReactRouter/IonRouter.tsx 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· core/src/components/searchbar/searchbar.tsx · ×1
core/src/components/searchbar/searchbar.tsx: 660 lines of code core/src/components/searchbar/searchbar.tsx:1— core/src/components/searchbar/searchbar.tsx has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/src/components/modal/gestures/sheet.ts · ×1
core/src/components/modal/gestures/sheet.ts: 653 lines of code core/src/components/modal/gestures/sheet.ts:1— core/src/components/modal/gestures/sheet.ts has 653 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/vue/src/components/IonRouterOutlet.ts · ×1
packages/vue/src/components/IonRouterOutlet.ts: 634 lines of code packages/vue/src/components/IonRouterOutlet.ts:1— packages/vue/src/components/IonRouterOutlet.ts has 634 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· core/src/components/action-sheet/action-sheet.tsx · ×1
core/src/components/action-sheet/action-sheet.tsx: 633 lines of code core/src/components/action-sheet/action-sheet.tsx:1— core/src/components/action-sheet/action-sheet.tsx has 633 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· core/src/components/content/content.tsx · ×1
core/src/components/content/content.tsx: 621 lines of code core/src/components/content/content.tsx:1— core/src/components/content/content.tsx has 621 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· core/src/components/segment/segment.tsx · ×1
core/src/components/segment/segment.tsx: 611 lines of code core/src/components/segment/segment.tsx:1— core/src/components/segment/segment.tsx has 611 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/angular/src/common/directives/navigation/router-outlet.ts · ×1
packages/angular/src/common/directives/navigation/router-outlet.ts: 608 lines of code packages/angular/src/common/directives/navigation/router-outlet.ts:1— packages/angular/src/common/directives/navigation/router-outlet.ts has 608 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· core/src/components/datetime/utils/data.ts · ×1
core/src/components/datetime/utils/data.ts: 601 lines of code core/src/components/datetime/utils/data.ts:1— core/src/components/datetime/utils/data.ts has 601 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· core/src/components/datetime/utils/manipulation.ts · ×1
core/src/components/datetime/utils/manipulation.ts: 517 lines of code core/src/components/datetime/utils/manipulation.ts:1— core/src/components/datetime/utils/manipulation.ts has 517 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· core/src/components/picker/picker.tsx · ×1
core/src/components/picker/picker.tsx: 509 lines of code core/src/components/picker/picker.tsx:1— core/src/components/picker/picker.tsx has 509 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· core/src/components/item/item.tsx · ×1
core/src/components/item/item.tsx: 486 lines of code core/src/components/item/item.tsx:1— core/src/components/item/item.tsx has 486 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· core/src/components/toggle/toggle.tsx · ×1
core/src/components/toggle/toggle.tsx: 479 lines of code core/src/components/toggle/toggle.tsx:1— core/src/components/toggle/toggle.tsx has 479 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· core/src/components/accordion/accordion.tsx · ×1
core/src/components/accordion/accordion.tsx: 457 lines of code core/src/components/accordion/accordion.tsx:1— core/src/components/accordion/accordion.tsx has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/src/components/item-sliding/item-sliding.tsx · ×1
core/src/components/item-sliding/item-sliding.tsx: 444 lines of code core/src/components/item-sliding/item-sliding.tsx:1— core/src/components/item-sliding/item-sliding.tsx has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/src/utils/sanitization/index.ts · ×1
core/src/utils/sanitization/index.ts: 423 lines of code core/src/utils/sanitization/index.ts:1— core/src/utils/sanitization/index.ts has 423 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· core/src/components/datetime-button/datetime-button.tsx · ×1
core/src/components/datetime-button/datetime-button.tsx: 420 lines of code core/src/components/datetime-button/datetime-button.tsx:1— core/src/components/datetime-button/datetime-button.tsx has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react/src/components/createInlineOverlayComponent.tsx · ×1
packages/react/src/components/createInlineOverlayComponent.tsx: 413 lines of code packages/react/src/components/createInlineOverlayComponent.tsx:1— packages/react/src/components/createInlineOverlayComponent.tsx has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/src/utils/helpers.ts: 405 lines of code core/src/utils/helpers.ts:1— core/src/utils/helpers.ts has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~969 LoC) core/src/components/refresher/refresher.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~516 LoC) core/src/components/item-sliding/item-sliding.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~471 LoC) core/src/components/datetime-button/datetime-button.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~433 LoC) core/src/components/router/router.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~381 LoC) core/src/components/reorder-group/reorder-group.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~353 LoC) core/src/utils/input-shims/hacks/scroll-assist.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/utils/input-shims/input-shims.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~344 LoC) core/src/components/router-outlet/router-outlet.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~284 LoC) core/src/components/header/header.utils.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/components/header/header.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~271 LoC) packages/vue/src/utils/overlays.ts— no import path from any entry point (142 application, 55 tooling, 1244 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 (~270 LoC) core/src/components/select-popover/select-popover.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~239 LoC) core/src/components/tabs/tabs.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~237 LoC) core/src/components/header/header.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~236 LoC) core/src/components/infinite-scroll/infinite-scroll.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~234 LoC) core/src/components/select-modal/select-modal.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~231 LoC) packages/angular/schematics/add/index.ts— no import path from any entry point (142 application, 55 tooling, 1244 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 (~203 LoC) core/src/components/split-pane/split-pane.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~181 LoC) core/src/utils/tap-click/index.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/components/app/app.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~164 LoC) core/src/components/img/img.tsx— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~163 LoC) core/src/components/segment-view/segment-view.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~152 LoC) core/src/components/tab-bar/tab-bar.tsx— no import path from any entry point (142 application, 55 tooling, 1244 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 (~150 LoC) packages/angular/schematics/utils/config.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/angular/schematics/add/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~144 LoC) core/src/utils/input-shims/input-shims.ts— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/src/components/app/app.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~130 LoC) core/src/components/app/app.tsx— no import path from any entry point (142 application, 55 tooling, 1244 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@capacitor/app' — Declared in packages/angular/test/code-split/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@capacitor/cli' — Declared in packages/angular/test/code-split/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vue/test-utils' — Declared in packages/vue/test/apps/vue3/package.json but never imported anywhere in that package or its workspace members — while packages/vue/test/base/tests/unit/deprecations.spec.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
`async` callback passed to `forEach` core/src/components/modal/modal.tsx:1398— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
Orphaned file core/src/components/accordion/accordion.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/datetime/utils/manipulation.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/reorder-group/reorder-group.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/datetime/utils/format.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/toast/gestures/swipe-to-dismiss.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/header/header.utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/accordion-group/accordion-group.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/refresher/refresher.utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/vue/src/utils/overlays.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/utils/gesture/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/infinite-scroll/infinite-scroll.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/datetime/utils/parse.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/header/header.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/angular/schematics/add/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/tabs/tabs.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/router/utils/matching.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/contexts/IonLifeCycleContext.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/utils/animation/animation-interface.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/datetime/utils/state.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/routing/PageManager.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/utils/keyboard/keyboard-controller.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/routing/LocationHistory.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/components/tab-button/tab-button.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/CreateAnimation.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/src/utils/forms/notch-controller.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.
redundant comment core/src/components/action-sheet/action-sheet.tsx:391— "Get all radio button elements and filter out disabled ones" repeats the code it sits on: 5 of its 6 words (radio, button, elements, filter, disabled) are already in `const radios = Array.from(this.el.querySelectorAll('.action-sheet-button[role="radio"]')).filter(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/button/test/form-reference/button.e2e.ts:158— "Set the form to have a submit button" repeats the code it sits on: 4 of its 4 words (set, form, submit, button) are already in `await page.setContent(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/button/test/form-reference/button.e2e.ts:188— "Expect hidden button type to be reset" repeats the code it sits on: 4 of its 5 words (expect, hidden, type, reset) are already in `await expect.poll(async () => await getHiddenType()).toBe('reset');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/datetime/test/datetime.e2e.ts:29— "Wait for the picker to be open" repeats the code it sits on: 3 of its 3 words (wait, picker, open) are already in `await page.locator('.month-year-picker-open').waitFor();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/datetime/test/datetime.e2e.ts:57— "Wait for the picker to be open" repeats the code it sits on: 3 of its 3 words (wait, picker, open) are already in `await page.locator('.month-year-picker-open').waitFor();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/datetime/test/show-adjacent-days/datetime.e2e.ts:67— "Wait for the datetime to be ready." repeats the code it sits on: 3 of its 3 words (wait, datetime, ready) are already in `await page.locator('.datetime-ready').waitFor();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/datetime/test/show-adjacent-days/datetime.e2e.ts:139— "Wait for the datetime to be ready." repeats the code it sits on: 3 of its 3 words (wait, datetime, ready) are already in `await page.locator('.datetime-ready').waitFor();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/header/test/condense-modal/header.e2e.ts:19— "Include both an MD header and an iOS modal to force both stylesheets to load" repeats the code it sits on: 7 of its 8 words (md, header, os, modal, force, stylesheets, load) are already in `await page.setContent(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/modal/modal.tsx:122— "Mutation observer to watch for parent removal" repeats the code it sits on: 4 of its 5 words (mutation, observer, parent, removal) are already in `private parentRemovalObserver?: MutationObserver;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/modal/modal.tsx:1275— "Portrait to landscape transition" repeats the code it sits on: 3 of its 3 words (portrait, landscape, transition) are already in `transitionAnimation = portraitToLandscapeTransition(this.el, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/modal/modal.tsx:1283— "Landscape to portrait transition" repeats the code it sits on: 3 of its 3 words (landscape, portrait, transition) are already in `transitionAnimation = landscapeToPortraitTransition(this.el, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/modal/test/inline/modal.e2e.ts:38— 8 comments in this file only repeat the code they sit on (lines 38, 50, 72, 142, 200, 208, 281, 289), for example "Open the child modal". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/range/test/range.spec.ts:634— "Blur the knob handle" repeats the code it sits on: 3 of its 3 words (blur, knob, handle) are already in `knobHandle.blur();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/range/test/range.spec.ts:775— "Blur knob handle B" repeats the code it sits on: 3 of its 3 words (blur, knob, handle) are already in `knobHandleB.blur();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/refresher/refresher.tsx:751— "set pull progress" repeats the code it sits on: 3 of its 3 words (set, pull, progress) are already in `this.progress = deltaY / pullMin;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/segment-view/segment-view.tsx:56— "Reset the timeout to check for scroll end" repeats the code it sits on: 4 of its 5 words (reset, timeout, scroll, end) are already in `this.resetScrollEndTimeout();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/segment-view/test/dynamic-height/segment-view.e2e.ts:56— "Click the third button" repeats the code it sits on: 3 of its 3 words (click, third, button) are already in `await page.locator('ion-segment-button[value="third"]').click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/segment/segment.tsx:371— "Get the first button with a contentId" repeats the code it sits on: 4 of its 5 words (first, button, content, id) are already in `const firstContentId = buttons.find((button: HTMLIonSegmentButtonElement) => button.contentId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/segment/segment.tsx:375— "Return the segment view for that matching segment content" repeats the code it sits on: 4 of its 5 words (return, segment, view, content) are already in `return segmentContent?.closest('ion-segment-view');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/components/select/test/rich-content-option/select.e2e.ts:98— 8 comments in this file only repeat the code they sit on (lines 98, 134, 174, 214, 250, 290, 326, 475), for example "Click on the first option". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/utils/animation/test/animation.spec.ts:37— "Expect that the promise resolves and returns undefined" repeats the code it sits on: 4 of its 5 words (expect, promise, resolves, undefined) are already in `expect(animationPromise).resolves.toEqual(undefined);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/utils/overlays.ts:298— "Focus the first element in the overlay wrapper" repeats the code it sits on: 4 of its 5 words (focus, first, overlay, wrapper) are already in `focusFirstDescendant(overlayWrapper, lastOverlay);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/utils/test/overlays/overlays.e2e.ts:301— "Wait for toast to be presented" repeats the code it sits on: 3 of its 3 words (wait, toast, presented) are already in `await ionToastDidPresent.next();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/utils/test/overlays/overlays.e2e.ts:364— "Wait for toast to be presented" repeats the code it sits on: 3 of its 3 words (wait, toast, presented) are already in `await ionToastDidPresent.next();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment core/src/utils/test/overlays/overlays.e2e.ts:418— "dismiss action sheet" repeats the code it sits on: 3 of its 3 words (dismiss, action, sheet) are already in `await actionSheet.evaluate((el: HTMLIonActionSheetElement) => el.dismiss());`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate core/src/components/select-modal/select-modal.tsx:104— `!!richOption.startContent || !!richOption.endContent || !!richOption.description` appears character-identically in 2 files — core/src/components/select-modal/select-modal.tsx, core/src/components/select-popover/select-popover.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 core/src/components/modal/animations/ios.enter.ts:38— `!expandToScroll && contentAnimation?.addElement(baseEl.querySelector('.ion-page')!)` appears character-identically in 2 files — core/src/components/modal/animations/ios.enter.ts, core/src/components/modal/animations/md.enter.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 core/src/components/select/select.tsx:385— `Build.isBrowser && getIonMode(this) === 'md' && this.fill === 'outline'` appears character-identically in 2 files — core/src/components/select/select.tsx, core/src/components/textarea/textarea.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 core/src/components/checkbox/checkbox.tsx:155— `Build.isBrowser && typeof MutationObserver !== 'undefined'` appears character-identically in 6 files — core/src/components/checkbox/checkbox.tsx, core/src/components/radio-group/radio-group.tsx, core/src/components/range/range.tsx, core/src/components/select/select.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react-router/src/ReactRouter/StackManager.tsx:449— `React.isValidElement(child) && (child.type === Route || child.type === IonRoute)` appears character-identically in 2 files — packages/react-router/src/ReactRouter/StackManager.tsx, packages/react-router/src/ReactRouter/utils/routeElements.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 core/src/components/nav/nav.tsx:761— `ani !== undefined && !this.gestureOrAnimationInProgress` appears character-identically in 2 files — core/src/components/nav/nav.tsx, core/src/components/router-outlet/router-outlet.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 core/src/utils/gesture/index.ts:265— `changedTouches && changedTouches.length > 0` appears character-identically in 2 files — core/src/utils/gesture/index.ts, core/src/utils/helpers.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/react-router/src/ReactRouter/IonRouter.tsx:370— `currentPushedBy !== undefined && currentPushedBy !== routeInfo.pathname` appears character-identically in 2 files — packages/react-router/src/ReactRouter/IonRouter.tsx, packages/vue-router/src/router.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/react-router/src/ReactRouter/IonRouter.tsx:374— `currentRouteInfo?.pathname || routeInfo.lastPathname` appears character-identically in 2 files — packages/react-router/src/ReactRouter/IonRouter.tsx, packages/vue-router/src/router.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/angular/src/lazy/directives/angular-component-lib/utils.ts:42— `customElement !== undefined && typeof customElements !== 'undefined' && !customElements.get(tagName)` appears character-identically in 3 files — packages/angular/src/lazy/directives/angular-component-lib/utils.ts, packages/angular/src/standalone/directives/angular-component-lib/utils.ts, packages/react/src/components/react-component-lib/utils/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/utils/framework-delegate.ts:131— `document.querySelector('ion-app') || document.body` appears character-identically in 2 files — core/src/utils/framework-delegate.ts, packages/react/src/components/createInlineOverlayComponent.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 core/src/components/button/button.tsx:183— `formButtonEl !== null && formEl.contains(formButtonEl)` appears character-identically in 2 files — core/src/components/button/button.tsx, core/src/components/fab-button/fab-button.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 core/src/components/select/select.tsx:1411— `hasOutlineFill && this.renderOutlineContainer()` appears character-identically in 2 files — core/src/components/select/select.tsx, core/src/components/textarea/textarea.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 core/src/components/menu-button/menu-button.tsx:104— `inheritedAttributes['aria-label'] || 'menu'` appears character-identically in 2 files — core/src/components/menu-button/menu-button.tsx, core/src/components/menu/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 core/src/components/checkbox/checkbox.tsx:361— `inheritedAttributes['aria-label'] || null` appears character-identically in 3 files — core/src/components/checkbox/checkbox.tsx, core/src/components/picker-column-option/picker-column-option.tsx, core/src/components/toggle/toggle.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/components/footer/footer.tsx:62— `keyboardOpen === false && waitForResize !== undefined` appears character-identically in 2 files — core/src/components/footer/footer.tsx, core/src/components/tab-bar/tab-bar.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/migrate/src/migrations/v9/angular-browser-policy-manual.ts:29— `major === undefined || major < BROWSER_POLICY_ANGULAR` appears character-identically in 2 files — packages/migrate/src/migrations/v9/angular-browser-policy-manual.ts, packages/migrate/src/migrations/v9/angular-browser-policy.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 core/src/components/select/select.tsx:1377— `mode === 'md' && fill !== 'outline' && !inItem` appears character-identically in 2 files — core/src/components/select/select.tsx, core/src/components/textarea/textarea.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react/src/components/createInlineOverlayComponent.tsx:326— `name.indexOf('on') === 0 && name[2] === name[2].toUpperCase()` appears character-identically in 5 files — packages/react/src/components/createInlineOverlayComponent.tsx, packages/react/src/components/createRoutingComponent.tsx, packages/react/src/components/react-component-lib/createComponent.tsx, packages/react/src/components/react-component-lib/utils/attachProps.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 core/src/components/nav/nav.tsx:795— `opts.animationBuilder || this.animation || config.get('navAnimation')` appears character-identically in 2 files — core/src/components/nav/nav.tsx, core/src/components/router-outlet/router-outlet.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 core/src/components/modal/modal.tsx:606— `parentEl !== null && !this.hasController` appears character-identically in 2 files — core/src/components/modal/modal.tsx, core/src/components/popover/popover.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx:1084— `parentPath && routePath && !routePath.startsWith('/')` appears character-identically in 2 files — packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx, packages/react-router/src/ReactRouter/StackManager.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react-router/src/ReactRouter/StackManager.tsx:454— `path && !path.startsWith('/') && path !== '*'` appears character-identically in 2 files — packages/react-router/src/ReactRouter/StackManager.tsx, packages/react-router/src/ReactRouter/utils/computeParentPath.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 core/src/components/modal/animations/ios.enter.ts:53— `presentingEl.tagName === 'ION-MODAL' && (presentingEl as HTMLIonModalElement).presentingElement !== undefined` appears character-identically in 3 files — core/src/components/modal/animations/ios.enter.ts, core/src/components/modal/animations/ios.leave.ts, core/src/components/modal/animations/ios.transition.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/react/src/components/createControllerComponent.tsx:75— `prevProps.isOpen !== this.props.isOpen && this.props.isOpen === true` appears character-identically in 3 files — packages/react/src/components/createControllerComponent.tsx, packages/react/src/components/createOverlayComponent.tsx, packages/react/src/components/react-component-lib/createOverlayComponent.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.
Disabled test core/src/components/accordion/test/a11y/accordion.e2e.ts:7— 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 core/src/components/fab/test/custom-size/fab.e2e.ts:10— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test core/src/components/picker-column/test/basic/picker-column.e2e.ts:40— 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 core/src/components/picker-column/test/basic/picker-column.e2e.ts:66— 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 core/src/components/popover/test/basic/popover.e2e.ts:33— 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 core/src/components/select-modal/test/basic/select-modal.e2e.ts:23— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test core/src/components/select-modal/test/basic/select-modal.e2e.ts:58— 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 core/src/components/select-modal/test/basic/select-modal.e2e.ts:87— 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 core/src/components/select-popover/test/basic/select-popover.e2e.ts:23— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test core/src/components/select-popover/test/basic/select-popover.e2e.ts:58— 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 core/src/components/select-popover/test/basic/select-popover.e2e.ts:87— 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 core/src/utils/focus-controller/test/generic/focus-controller.e2e.ts:48— 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 core/src/utils/focus-controller/test/ionic/focus-controller.e2e.ts:48— 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/react/test/base/tests/e2e/specs/overlay-hooks/useIonModal.cy.ts:65— 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/react/test/base/tests/e2e/specs/tabs/tabs.cy.ts:68— 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/vue/test/base/tests/e2e/specs/hbb.cy.js:63— 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/vue/test/base/tests/e2e/specs/routing.cy.js:575— 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/vue/test/base/tests/e2e/specs/tabs.cy.js:698— 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/vue/test/base/tests/e2e/specs/tabs.cy.js:717— 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/vue/test/base/tests/e2e/specs/tabs.cy.js:728— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Blanket warning suppression packages/angular/src/common/utils/proxy.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/angular/src/lazy/directives/angular-component-lib/boolean-attribute.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/angular/src/lazy/directives/angular-component-lib/utils.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/angular/src/standalone/directives/angular-component-lib/boolean-attribute.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/angular/src/standalone/directives/angular-component-lib/utils.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/react/src/components/components.ts:8— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Mock-dominated test: should fire lifecycle events on inner tab page packages/vue/test/base/tests/unit/lifecycle.spec.ts:101— This test sets up 12 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 28 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should add event on sync and readd on additional syncs packages/react/src/components/__tests__/utils.spec.ts:15— This test sets up 3 test doubles (for example `jest.spyOn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log the error core/src/components/tab/test/tab.spec.ts:139— This test sets up 3 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Documentation: no build, run or usage example packages/angular-server/readme.md:1— `angular-server` is a published package (`package.json` without `"private": true`) and neither `packages/angular-server/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/docs/README.md:1— `docs` is a published package (`package.json` without `"private": true`) and neither `packages/docs/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/react-router/README.md:1— `react-router` is a published package (`package.json` without `"private": true`) and neither `packages/react-router/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.
Hand-rolled JSON/XML parsing via regex packages/migrate/src/migrations/v9/angular-module-resolution.ts:18— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/migrate/src/migrations/v9/angular-module-resolution.ts:25— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/migrate/src/ast/browserslist.ts:91— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Fat interface: MenuControllerI (17 required operations) core/src/components/menu/menu-interface.ts:28— `MenuControllerI` declares 17 required operations: `registerAnimation`, `get`, `getMenus`, `getOpen`, `isEnabled`, `swipeGesture`, `isAnimating`, `isOpen`, `enable`, `toggle`, `close`, `open`, `_getOpenSync`, `_createAnimation`, `_register`, `_unregister`, `_setOpen`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Animation (44 required operations) core/src/utils/animation/animation-interface.ts:3— `Animation` declares 44 required operations: `play`, `pause`, `stop`, `destroy`, `progressStart`, `progressStep`, `progressEnd`, `from`, `to`, `fromTo`, `keyframes`, `addAnimation`, `addElement`, `iterations`, `fill`, `direction`, `duration`, `easing`, `delay`, `getKeyframes`, `getDirection`, `getFill`, `getDelay`, `getIterations`, `getEasing`, `getDuration`, `getWebAnimations`, `afterAddRead`, `afterAddWrite`, `afterClearStyles`, `afterStyles`, `afterAddClass`, `afterRemoveClass`, `beforeAddRead`, `beforeAddWrite`, `beforeClearStyles`, `beforeStyles`, `beforeAddClass`, `beforeRemoveClass`, `onFinish`, and 4 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: packages/react-router/src/ReactRouter/ReactRouterViewStack.tsx, packages/migrate/src/migrations/v9/angular-zoneless.ts, packages/migrate/src/main.ts, packages/react/src/components/react-component-lib/utils/attachProps.ts, packages/angular/src/common/directives/navigation/router-link-delegate.ts, packages/migrate/src/ast/deps-migration.ts, packages/migrate/src/detect.ts, packages/migrate/src/migrations/index.ts (+1 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/angular/src/lazy/index.ts, packages/angular/src/lazy/ionic-module.ts, core/src/utils/forms/click-controller.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (15 single-owned of 210 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; 210 of the 543 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (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/angular/src/common/providers/nav-controller.ts, core/src/components/tab-bar/tab-bar.tsx, packages/angular-server/src/ionic-server-module.ts.
No ADRs found packages/migrate/package.json:30— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/migrate/package.json` makes this repository a deployable product (line 30).
D21 · Naming Consistency· `configFromURL` spells `URL` where 20 names in the project spell it `Url` · ×1
`configFromURL` spells `URL` where 20 names in the project spell it `Url` core/src/global/config.ts:57— 20 of 22 names in project repository spell the token `Url` (20 of 22; unit: names in project repository containing `Url`). Peers: path.generateUrl (core/src/components/router/utils/path.ts:11); RouterLinkDelegateDirective.updateTargetUrlAndHref (packages/angular/src/common/directives/navigation/router-link-delegate.ts:112); RouterLinkWithHrefDelegateDirective.updateTargetUrlAndHref (packages/angular/src/common/directives/navigation/router-link-delegate.ts:164); IonRouterOutlet.getLastUrl (packages/angular/src/common/directives/navigation/router-outlet.ts:492); StackController.getLastUrl (packages/angular/src/common/directives/navigation/stack-controller.ts:210). Rename to `configFromUrl`. [rule N6]
D21 · Naming Consistency· `openURL` spells `URL` where 20 names in the project spell it `Url` · ×1
`openURL` spells `URL` where 20 names in the project spell it `Url` core/src/utils/theme.ts:40— 20 of 22 names in project repository spell the token `Url` (20 of 22; unit: names in project repository containing `Url`). Peers: path.generateUrl (core/src/components/router/utils/path.ts:11); RouterLinkDelegateDirective.updateTargetUrlAndHref (packages/angular/src/common/directives/navigation/router-link-delegate.ts:112); RouterLinkWithHrefDelegateDirective.updateTargetUrlAndHref (packages/angular/src/common/directives/navigation/router-link-delegate.ts:164); IonRouterOutlet.getLastUrl (packages/angular/src/common/directives/navigation/router-outlet.ts:492); StackController.getLastUrl (packages/angular/src/common/directives/navigation/stack-controller.ts:210). Rename to `openUrl`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 10 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `core` (47796 LoC, 418 module-visible types across 129 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.
Pass-through layer packages/angular/src/common/providers/menu-controller.ts:3— MenuController: all 17 public methods forward their arguments unchanged to menuController and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call menuController directly, or give the layer a job.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 74 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: core/src/components/accordion/accordion.tsx, core/src/components/datetime/utils/manipulation.ts, core/src/components/reorder-group/reorder-group.tsx, core/src/components/datetime/utils/format.ts, core/src/components/toast/gestures/swipe-to-dismiss.ts, core/src/components/header/header.utils.ts, core/src/components/accordion-group/accordion-group.tsx, core/src/components/refresher/refresher.utils.ts (and 66 more) (77 orphaned of 211 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; 211 of the 543 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No dependency-update automation package.json:4— `package.json` 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.
No security response headers detected core/vercel.json:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 25/28 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~6.7 `!` null assertions per 1k TypeScript source lines — 535 assertion(s) across the 80227 source line(s) of the 519 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: core/src/components/datetime/datetime.tsx (21), core/src/components/modal/modal.tsx (21), core/src/components/nav/nav.tsx (21). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default in catch core/src/global/config.ts:44— `configFromSession` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
doc comments repeat the names packages/angular/schematics/add/index.ts:47— 2 of 16 documented parameters and 1 of 164 summaries in `@ionic/angular` only repeat the member or parameter name (e.g. "The name of the project." for `projectName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names core/src/components/button/button.tsx:56— 6 of 248 documented parameters and 3 of 1991 summaries in `@ionic/core` only repeat the member or parameter name (e.g. "The type of button." for `buttonType`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/react-router/src/ReactRouter/IonRouter.tsx:420— 3 of 53 documented parameters and 1 of 196 summaries in `@ionic/react-router` only repeat the member or parameter name (e.g. "Handles tab changes." for `handleChangeTab`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/vue/src/components/IonTabBar.ts:173— 0 of 1 documented parameters and 0 of 56 summaries in `@ionic/vue` only repeat the member or parameter name (e.g. "" for `ionRouter`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Skipped (documented): (unnamed test) packages/react-router/test/base/src/pages/modal-aria-hidden/ModalAriaHidden.tsx:44— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/vue/types/proxies.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a1da3d-0946-7303-9da7-d044fa8a5e56 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 60 · Warnings: 956 · Recommendations: 227 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 13:26 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.