Public report of emberjs/ember.js, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 17 November 2026, 05:03 UTC · Survey ID cd_72b4a70a44904ea5aebd4a4f993cab39
emberjs/ember.js
Measured 17 November 2026, 04:59 UTC, at code version a8dde59
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
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: 93,874 lines of product code in 60 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Architecture, 44.5
Findings by how serious they are
89 critical573 serious419 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
17 November 2026, 04:59 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 ▸
68of 68 dimensions measured by tools.
1043of 1081 findings point to an exact file and line, so you can open each one in the code. The other 38 concern the repository as a whole, such as missing documentation.
68dimensions across 6 lenses, read from 93,874 lines of product code in 60 projects.
emberjs/ember.js is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has pieces of product code that depend on test code. It scores 52.0 out of 100, which the At risk rating leaves unchanged.
Architecture, at 44.5, is the weakest lens and counts most in the score. The best first steps are removing the test references and breaking the import cycles, each worth about 6.1 points. Raising Architecture to 70 would lift the score to about 58.5.
Forty-two known security holes in the packages the code depends on can be used by attackers. Five places in the code run text as code, which an attacker could use, and six parts of the code are no longer understood by anyone working on it. Updating the vulnerable packages, replacing text run as code with direct calls and having someone learn the forgotten files would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code. The 18 pieces of product code that depend on test code need their reference to the test project removed.
The product code is 93,874 lines, about €200,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 Architecture rose from 44.5 to 70, the lowest score rated Strong, the score would rise from 52.0 to about 58.5.
Code composition: what the lines of code are
Product code 45%Tests 55%
Rebuild cost: about €200,000 · Estimate
Cost to rebuild
€67,000 to €340,000, for 1,117 to 3,542 hours of work, about 1.4 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: 93,874 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
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Raises the score by about 6.1 points · Medium effort · Test isolation
2
Break each cycle by extracting the shared piece into a module both sides can import.
Raises the score by about 6.1 points · Medium effort · Circular Imports
3
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with destroyables-test.ts.
Raises the score by about 2.5 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 €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Architecture, at 44.5 (Weak). Architecture is about whether the structure holds up as the product grows, and when the structure is weak, a change in one place ripples into many others. Because the weakest lens counts most in the score, work on Architecture also moves the score most.
Based on: the rebuild estimate · the Architecture grade · how much each lens counts
What to do: Start with the Architecture actions in Top priorities.
If you do one thing first · First action
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse. Of all the actions in this report, it raises the score most for the work it takes: about 6.1 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.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 79,930 lines over the last 90 days, which is about 324,161 lines a year. At that pace, the extra work comes to an estimated 16.2 to 108.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
391 modules, with 677 dependencies between them. 5 loops run through 24 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 351 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
packages.@ember.-internals.container.lib.container uses packages.@ember.-internals.owner, so a change to packages.@ember.-internals.owner can break packages.@ember.-internals.container.lib.container, while a change to packages.@ember.-internals.container.lib.container can't break packages.@ember.-internals.owner.
Position
Below the diagonal: packages.@ember.-internals.container.lib.container uses a module listed above it, which is the healthy direction.
packages.@ember.-internals.glimmer.lib.renderer uses packages.@ember.-internals.owner, so a change to packages.@ember.-internals.owner can break packages.@ember.-internals.glimmer.lib.renderer, while a change to packages.@ember.-internals.glimmer.lib.renderer can't break packages.@ember.-internals.owner.
Position
Below the diagonal: packages.@ember.-internals.glimmer.lib.renderer uses a module listed above it, which is the healthy direction.
packages.@ember.-internals.glimmer.lib.renderer uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@ember.-internals.glimmer.lib.renderer, while a change to packages.@ember.-internals.glimmer.lib.renderer can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@ember.-internals.glimmer.lib.renderer uses a module listed above it, which is the healthy direction.
packages.@ember.-internals.glimmer.lib.renderer uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@ember.-internals.glimmer.lib.renderer, while a change to packages.@ember.-internals.glimmer.lib.renderer can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@ember.-internals.glimmer.lib.renderer uses a module listed above it, which is the healthy direction.
packages.@glimmer.compiler.lib.builder.builder-interface uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.compiler.lib.builder.builder-interface, while a change to packages.@glimmer.compiler.lib.builder.builder-interface can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.compiler.lib.builder.builder-interface uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.element-builder uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.runtime.lib.vm.element-builder, while a change to packages.@glimmer.runtime.lib.vm.element-builder can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.element-builder uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in packages.@glimmer.runtime.lib.vm.element-builder uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.runtime.lib.vm.element-builder uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.runtime.lib.vm.element-builder, while a change to packages.@glimmer.runtime.lib.vm.element-builder can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.element-builder uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.element-builder uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.@glimmer.runtime.lib.vm.element-builder, while a change to packages.@glimmer.runtime.lib.vm.element-builder can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.element-builder uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.symbol-table uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.@glimmer.syntax.lib.symbol-table, while a change to packages.@glimmer.syntax.lib.symbol-table can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.@glimmer.syntax.lib.symbol-table uses a module listed above it, which is the healthy direction.
packages.router_js.lib.route-info uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.router_js.lib.route-info, while a change to packages.router_js.lib.route-info can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.router_js.lib.route-info uses a module listed above it, which is the healthy direction.
packages.router_js.lib.transition-state uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.router_js.lib.transition-state, while a change to packages.router_js.lib.transition-state can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.router_js.lib.transition-state uses a module listed above it, which is the healthy direction.
15→19 packages.router_js.lib.transition-state uses packages.router_js.lib.transitionpart of a loop✕
Connections
1 pair of types, where a type in packages.router_js.lib.transition-state uses a type in packages.router_js.lib.transition.
packages.router_js.lib.transition-state uses packages.router_js.lib.transition, so a change to packages.router_js.lib.transition can break packages.router_js.lib.transition-state, while a change to packages.router_js.lib.transition-state can't break packages.router_js.lib.transition.
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.@ember.-internals.metal.lib uses internal-docs.guides.reactivity.pseudocode.tags, so a change to internal-docs.guides.reactivity.pseudocode.tags can break packages.@ember.-internals.metal.lib, while a change to packages.@ember.-internals.metal.lib can't break internal-docs.guides.reactivity.pseudocode.tags.
Position
Below the diagonal: packages.@ember.-internals.metal.lib uses a module listed above it, which is the healthy direction.
packages.@ember.-internals.metal.lib uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@ember.-internals.metal.lib, while a change to packages.@ember.-internals.metal.lib can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@ember.-internals.metal.lib uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.update uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.runtime.lib.vm.update, while a change to packages.@glimmer.runtime.lib.vm.update can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.update uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.update uses packages.@ember.-internals.glimmer.lib.renderer, so a change to packages.@ember.-internals.glimmer.lib.renderer can break packages.@glimmer.runtime.lib.vm.update, while a change to packages.@glimmer.runtime.lib.vm.update can't break packages.@ember.-internals.glimmer.lib.renderer.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.update uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.update uses packages.@glimmer.runtime.lib.vm.element-builder, so a change to packages.@glimmer.runtime.lib.vm.element-builder can break packages.@glimmer.runtime.lib.vm.update, while a change to packages.@glimmer.runtime.lib.vm.update can't break packages.@glimmer.runtime.lib.vm.element-builder.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.update uses a module listed above it, which is the healthy direction.
17→23 packages.@glimmer.runtime.lib.vm.update uses packages.@glimmer.runtime.lib.vm.appendpart of a loop✕
Connections
3 pairs of types, where a type in packages.@glimmer.runtime.lib.vm.update uses a type in packages.@glimmer.runtime.lib.vm.append.
packages.@glimmer.runtime.lib.vm.update uses packages.@glimmer.runtime.lib.vm.append, so a change to packages.@glimmer.runtime.lib.vm.append can break packages.@glimmer.runtime.lib.vm.update, while a change to packages.@glimmer.runtime.lib.vm.update can't break packages.@glimmer.runtime.lib.vm.append.
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.
5 pairs of types, where a type in packages.@glimmer.syntax.lib.v1.handlebars-ast uses a type in packages.@glimmer.compiler.lib.builder.builder-interface.
packages.@glimmer.syntax.lib.v1.handlebars-ast uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@glimmer.syntax.lib.v1.handlebars-ast, while a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.handlebars-ast uses a module listed above it, which is the healthy direction.
packages.router_js.lib.transition uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.router_js.lib.transition, while a change to packages.router_js.lib.transition can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.router_js.lib.transition uses a module listed above it, which is the healthy direction.
packages.router_js.lib.transition uses packages.router_js.lib.route-info, so a change to packages.router_js.lib.route-info can break packages.router_js.lib.transition, while a change to packages.router_js.lib.transition can't break packages.router_js.lib.route-info.
Position
Below the diagonal: packages.router_js.lib.transition uses a module listed above it, which is the healthy direction.
packages.router_js.lib.transition uses packages.router_js.lib.transition-state, so a change to packages.router_js.lib.transition-state can break packages.router_js.lib.transition, while a change to packages.router_js.lib.transition can't break packages.router_js.lib.transition-state.
Position
Below the diagonal: packages.router_js.lib.transition uses a module listed above it, which is the healthy direction.
packages.@ember.routing.router uses packages.@ember.-internals.owner, so a change to packages.@ember.-internals.owner can break packages.@ember.routing.router, while a change to packages.@ember.routing.router can't break packages.@ember.-internals.owner.
Position
Below the diagonal: packages.@ember.routing.router uses a module listed above it, which is the healthy direction.
packages.@ember.routing.router uses packages.router_js.lib.route-info, so a change to packages.router_js.lib.route-info can break packages.@ember.routing.router, while a change to packages.@ember.routing.router can't break packages.router_js.lib.route-info.
Position
Below the diagonal: packages.@ember.routing.router uses a module listed above it, which is the healthy direction.
packages.@ember.routing.router uses packages.router_js.lib.transition-state, so a change to packages.router_js.lib.transition-state can break packages.@ember.routing.router, while a change to packages.@ember.routing.router can't break packages.router_js.lib.transition-state.
Position
Below the diagonal: packages.@ember.routing.router uses a module listed above it, which is the healthy direction.
packages.@ember.routing.router uses packages.router_js.lib.transition, so a change to packages.router_js.lib.transition can break packages.@ember.routing.router, while a change to packages.@ember.routing.router can't break packages.router_js.lib.transition.
Position
Below the diagonal: packages.@ember.routing.router uses a module listed above it, which is the healthy direction.
packages.@glimmer.debug.lib uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.debug.lib, while a change to packages.@glimmer.debug.lib can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.debug.lib uses a module listed above it, which is the healthy direction.
packages.@glimmer.debug.lib uses packages.@glimmer.debug.lib.render.fragment, so a change to packages.@glimmer.debug.lib.render.fragment can break packages.@glimmer.debug.lib, while a change to packages.@glimmer.debug.lib can't break packages.@glimmer.debug.lib.render.fragment.
Position
Below the diagonal: packages.@glimmer.debug.lib uses a module listed above it, which is the healthy direction.
packages.@glimmer.debug.lib uses packages.router_js.lib.core, so a change to packages.router_js.lib.core can break packages.@glimmer.debug.lib, while a change to packages.@glimmer.debug.lib can't break packages.router_js.lib.core.
Position
Below the diagonal: packages.@glimmer.debug.lib uses a module listed above it, which is the healthy direction.
packages.@glimmer.debug.lib uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.debug.lib, while a change to packages.@glimmer.debug.lib can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.debug.lib uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a type in packages.@ember.-internals.utility-types.
packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers, while a change to packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers, while a change to packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a type in packages.@glimmer.compiler.lib.builder.builder-interface.
packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers, while a change to packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a type in packages.@glimmer.syntax.lib.v1.handlebars-ast.
packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers, while a change to packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.opcode-compiler.lib.opcode-builder.helpers uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.append uses packages.@ember.-internals.owner, so a change to packages.@ember.-internals.owner can break packages.@glimmer.runtime.lib.vm.append, while a change to packages.@glimmer.runtime.lib.vm.append can't break packages.@ember.-internals.owner.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.append uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.append uses packages.@ember.-internals.glimmer.lib.renderer, so a change to packages.@ember.-internals.glimmer.lib.renderer can break packages.@glimmer.runtime.lib.vm.append, while a change to packages.@glimmer.runtime.lib.vm.append can't break packages.@ember.-internals.glimmer.lib.renderer.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.append uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.append uses packages.@glimmer.runtime.lib.vm.update, so a change to packages.@glimmer.runtime.lib.vm.update can break packages.@glimmer.runtime.lib.vm.append, while a change to packages.@glimmer.runtime.lib.vm.append can't break packages.@glimmer.runtime.lib.vm.update.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.append uses a module listed above it, which is the healthy direction.
packages.@glimmer.runtime.lib.vm.append uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.runtime.lib.vm.append, while a change to packages.@glimmer.runtime.lib.vm.append can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.runtime.lib.vm.append uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.parser uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser uses a module listed above it, which is the healthy direction.
24→26 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.parser.handlebars-node-visitorspart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, so a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors.
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.
24→27 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.parser.tokenizer-event-handlerspart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, so a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
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.
24→28 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.sourcepart of a loop✕
Connections
2 pairs of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.source.source.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.source.source.
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.
24→29 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.loc.offsetpart of a loop✕
Connections
3 pairs of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.source.loc.offset.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.loc.offset, so a change to packages.@glimmer.syntax.lib.source.loc.offset can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.source.loc.offset.
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.
24→31 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
4 pairs of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.source.loc.span.
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.
24→34 packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.v1.nodes-v1part of a loop✕
Connections
2 pairs of types, where a type in packages.@glimmer.syntax.lib.parser uses a type in packages.@glimmer.syntax.lib.v1.nodes-v1.
packages.@glimmer.syntax.lib.parser uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.parser, while a change to packages.@glimmer.syntax.lib.parser can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
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.@ember.routing.lib uses packages.@ember.-internals.owner, so a change to packages.@ember.-internals.owner can break packages.@ember.routing.lib, while a change to packages.@ember.routing.lib can't break packages.@ember.-internals.owner.
Position
Below the diagonal: packages.@ember.routing.lib uses a module listed above it, which is the healthy direction.
packages.@ember.routing.lib uses packages.@ember.-internals.container.lib.container, so a change to packages.@ember.-internals.container.lib.container can break packages.@ember.routing.lib, while a change to packages.@ember.routing.lib can't break packages.@ember.-internals.container.lib.container.
Position
Below the diagonal: packages.@ember.routing.lib uses a module listed above it, which is the healthy direction.
packages.@ember.routing.lib uses packages.@ember.routing.router, so a change to packages.@ember.routing.router can break packages.@ember.routing.lib, while a change to packages.@ember.routing.lib can't break packages.@ember.routing.router.
Position
Below the diagonal: packages.@ember.routing.lib uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.compiler.lib.builder.builder-interface.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a module listed above it, which is the healthy direction.
16 pairs of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.syntax.lib.v1.handlebars-ast.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.parser, so a change to packages.@glimmer.syntax.lib.parser can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.syntax.lib.parser.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a module listed above it, which is the healthy direction.
26→29 packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.source.loc.offsetpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.syntax.lib.source.loc.offset.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.source.loc.offset, so a change to packages.@glimmer.syntax.lib.source.loc.offset can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.syntax.lib.source.loc.offset.
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.
26→31 packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
2 pairs of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.syntax.lib.source.loc.span.
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.
26→34 packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.v1.nodes-v1part of a loop✕
Connections
2 pairs of types, where a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses a type in packages.@glimmer.syntax.lib.v1.nodes-v1.
packages.@glimmer.syntax.lib.parser.handlebars-node-visitors uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, while a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
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.
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses a type in packages.@glimmer.syntax.lib.parser.handlebars-node-visitors.
packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses packages.@glimmer.syntax.lib.parser.handlebars-node-visitors, so a change to packages.@glimmer.syntax.lib.parser.handlebars-node-visitors can break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, while a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can't break packages.@glimmer.syntax.lib.parser.handlebars-node-visitors.
Position
Below the diagonal: packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses a module listed above it, which is the healthy direction.
27→31 packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, while a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can't break packages.@glimmer.syntax.lib.source.loc.span.
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.
27→34 packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses packages.@glimmer.syntax.lib.v1.nodes-v1part of a loop✕
Connections
3 pairs of types, where a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses a type in packages.@glimmer.syntax.lib.v1.nodes-v1.
packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, while a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
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.@glimmer.syntax.lib.source.source uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.syntax.lib.source.source, while a change to packages.@glimmer.syntax.lib.source.source can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.source uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.source.source, while a change to packages.@glimmer.syntax.lib.source.source can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.source uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.syntax.lib.source.source uses a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, so a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can break packages.@glimmer.syntax.lib.source.source, while a change to packages.@glimmer.syntax.lib.source.source can't break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.source uses a module listed above it, which is the healthy direction.
28→29 packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.source.loc.offsetpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.source.source uses a type in packages.@glimmer.syntax.lib.source.loc.offset.
packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.source.loc.offset, so a change to packages.@glimmer.syntax.lib.source.loc.offset can break packages.@glimmer.syntax.lib.source.source, while a change to packages.@glimmer.syntax.lib.source.source can't break packages.@glimmer.syntax.lib.source.loc.offset.
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.
28→31 packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.source.source uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.source.source uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.source.source, while a change to packages.@glimmer.syntax.lib.source.source can't break packages.@glimmer.syntax.lib.source.loc.span.
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.@glimmer.syntax.lib.source.loc.offset uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.source.loc.offset, while a change to packages.@glimmer.syntax.lib.source.loc.offset can't break packages.@glimmer.syntax.lib.source.source.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.loc.offset uses a module listed above it, which is the healthy direction.
29→31 packages.@glimmer.syntax.lib.source.loc.offset uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.source.loc.offset uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.source.loc.offset uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.source.loc.offset, while a change to packages.@glimmer.syntax.lib.source.loc.offset can't break packages.@glimmer.syntax.lib.source.loc.span.
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.@glimmer.syntax.lib.source.slice uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.source.slice, while a change to packages.@glimmer.syntax.lib.source.slice can't break packages.@glimmer.syntax.lib.source.source.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.slice uses a module listed above it, which is the healthy direction.
30→31 packages.@glimmer.syntax.lib.source.slice uses packages.@glimmer.syntax.lib.source.loc.spanpart of a loop✕
Connections
1 pair of types, where a type in packages.@glimmer.syntax.lib.source.slice uses a type in packages.@glimmer.syntax.lib.source.loc.span.
packages.@glimmer.syntax.lib.source.slice uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.source.slice, while a change to packages.@glimmer.syntax.lib.source.slice can't break packages.@glimmer.syntax.lib.source.loc.span.
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.@glimmer.syntax.lib.source.loc.span uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.source.loc.span, while a change to packages.@glimmer.syntax.lib.source.loc.span can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.loc.span uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.source.loc.span uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.source.loc.span, while a change to packages.@glimmer.syntax.lib.source.loc.span can't break packages.@glimmer.syntax.lib.source.source.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.loc.span uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.source.loc.span uses packages.@glimmer.syntax.lib.source.loc.offset, so a change to packages.@glimmer.syntax.lib.source.loc.offset can break packages.@glimmer.syntax.lib.source.loc.span, while a change to packages.@glimmer.syntax.lib.source.loc.span can't break packages.@glimmer.syntax.lib.source.loc.offset.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.loc.span uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.source.loc.span uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.source.loc.span, while a change to packages.@glimmer.syntax.lib.source.loc.span can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.source.loc.span uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.@glimmer.syntax.lib.v2.objects.attr-block uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.syntax.lib.v2.objects.attr-block uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v2.objects.attr-block, while a change to packages.@glimmer.syntax.lib.v2.objects.attr-block can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.attr-block uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.attr-block uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.v2.objects.attr-block, while a change to packages.@glimmer.syntax.lib.v2.objects.attr-block can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.attr-block uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.expr uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.v2.objects.expr, while a change to packages.@glimmer.syntax.lib.v2.objects.expr can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.expr uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.expr uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.v2.objects.expr, while a change to packages.@glimmer.syntax.lib.v2.objects.expr can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.expr uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1.nodes-v1 uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.syntax.lib.v1.nodes-v1, while a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.nodes-v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1.nodes-v1 uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v1.nodes-v1, while a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.nodes-v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1.nodes-v1 uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@glimmer.syntax.lib.v1.nodes-v1, while a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.nodes-v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1.nodes-v1 uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.v1.nodes-v1, while a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.nodes-v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1.nodes-v1 uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.v1.nodes-v1, while a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can't break packages.@glimmer.syntax.lib.source.loc.span.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1.nodes-v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.args uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v2.objects.args, while a change to packages.@glimmer.syntax.lib.v2.objects.args can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.args uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.args uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.v2.objects.args, while a change to packages.@glimmer.syntax.lib.v2.objects.args can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.args uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.objects.args uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.v2.objects.args, while a change to packages.@glimmer.syntax.lib.v2.objects.args can't break packages.@glimmer.syntax.lib.source.loc.span.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.objects.args uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.compiler.lib.passes.1-normalization.context uses a type in packages.@ember.engine.lib.strict-resolver.
packages.@glimmer.compiler.lib.passes.1-normalization.context uses packages.@ember.engine.lib.strict-resolver, so a change to packages.@ember.engine.lib.strict-resolver can break packages.@glimmer.compiler.lib.passes.1-normalization.context, while a change to packages.@glimmer.compiler.lib.passes.1-normalization.context can't break packages.@ember.engine.lib.strict-resolver.
Position
Below the diagonal: packages.@glimmer.compiler.lib.passes.1-normalization.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.compiler.lib.passes.1-normalization.context uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.compiler.lib.passes.1-normalization.context uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.compiler.lib.passes.1-normalization.context, while a change to packages.@glimmer.compiler.lib.passes.1-normalization.context can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.compiler.lib.passes.1-normalization.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.compiler.lib.passes.1-normalization.context uses a type in packages.@glimmer.syntax.lib.symbol-table.
packages.@glimmer.compiler.lib.passes.1-normalization.context uses packages.@glimmer.syntax.lib.symbol-table, so a change to packages.@glimmer.syntax.lib.symbol-table can break packages.@glimmer.compiler.lib.passes.1-normalization.context, while a change to packages.@glimmer.compiler.lib.passes.1-normalization.context can't break packages.@glimmer.syntax.lib.symbol-table.
Position
Below the diagonal: packages.@glimmer.compiler.lib.passes.1-normalization.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.compiler.lib.passes.1-normalization.context uses a type in packages.@glimmer.syntax.lib.v1.nodes-v1.
packages.@glimmer.compiler.lib.passes.1-normalization.context uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.compiler.lib.passes.1-normalization.context, while a change to packages.@glimmer.compiler.lib.passes.1-normalization.context can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
Position
Below the diagonal: packages.@glimmer.compiler.lib.passes.1-normalization.context uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@ember.-internals.utility-types, so a change to packages.@ember.-internals.utility-types can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@ember.-internals.utility-types.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.compiler.lib.builder.builder-interface, so a change to packages.@glimmer.compiler.lib.builder.builder-interface can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.compiler.lib.builder.builder-interface.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.syntax.lib.source.source.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.syntax.lib.source.loc.span.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v1 uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.v1, while a change to packages.@glimmer.syntax.lib.v1 can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v1 uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.symbol-table, so a change to packages.@glimmer.syntax.lib.symbol-table can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.symbol-table.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.source.loc.span.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.v2.objects.attr-block, so a change to packages.@glimmer.syntax.lib.v2.objects.attr-block can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.v2.objects.attr-block.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.v2.objects.expr, so a change to packages.@glimmer.syntax.lib.v2.objects.expr can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.v2.objects.expr.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.builders uses packages.@glimmer.syntax.lib.v2.objects.args, so a change to packages.@glimmer.syntax.lib.v2.objects.args can break packages.@glimmer.syntax.lib.v2.builders, while a change to packages.@glimmer.syntax.lib.v2.builders can't break packages.@glimmer.syntax.lib.v2.objects.args.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.builders uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in packages.@glimmer.syntax.lib.v2.serialize.serialize uses a type in packages.@glimmer.compiler.lib.passes.2-encoding.mir.
packages.@glimmer.syntax.lib.v2.serialize.serialize uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v2.serialize.serialize, while a change to packages.@glimmer.syntax.lib.v2.serialize.serialize can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.serialize.serialize uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.@glimmer.syntax.lib.v2.serialize.serialize uses a type in packages.@glimmer.syntax.lib.v2.objects.attr-block.
packages.@glimmer.syntax.lib.v2.serialize.serialize uses packages.@glimmer.syntax.lib.v2.objects.attr-block, so a change to packages.@glimmer.syntax.lib.v2.objects.attr-block can break packages.@glimmer.syntax.lib.v2.serialize.serialize, while a change to packages.@glimmer.syntax.lib.v2.serialize.serialize can't break packages.@glimmer.syntax.lib.v2.objects.attr-block.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.serialize.serialize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.serialize.serialize uses packages.@glimmer.syntax.lib.v2.objects.expr, so a change to packages.@glimmer.syntax.lib.v2.objects.expr can break packages.@glimmer.syntax.lib.v2.serialize.serialize, while a change to packages.@glimmer.syntax.lib.v2.serialize.serialize can't break packages.@glimmer.syntax.lib.v2.objects.expr.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.serialize.serialize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.serialize.serialize uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.v2.serialize.serialize, while a change to packages.@glimmer.syntax.lib.v2.serialize.serialize can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.serialize.serialize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.serialize.serialize uses packages.@glimmer.syntax.lib.v2.objects.args, so a change to packages.@glimmer.syntax.lib.v2.objects.args can break packages.@glimmer.syntax.lib.v2.serialize.serialize, while a change to packages.@glimmer.syntax.lib.v2.serialize.serialize can't break packages.@glimmer.syntax.lib.v2.objects.args.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.serialize.serialize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.compiler.lib.passes.2-encoding.mir, so a change to packages.@glimmer.compiler.lib.passes.2-encoding.mir can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.compiler.lib.passes.2-encoding.mir.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.symbol-table, so a change to packages.@glimmer.syntax.lib.symbol-table can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.symbol-table.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.v1.handlebars-ast, so a change to packages.@glimmer.syntax.lib.v1.handlebars-ast can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.v1.handlebars-ast.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.@glimmer.syntax.lib.v2.normalize uses a type in packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers, so a change to packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.parser.tokenizer-event-handlers.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.source.source, so a change to packages.@glimmer.syntax.lib.source.source can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.source.source.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.source.slice, so a change to packages.@glimmer.syntax.lib.source.slice can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.source.slice.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.source.loc.span, so a change to packages.@glimmer.syntax.lib.source.loc.span can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.source.loc.span.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.v2.objects.attr-block, so a change to packages.@glimmer.syntax.lib.v2.objects.attr-block can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.v2.objects.attr-block.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.v2.objects.expr, so a change to packages.@glimmer.syntax.lib.v2.objects.expr can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.v2.objects.expr.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.v1.nodes-v1, so a change to packages.@glimmer.syntax.lib.v1.nodes-v1 can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.v1.nodes-v1.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize uses a module listed above it, which is the healthy direction.
packages.@glimmer.syntax.lib.v2.normalize uses packages.@glimmer.syntax.lib.v2.builders, so a change to packages.@glimmer.syntax.lib.v2.builders can break packages.@glimmer.syntax.lib.v2.normalize, while a change to packages.@glimmer.syntax.lib.v2.normalize can't break packages.@glimmer.syntax.lib.v2.builders.
Position
Below the diagonal: packages.@glimmer.syntax.lib.v2.normalize 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
66
High / Critical
A05:2025 — Injection
22
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse; Break each cycle by extracting the shared piece into a module both sides can import; Resolve the 10 Off the main sequence finding(s) in Coupling.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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 — 89
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 — 573
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 — 419
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 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 68 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, 1043 of 1081 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.
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.
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.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `internal-docs/guides/reactivity/pseudocode/composition.ts`, `packages/@ember/-internals/glimmer/lib/component-managers/curly-brand.ts`, `packages/@ember/-internals/glimmer/lib/component.ts`, `packages/@ember/-internals/glimmer/lib/components/internal.ts`, `packages/@ember/-internals/glimmer/lib/helper-brand.ts`, … (+47 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/@glimmer/runtime/lib/scope.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ember-source@7.6.0-alpha.1 start / > vite dev / VITE v7.3.7 ready in 1116 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ember-source@7.6.0-alpha.1 start / > vite dev / VITE v7.3.7 ready in 1116 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
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 none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
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. 90 further occurrence(s) are not listed individually; the score already reflects all 130.
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. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
R8 Dependency Hygiene — 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. 30 further occurrence(s) are not listed individually; the score already reflects all 70.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 24 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.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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.
34 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous)::(anonymous)::anonymous at 54. A further 7 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 (anonymous)::anonymous at 80 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/@glimmer/compiler/lib/passes/1-normalization/visitors/strict-mode.ts (StrictModeValidationPass.Expression at 18), packages/@glimmer/compiler/lib/passes/2-encoding/expressions.ts (ExpressionEncoder.expr at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with (anonymous)::(anonymous)::anonymous (cyclomatic 54), WireFormatDebugger.formatOpcode (cyclomatic 49), (anonymous)::parse (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 55 bodies over 15 down to 15 or less in Cognitive Complexity — start with (anonymous)::parse (cognitive 63), chain-tags.getChainTags (cognitive 53), collectNamedExports (cognitive 49). — 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 55 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Stronggated by 23 serious findings✓ 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 8 FileTooLong finding(s) in God Classes — start with router.ts (2), parser.js, builder-interface.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with router.ts (2), element-builder.ts, route.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 MethodTooLong finding(s) in God Classes — start with router.ts (2), wire-format-debug.ts, tokenizer-event-handlers.ts. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling0.0 / 10Critical✓ 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.
60 production modules (npm), 1 dependency cycle(s), 5 unstable depended-on module(s). Read from the build's own module declarations; 10 module(s) off the main sequence, with abstractness counted on 41 of the 60 (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).
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 13 Low cohesion finding(s) in Cohesion (LCOM4) — start with manager.ts, curly.ts, test_helpers.ts. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 1 critical finding✓ 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.
33 skipped (33 with a documented reason), 108 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1036 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions (empty test): assertion does not throw if destroyables were destroyedpackages/@glimmer/destroyable/test/destroyables-test.ts:437
No assertions: (unnamed test) · ×3packages/@glimmer-workspace/integration-tests/test/support.ts:56
No direct assertions: mustache · ×104packages/@handlebars/parser/spec/ast.js:7
Test project verifies nothing: packages/@handlebars/parserpackages/@handlebars/parser/spec/ast.js:7
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with destroyables-test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 104 No direct assertions finding(s) in Test Quality — start with parser.js (62), ast.js (32), visitor.js (10). — One of this dimension's main actionable groups (104 recommendation-level).
Resolve the 3 No assertions finding(s) in Test Quality — start with destroyables-test.ts (2), support.ts. — One of this dimension's main actionable groups (3 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 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `pnpm install --frozen-lockfile --ignore-scripts` in packages/@handlebars/parser/ (104 tests); its own test command under node's V8 coverage via `pnpm install --frozen-lockfile --ignore-scripts` in smoke-tests/node-template/ (2 tests); its own test command under node's V8 coverage via `pnpm install --frozen-lockfile --ignore-scripts` in smoke-tests/scenarios/ (17 tests); mocha via `pnpm install --frozen-lockfile --ignore-scripts` in tests/node-blueprints/ (265 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in tests/node-vitest/ (2 tests)): measured (0 flaky).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
11 outdated direct production npm dependency(ies) of 32 graded, 0 pinning defect(s), across 80 package.json (63 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 38 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (38). — One of this dimension's main actionable groups (38 recommendation-level).
Resolve the 26 Deprecated finding(s) in Dependency Hygiene — start with package.json (26). — One of this dimension's main actionable groups (26 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 348 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 348 package(s) this repository's committed lockfile installs for a consumer — its 32 production, optional and peer dependency(ies), across 63 product package.json manifest(s), and everything those install in turn. Its 387 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under ISC / MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with router.ts (2), named-transition-intent.ts, compat.ts. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.9 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
34 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 324 of the 749 production source files in this repository: 421 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
96 deducted task-comment markers across 87920 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 91 TodoComment finding(s) in Explicit Debt — start with REDACTED (5), component.ts (5), router.ts (4). — One of this dimension's main actionable groups (91 warning-level).
Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with element-builder.ts, operations.ts, expressions.ts. — One of this dimension's main actionable groups (5 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.
2 of 2 documentation facets pass in full. 11 document(s) read across 62 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
1 naming inconsistencies among 10 declarations measured against a convention their peers follow.
`isHBSLiteral` spells `HBS` where 12 names in the project spell it `Hbs`packages/@glimmer/syntax/lib/utils.ts:25
What to do
Resolve the 1 `isHBSLiteral` spells `HBS` where 12 names in the project spell it `Hbs` finding(s) in Naming Consistency — start with utils.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
191 domain type(s) cross context boundaries across 50 contexts; they are measured and withheld (not published, not scored). Contexts: -internals, app-template, application, array, benchmark-app, canary-features, compiler, component, constants, controller, debug, debug-util and 38 more.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
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.
35 % of calls cross a namespace and 15 % go through an interface, but 85 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. 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).
22 finding(s): 0 critical, 11 high, 11 medium, 0 low. semgrep hit a parse error in 57 file(s) — `blueprints/component-test/files/__root__/__testType__/__path__/__test__.ts` (line 1, line 4, line 26, …), `internal-docs/guides/reactivity/pseudocode/composition.ts` (line 84), `packages/@ember/-internals/glimmer/lib/component-managers/curly-brand.ts` (line 7), `packages/@ember/-internals/glimmer/lib/component.ts` (line 213), `packages/@ember/-internals/glimmer/lib/components/internal.ts` (line 112), … (+52 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 33 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (33). — One of this dimension's main actionable groups (33 issue-level).
Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
157 of 328 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 328 of the 749 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 151 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (9), expressions.ts (4), index.js (4). — One of this dimension's main actionable groups (151 recommendation-level).
Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with REDACTED, computed.ts, builder-interface.ts. — One of this dimension's main actionable groups (6 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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with bucket.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with wire-format-debug.ts, component.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with compilable-template.ts, call.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
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 7 platform declaration(s) and 17 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.
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.
The projects @ember/-internals → @ember/application → @ember/-internals (one cycle inside a mutually-dependent group of 28 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/@ember/-internals/package.json:28
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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.
`EmberArray` declares 35 required operations: `objectAt`, `objectsAt`, `slice`, `indexOf`, `lastIndexOf`, `forEach`, `getEach`, `setEach`, `map`, `mapBy`, `mapBy`, `filter`, `reject`, `filterBy`, `rejectBy`, `find`, `find`, `findBy`, `findBy`, `every`, `isEvery`, `isEvery`, `any`, `isAny`, `isAny`, `reduce`, `invoke`, `toArray`, `compact`, `includes`, `sortBy`, `uniq`, `uniqBy`, `uniqBy`, `without`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 35 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/@ember/array/index.ts:55
`MutableArray` declares 16 required operations: `replace`, `clear`, `insertAt`, `removeAt`, `pushObject`, `pushObjects`, `popObject`, `shiftObject`, `unshiftObject`, `unshiftObjects`, `reverseObjects`, `setObjects`, `removeObject`, `removeObjects`, `addObject`, `addObjects`. 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. — packages/@ember/array/index.ts:1071
`InternalObservable` declares 19 required operations under just 11 distinct name(s): `get`, `get`, `getProperties`, `getProperties`, `getProperties`, `getProperties`, `set`, `set`, `setProperties`, `setProperties`, `notifyPropertyChange`, `addObserver`, `addObserver`, `removeObserver`, `removeObserver`, `incrementProperty`, `decrementProperty`, `toggleProperty`, `cacheFor`. 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. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 11 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/@ember/object/observable-internal.ts:32
`Observable` declares 19 required operations under just 11 distinct name(s): `get`, `get`, `getProperties`, `getProperties`, `getProperties`, `getProperties`, `set`, `set`, `setProperties`, `setProperties`, `notifyPropertyChange`, `addObserver`, `addObserver`, `removeObserver`, `removeObserver`, `incrementProperty`, `decrementProperty`, `toggleProperty`, `cacheFor`. 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. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 11 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/@ember/object/observable.ts:87
`RouteManagerWithClassicInterop` declares 22 required operations: `isInaccessibleByURL`, `willEnter`, `enter`, `didEnter`, `willExit`, `exit`, `didExit`, `qp`, `stashNames`, `serializeQueryParam`, `deserializeQueryParam`, `serializeContext`, `queryParamsDidChange`, `finalizeQueryParamChange`, `getContext`, `redirect`, `invokeAction`, `triggerLoadingEvent`, `triggerErrorEvent`, `handleLoadingEvent`, `handleErrorEvent`, `getRouteInfoMetadata`. 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. — packages/router_js/lib/route-manager.ts:337
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX8 · Test isolation0.0 / 10Critical✓ 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.
`@ember/-internals` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/-internals/package.json:73
`@ember/application` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/application/package.json:33
`@ember/array` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/array/package.json:29
`@ember/controller` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/controller/package.json:22
`@ember/debug` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/debug/package.json:31
`@ember/engine` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/engine/package.json:30
`@ember/enumerable` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/enumerable/package.json:20
`@ember/instrumentation` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/instrumentation/package.json:19
`@ember/object` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/object/package.json:38
`@ember/routing` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/routing/package.json:40
`@ember/runloop` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/runloop/package.json:21
`@ember/service` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/service/package.json:20
`@ember/utils` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/@ember/utils/package.json:24
`ember` (production) references the test project `@ember/test`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/ember/package.json:31
`ember` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/ember/package.json:47
`ember-template-compiler` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/ember-template-compiler/package.json:38
`ember-testing` (production) references the test project `@ember/test`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/ember-testing/package.json:20
`ember-testing` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/ember-testing/package.json:29
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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.
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — packages/@ember/object/lib/computed/reduce_computed_macros.ts:81, packages/@ember/object/lib/computed/reduce_computed_macros.ts:1368
`hasDefaultComponentManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/@glimmer/manager/lib/internal/api.ts:238
`hasDefaultModifierManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/@glimmer/manager/lib/internal/api.ts:246
`scheduleOutletUpdate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/router_js/lib/router.ts:107
`didCreateElement` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/-internals/glimmer/lib/helpers/element.ts:38
`didRenderLayout` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/-internals/glimmer/lib/helpers/element.ts:49
`didUpdateLayout` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/-internals/glimmer/lib/helpers/element.ts:50
`didCreate` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/-internals/glimmer/lib/helpers/element.ts:51
`didUpdate` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/-internals/glimmer/lib/helpers/element.ts:52
`registerHandler` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/@ember/debug/lib/deprecate.ts:77, packages/@ember/debug/lib/warn.ts:19
`deprecate` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/debug/lib/deprecate.ts:81
`invoke` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/debug/lib/handlers.ts:27
`warn` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/@ember/debug/lib/warn.ts:20
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. — packages/@handlebars/parser/lib/parser.js:1
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
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.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 14 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/ci.yml:16
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`existsSync` in `prepareApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/benchmark/utils.mjs:166
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety6.6 / 10Adequate✓ 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.
829 typed · 432 plain JS — the untyped files are blueprints/-addon-import.js, blueprints/-utils.js, blueprints/acceptance-test/index.js, blueprints/component-addon/index.js, blueprints/component-class-addon/index.js, blueprints/component-class/index.js (+426 more).
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.
6 duplicated blocks under blueprints/ have copies in at least two of the sibling directories component, component-addon, component-class, component-class-addon, controller, route (+2 more sibling(s) not listed) — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — blueprints/component-class/index.js:63
6 duplicated blocks under packages/ have copies in at least two of the sibling directories @ember, @glimmer, ember-template-compiler, router_js — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/@ember/template-compiler/lib/plugins/index.ts:15
6 duplicated blocks under packages/@ember/ have copies in at least two of the sibling directories -internals, controller, routing, service — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/@ember/-internals/views/lib/views/core_view.ts:79
packages/@glimmer/validator/lib/collections/map.ts:63 · packages/@glimmer/validator/lib/collections/set.ts:52 — the two spans are one implementation copied and then locally edited — 242 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/@glimmer/validator/lib/collections/map.ts:63
packages/@ember/template-compiler/lib/plugins/index.ts:15 · packages/ember-template-compiler/lib/plugins/index.ts:15 — the two spans are one implementation copied and then locally edited — 112 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/@ember/template-compiler/lib/plugins/index.ts:15
REDACTED:25 · packages/ember-template-compiler/lib/system/compile-options.ts:10 — the two spans are one implementation copied and then locally edited — 268 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. — REDACTED:25
packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:261 · packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:351 — the two spans are one implementation copied and then locally edited — 233 tokens are still identical, in the same order in both spans, 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/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:261
packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:93 · packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:93
packages/@ember/-internals/utils/lib/get-debug-name.ts:22 · packages/@glimmer/debug-util/lib/debug-to-string.ts:23 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/@ember/-internals/utils/lib/get-debug-name.ts:22
packages/@ember/routing/route.ts:789 · packages/@ember/routing/router.ts:226 — 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/@ember/routing/route.ts:789
blueprints/component-class/index.js:63 · blueprints/component/index.js:179 — 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. — blueprints/component-class/index.js:63
eslint-rules/no-barrel-imports.cjs:554 · eslint-rules/no-barrel-imports.cjs:628 — 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. — eslint-rules/no-barrel-imports.cjs:554
packages/@glimmer/debug/lib/debug.ts:101 · packages/@glimmer/debug/lib/dism/dism.ts:27 — 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/@glimmer/debug/lib/debug.ts:101
packages/@ember/-internals/metal/lib/computed.ts:397 · packages/@ember/-internals/metal/lib/computed.ts:561 — the two spans are one implementation copied and then locally edited — 174 tokens are still identical, in the same order in both spans, 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/@ember/-internals/metal/lib/computed.ts:397
packages/@glimmer/validator/lib/collections/set.ts:17 · packages/@glimmer/validator/lib/collections/weak-set.ts:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/@glimmer/validator/lib/collections/set.ts:17
packages/@glimmer/validator/lib/collections/map.ts:24 · packages/@glimmer/validator/lib/collections/weak-map.ts:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/@glimmer/validator/lib/collections/map.ts:24
blueprints/component-addon/index.js:6 · blueprints/component-class-addon/index.js:6 — 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. — blueprints/component-addon/index.js:6
packages/@ember/template-compiler/lib/system/calculate-location-display.ts:3 · packages/ember-template-compiler/lib/system/calculate-location-display.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/@ember/template-compiler/lib/system/calculate-location-display.ts:3
packages/@ember/-internals/views/lib/views/core_view.ts:79 · packages/@ember/routing/route.ts:789 · packages/@ember/routing/router.ts:226 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/@ember/-internals/views/lib/views/core_view.ts:79
packages/@ember/object/lib/computed/reduce_computed_macros.ts:417 · packages/@ember/object/lib/computed/reduce_computed_macros.ts:646 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@ember/object/lib/computed/reduce_computed_macros.ts:417
rollup.config.mjs:136 · rollup.config.mjs:157 — 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. — rollup.config.mjs:136
packages/@ember/object/events.ts:8 · packages/@ember/object/events.ts:43 — the two spans are one implementation copied and then locally edited — 128 tokens are still identical, in the same order in both spans, 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/@ember/object/events.ts:8
packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:319 · packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:345 — 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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `kw(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:319
packages/@glimmer/validator/lib/collections/weak-map.ts:78 · packages/@glimmer/validator/lib/collections/weak-set.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/@glimmer/validator/lib/collections/weak-map.ts:78
packages/@ember/-internals/metal/lib/array_events.ts:5 · packages/@ember/-internals/metal/lib/array_events.ts:30 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both spans, 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/@ember/-internals/metal/lib/array_events.ts:5
packages/@glimmer/compiler/lib/wire-format-debug.ts:79 · packages/@glimmer/compiler/lib/wire-format-debug.ts:101 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@glimmer/compiler/lib/wire-format-debug.ts:79
packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:131 · packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:131
packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:394 · packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:442 · packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:492 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:394
packages/@glimmer/syntax/lib/v1/parser-builders.ts:341 · packages/@glimmer/syntax/lib/v1/parser-builders.ts:378 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@glimmer/syntax/lib/v1/parser-builders.ts:341
packages/@ember/-internals/metal/lib/injected_property.ts:71 · packages/@ember/-internals/metal/lib/injected_property.ts:112 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, 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/@ember/-internals/metal/lib/injected_property.ts:71
packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:94 · packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:122 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:94
packages/@glimmer/manager/lib/public/component.ts:120 · packages/@glimmer/manager/lib/public/helper.ts:82 — the two spans are one implementation copied and then locally edited — 74 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/@glimmer/manager/lib/public/component.ts:120
packages/@glimmer/manager/lib/public/helper.ts:82 · packages/@glimmer/manager/lib/public/modifier.ts:83 — the two spans are one implementation copied and then locally edited — 74 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/@glimmer/manager/lib/public/helper.ts:82
packages/@glimmer/runtime/lib/environment.ts:63 · packages/@glimmer/runtime/lib/environment.ts:80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@glimmer/runtime/lib/environment.ts:63
packages/@ember/-internals/glimmer/lib/components/input.ts:221 · packages/@ember/-internals/glimmer/lib/components/textarea.ts:133 — the two spans are one implementation copied and then locally edited — 81 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/@ember/-internals/glimmer/lib/components/input.ts:221
packages/@ember/object/observable-internal.ts:51 · packages/@ember/object/observable.ts:329 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — packages/@ember/object/observable-internal.ts:51
packages/@ember/routing/lib/routing-service.ts:40 · packages/@ember/routing/router-service.ts:167 — 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/@ember/routing/lib/routing-service.ts:40
packages/@glimmer/compiler/lib/builder/builder-interface.ts:202 · packages/@glimmer/compiler/lib/builder/builder-interface.ts:261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@glimmer/compiler/lib/builder/builder-interface.ts:202
packages/@glimmer/compiler/lib/builder/builder-interface.ts:714 · packages/@glimmer/compiler/lib/builder/builder-interface.ts:786 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@glimmer/compiler/lib/builder/builder-interface.ts:714
packages/@glimmer/validator/lib/collections/weak-map.ts:57 · packages/@glimmer/validator/lib/collections/weak-set.ts:73 — 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/@glimmer/validator/lib/collections/weak-map.ts:57
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.
broccoli/glimmer-template-compiler.mjs:5 reaches into another package with a relative path (../packages/ember-template-compiler/minimal.ts) — import the package by name instead. — broccoli/glimmer-template-compiler.mjs:5
packages/@glimmer/component/src/-private/component.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/@glimmer/component/src/-private/component.ts:1
packages/@glimmer/component/src/-private/ember-component-manager.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/@glimmer/component/src/-private/ember-component-manager.ts:1
packages/@glimmer/component/src/index.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/@glimmer/component/src/index.ts:1
packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:1 reaches into another package with a relative path (../../array.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:1
packages/@glimmer/interfaces/lib/managers/internal.d.ts:1 reaches into another package with a relative path (./internal/component.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/managers/internal.d.ts:1
packages/@glimmer/interfaces/lib/managers/internal.d.ts:2 reaches into another package with a relative path (./internal/helper.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/managers/internal.d.ts:2
packages/@glimmer/interfaces/lib/managers/internal/helper.d.ts:2 reaches into another package with a relative path (../helper.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/managers/internal/helper.d.ts:2
packages/@glimmer/interfaces/lib/template.d.ts:1 reaches into another package with a relative path (./array.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/template.d.ts:1
packages/@glimmer/interfaces/lib/template.d.ts:5 reaches into another package with a relative path (./managers/internal/component.js) — import the package by name instead. — packages/@glimmer/interfaces/lib/template.d.ts:5
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (7 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (3 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
anonymous has cyclomatic complexity 54 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@handlebars/parser/lib/parser.js:1756
formatOpcode has cyclomatic complexity 49 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 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/@glimmer/compiler/lib/wire-format-debug.ts:38
(top-level) has cyclomatic complexity 36 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/router_js/lib/transition-intent/named-transition-intent.ts:2
parse has cyclomatic complexity 35 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@handlebars/parser/lib/parser.js:1251
assert has cyclomatic complexity 33 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/internal-test-helpers/lib/ember-dev/method-call-tracker.ts:72
updateListener has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/runtime/lib/modifiers/on.ts:57
#stringify has cyclomatic complexity 30 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/debug/lib/dism/opcode.ts:80
getChainTags has cyclomatic complexity 26 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/@ember/-internals/metal/lib/chain-tags.ts:59
collectNamedExports has cyclomatic complexity 25 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — eslint-rules/no-barrel-imports.cjs:174
checkCall has cyclomatic complexity 25 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. — tests/node-vitest/lib/detect.js:190
compare has cyclomatic complexity 24 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 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/@ember/utils/lib/compare.ts:100
initialize has cyclomatic complexity 21 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/@ember/object/core.ts:72
InvokeStaticComponent has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.ts:194
Program has cyclomatic complexity 19 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/@handlebars/parser/lib/whitespace-control.js:8
handleImport 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. — eslint-rules/no-barrel-imports.cjs:508
buildElement has cyclomatic complexity 19 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/syntax/lib/v1/public-builders.ts:191
(anonymous) has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/router_js/lib/router.ts:263
appendTo has cyclomatic complexity 18 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 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/@glimmer/debug/lib/render/fragment.ts:229
(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/@glimmer/runtime/lib/compiled/opcodes/component.ts:162
buildStatement has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/@glimmer/compiler/lib/builder/builder.ts:232
(top-level) has cyclomatic complexity 18 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/@ember/-internals/browser-environment/lib/has-dom.ts:2
finalizeQueryParamChange has cyclomatic complexity 17 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@ember/-internals/routing/route-managers/classic/query-params.ts:103
inspectValue has cyclomatic complexity 17 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/@ember/debug/lib/inspect.ts:37
mergeProps has cyclomatic complexity 16 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/@ember/object/mixin-internal.ts:284
BlockStatement has cyclomatic complexity 16 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/@glimmer/syntax/lib/generation/printer.ts:352
describe has cyclomatic complexity 16 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/debug/lib/vm/snapshot.ts:121
arrayContentDidChange has cyclomatic complexity 16 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/@ember/-internals/metal/lib/array_events.ts:30
handleExportNamed has cyclomatic complexity 16 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 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. — eslint-rules/no-barrel-imports.cjs:593
PartialBlockStatement has cyclomatic complexity 16 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 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/@handlebars/parser/lib/whitespace-control.js:67
acceptCallNodes has cyclomatic complexity 16 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:653
next has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@handlebars/parser/lib/parser.js:1642
getPathName has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/syntax/lib/get-template-locals.ts:15
init has cyclomatic complexity 15 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 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/@ember/-internals/glimmer/lib/component.ts:915
testOverrideGlobalContext has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/@glimmer/global-context/index.ts:209
(anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. (×2) — packages/@ember/object/compat.ts:153, packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:214
sync has cyclomatic complexity 14 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@glimmer/runtime/lib/vm/update.ts:255
getRoute has cyclomatic complexity 14 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@ember/routing/router.ts:387
constructor has cyclomatic complexity 14 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. — lib/overrides.cjs:105
preparePath has cyclomatic complexity 14 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 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/@handlebars/parser/lib/helpers.js:44
Do you agree with this assessment?
R3 · Large Files7.2 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/@handlebars/parser/lib/parser.js has 1979 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/@handlebars/parser/lib/parser.js:1
packages/@ember/routing/route.ts has 1736 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/@ember/routing/route.ts:1
packages/@ember/routing/router.ts has 1566 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/@ember/routing/router.ts:1
packages/@ember/helper/index.ts has 1485 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/@ember/helper/index.ts:1
packages/@ember/-internals/glimmer/lib/component.ts has 1339 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/@ember/-internals/glimmer/lib/component.ts:1
packages/@ember/array/index.ts has 1322 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/@ember/array/index.ts:1
packages/@ember/object/lib/computed/reduce_computed_macros.ts has 1136 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/@ember/object/lib/computed/reduce_computed_macros.ts:1
REDACTED has 1109 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/router_js/lib/router.ts has 1041 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/router_js/lib/router.ts:1
packages/@glimmer/syntax/lib/v2/normalize.ts has 935 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/@glimmer/syntax/lib/v2/normalize.ts:1
packages/@ember/object/core.ts has 919 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/@ember/object/core.ts:1
packages/@ember/application/index.ts has 901 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/@ember/application/index.ts:1
packages/@ember/runloop/index.ts has 804 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/@ember/runloop/index.ts:1
packages/@glimmer/compiler/lib/builder/builder-interface.ts has 803 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/@glimmer/compiler/lib/builder/builder-interface.ts:1
packages/@glimmer/runtime/lib/compiled/opcodes/component.ts has 803 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/@glimmer/runtime/lib/compiled/opcodes/component.ts:1
packages/@glimmer/runtime/lib/vm/append.ts has 794 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/@glimmer/runtime/lib/vm/append.ts:1
REDACTED has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/@ember/-internals/metal/lib/computed.ts has 767 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/@ember/-internals/metal/lib/computed.ts:1
packages/@ember/routing/router-service.ts has 729 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/@ember/routing/router-service.ts:1
packages/@ember/object/lib/computed/computed_macros.ts 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. — packages/@ember/object/lib/computed/computed_macros.ts:1
packages/@ember/-internals/glimmer/lib/base-renderer.ts has 718 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/@ember/-internals/glimmer/lib/base-renderer.ts:1
packages/@glimmer-workspace/integration-tests/lib/render-test.ts has 693 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/@glimmer-workspace/integration-tests/lib/render-test.ts:1
packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts has 676 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/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:1
packages/@glimmer/compiler/lib/builder/builder.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/@glimmer/compiler/lib/builder/builder.ts:1
packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts has 658 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/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:1
packages/@glimmer/debug/lib/opcode-metadata.ts has 629 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/@glimmer/debug/lib/opcode-metadata.ts:1
packages/@ember/-internals/meta/lib/meta.ts has 625 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/@ember/-internals/meta/lib/meta.ts:1
packages/@glimmer-workspace/integration-tests/lib/suites/each.ts 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. — packages/@glimmer-workspace/integration-tests/lib/suites/each.ts:1
packages/@ember/debug/data-adapter.ts has 607 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/@ember/debug/data-adapter.ts:1
eslint-rules/no-barrel-imports.cjs has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — eslint-rules/no-barrel-imports.cjs:1
packages/@ember/-internals/owner/index.ts has 603 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/@ember/-internals/owner/index.ts:1
packages/@ember/object/mixin-internal.ts has 593 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/@ember/object/mixin-internal.ts:1
packages/@ember/-internals/glimmer/lib/components/link-to.ts has 563 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/@ember/-internals/glimmer/lib/components/link-to.ts:1
packages/@ember/array/index-internal.ts has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/@ember/array/index-internal.ts:1
packages/router_js/lib/route-info.ts has 520 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/router_js/lib/route-info.ts:1
packages/@ember/-internals/container/lib/container.ts has 490 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/@ember/-internals/container/lib/container.ts:1
packages/@glimmer/syntax/lib/source/loc/span.ts has 490 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/@glimmer/syntax/lib/source/loc/span.ts:1
packages/@glimmer/runtime/lib/vm/element-builder.ts has 481 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/@glimmer/runtime/lib/vm/element-builder.ts:1
packages/@ember/-internals/glimmer/lib/component-managers/curly.ts has 469 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/@ember/-internals/glimmer/lib/component-managers/curly.ts:1
packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts has 469 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/@glimmer/runtime/lib/vm/rehydrate-builder.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.4 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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. (×34) — eslint-rules/no-barrel-imports.cjs:1, lib/overrides.cjs:1, packages/@glimmer/debug/lib/metadata.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each 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.
The root package declares the lint script `lint:eslint` (`eslint --report-unused-disable-directives --cache .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint:eslint` in `.` (or the workspace's task runner). — package.json:63
Do you agree with this assessment?
R7 · Dead Code9.6 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
73 file(s) (~17229 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/@glimmer-workspace/integration-tests/test
83 file(s) (~4767 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. — tests/node-blueprints
7 file(s) (~665 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. — tests/node-vitest
Unreachable from the 762 application, 66 tooling and 802 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (762 application, 66 tooling, 802 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) — blueprints/route/index.js, internal-docs/guides/reactivity/pseudocode/composition.ts, blueprints/component-class/index.js, …
no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (internal-docs/guides/reactivity/pseudocode/composition.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 — internal-docs/guides/reactivity/pseudocode/primitives.ts
no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (internal-docs/guides/reactivity/pseudocode/composition.ts, internal-docs/guides/reactivity/pseudocode/primitives.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 — internal-docs/guides/reactivity/pseudocode/tags.ts
no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (blueprints/helper-addon/index.js, blueprints/initializer-addon/index.js, blueprints/instance-initializer-addon/index.js) — 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 — blueprints/-addon-import.js
no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (×11) — packages/ember-template-compiler/lib/plugins/assert-against-attrs.ts, packages/ember-template-compiler/lib/plugins/assert-against-named-outlets.ts, packages/ember-template-compiler/lib/plugins/assert-input-helper-without-block.ts, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root 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. (×4) — package.json:105, package.json:135, package.json:136, …
Declared in packages/@ember/-internals/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. (×2) — packages/@ember/-internals/package.json:30, packages/@ember/-internals/package.json:46
Declared in packages/@ember/template-compilation/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. — packages/@ember/template-compilation/package.json:11
Declared in packages/@ember/version/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. — packages/@ember/version/package.json:13
Declared in packages/@glimmer-workspace/integration-tests/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. (×2) — packages/@glimmer-workspace/integration-tests/package.json:20, packages/@glimmer-workspace/integration-tests/package.json:58
Declared in packages/@glimmer-workspace/integration-tests/test/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. (×2) — packages/@glimmer-workspace/integration-tests/test/package.json:8, packages/@glimmer-workspace/integration-tests/test/package.json:13
Declared in packages/@glimmer/destroyable/test/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. — packages/@glimmer/destroyable/test/package.json:8
Declared in packages/@glimmer/interfaces/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. — packages/@glimmer/interfaces/package.json:27
Declared in packages/@glimmer/opcode-compiler/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. — packages/@glimmer/opcode-compiler/package.json:56
Declared in packages/@glimmer/syntax/test/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. — packages/@glimmer/syntax/test/package.json:7
Declared in packages/ember/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) — packages/ember/package.json:12, packages/ember/package.json:30, packages/ember/package.json:33
Declared in packages/ember-template-compiler/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. — packages/ember-template-compiler/package.json:14
Declared in packages/router_js/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. — packages/router_js/package.json:19
Declared in smoke-tests/app-template/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. (×15) — smoke-tests/app-template/package.json:33, smoke-tests/app-template/package.json:39, smoke-tests/app-template/package.json:41, …
Declared in smoke-tests/scenarios/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. (×4) — smoke-tests/scenarios/package.json:11, smoke-tests/scenarios/package.json:13, smoke-tests/scenarios/package.json:15, …
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
packages/@glimmer/compiler/lib/passes/1-normalization/keywords.ts → packages/@glimmer/compiler/lib/passes/1-normalization/keywords/append.ts → packages/@glimmer/compiler/lib/passes/1-normalization/keywords/utils/curry.ts → packages/@glimmer/compiler/lib/passes/1-normalization/visitors/expressions.ts → packages/@glimmer/compiler/lib/passes/1-normalization/keywords.ts (one verified cycle inside a mutually-dependent group of 13 files) — packages/@glimmer/compiler/lib/passes/1-normalization/keywords.ts:1
packages/@glimmer/debug/lib/dism/opcode.ts → packages/@glimmer/debug/lib/render/basic.ts → packages/@glimmer/debug/lib/dism/opcode.ts (one verified cycle inside a mutually-dependent group of 4 files) — packages/@glimmer/debug/lib/dism/opcode.ts:23
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
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.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — packages/@glimmer/compiler/lib/compiler.ts:45
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
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.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.0 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`loc` is exported and takes `span: HasSourceSpan` from its caller, and it calls itself at line 48 (`loc`) with a piece of `span` — and nowhere in `loc` 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 `loc` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/@glimmer/syntax/lib/source/span-list.ts:48
`buildSingleMeta` is exported, takes a document from its caller (line 194) and hands it to `stringify`, which calls itself at line 213 (`stringify`) with a piece of `o` (and at line 219) — and nowhere in `stringify` 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 `stringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/@glimmer/debug/lib/metadata.ts:213
`intoFragment` is exported, takes a document from its caller (line 349) and hands it to `intoFragments`, which calls itself at line 362 (`intoFragments`) with a piece of `value` — and nowhere in `intoFragments` 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 `intoFragments` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/@glimmer/debug/lib/render/fragment.ts:362
`toString` is exported and takes `obj: any | undefined | null` from its caller, and it calls itself at line 29 (`toString`) with a piece of `obj` — and nowhere in `toString` 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 `toString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/@ember/-internals/utils/lib/to-string.ts:29
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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.3 / 10Critical✓ 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 `insertAdjacentHTML` 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. (×3) — packages/@glimmer/runtime/lib/dom/operations.ts:97, packages/@glimmer/runtime/lib/dom/operations.ts:100, packages/@glimmer/runtime/lib/dom/operations.ts:108
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.
`.then(…, () => {})` 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. (×3) — packages/router_js/lib/route-manager.ts:101, packages/@ember/-internals/routing/route-managers/outlet-state.ts:53, packages/@ember/-internals/routing/route-managers/outlet-state.ts:65
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/router_js/lib/transition-state.ts:113
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. (×6) — packages/@handlebars/parser/lib/exception.js:61, packages/@glimmer/compiler/lib/compiler.ts:54, packages/@ember/application/index.ts:676, …
`catch (_e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/@ember/routing/lib/routing-service.ts:107
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
5/6 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.
~3.6 `!` null assertions per 1k TypeScript source lines — 335 assertion(s) across the 93910 source line(s) of the 590 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/router_js/lib/router.ts (50), packages/@ember/-internals/meta/lib/meta.ts (22), packages/router_js/lib/transition.ts (16). 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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 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 — 24 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 — 59 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.
AC1 Text alternatives — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ember-source@7.6.0-alpha.1 start / > vite dev / VITE v7.3.7 ready in 1116 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" 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.
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 — N/A — too few peer members to establish a convention across 31 exposed TypeScript types.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 52 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) 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
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the its own test command under node's V8 coverage suite in smoke-tests/node-template/ ran and not one test passed (Error: Failed to load file tests/node/app-boot-test.js), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
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
M4 Documentation accuracy — Not applicable: the 13 current-state document(s) make no claim of a kind M4 checks. 27 claim(s) of kinds M4 does not check were not checked (path 1, command argument 21, install 1, package 1, cd 3); M4 checks only links and versions and artefact counts.
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'.
P2 Observability — This repository's JavaScript/TypeScript source (60 module(s), 745 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AX8 · Test isolation· Production project references a test project · ×18
Production project references a test project: @ember/-internals → internal-test-helpers packages/@ember/-internals/package.json:73— `@ember/-internals` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/application → internal-test-helpers packages/@ember/application/package.json:33— `@ember/application` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/array → internal-test-helpers packages/@ember/array/package.json:29— `@ember/array` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/controller → internal-test-helpers packages/@ember/controller/package.json:22— `@ember/controller` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/debug → internal-test-helpers packages/@ember/debug/package.json:31— `@ember/debug` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/engine → internal-test-helpers packages/@ember/engine/package.json:30— `@ember/engine` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/enumerable → internal-test-helpers packages/@ember/enumerable/package.json:20— `@ember/enumerable` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/instrumentation → internal-test-helpers packages/@ember/instrumentation/package.json:19— `@ember/instrumentation` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/object → internal-test-helpers packages/@ember/object/package.json:38— `@ember/object` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/routing → internal-test-helpers packages/@ember/routing/package.json:40— `@ember/routing` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/runloop → internal-test-helpers packages/@ember/runloop/package.json:21— `@ember/runloop` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/service → internal-test-helpers packages/@ember/service/package.json:20— `@ember/service` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @ember/utils → internal-test-helpers packages/@ember/utils/package.json:24— `@ember/utils` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ember → @ember/test packages/ember/package.json:31— `ember` (production) references the test project `@ember/test`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ember → internal-test-helpers packages/ember/package.json:47— `ember` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ember-template-compiler → internal-test-helpers packages/ember-template-compiler/package.json:38— `ember-template-compiler` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ember-testing → @ember/test packages/ember-testing/package.json:20— `ember-testing` (production) references the test project `@ember/test`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ember-testing → internal-test-helpers packages/ember-testing/package.json:29— `ember-testing` (production) references the test project `internal-test-helpers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Orphaned knowledge REDACTED:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/@ember/-internals/metal/lib/computed.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 packages/@glimmer/compiler/lib/builder/builder-interface.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 packages/@ember/-internals/owner/index.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 packages/@ember/-internals/meta/lib/meta.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 packages/@glimmer/compiler/lib/builder/builder.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.
Project dependency cycle packages/@ember/-internals/package.json:28— The projects @ember/-internals → @ember/application → @ember/-internals (one cycle inside a mutually-dependent group of 28 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): assertion does not throw if destroyables were destroyed packages/@glimmer/destroyable/test/destroyables-test.ts:437— Test method has an empty body — it asserts nothing and exercises no code.
Boundary-crossing change coupling: bucket.ts ↔ route-manager.ts packages/@ember/-internals/routing/route-managers/classic/bucket.ts:1— `packages/@ember/-internals/routing/route-managers/classic/bucket.ts` (context @ember) and `packages/router_js/lib/route-manager.ts` (context router_js) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `d0af7217` refactor: remove enterPromise. non-async getInvokable. invokable cach…; `7d9fbb89` wip: remove getRenderState; `c1133ea2` feat: provide @context via outletState Subscribes to the enterPromise… — run `git show` on any of them.
TodoComment packages/router_js/tests/query_params_test.ts:540— // TODO wat — 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/router_js/tests/route_info_test.ts:196— // TODO: this stub is here because something is setting this and it breaks if there isn't a setter — 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/router_js/tests/router_test.ts:97— // TODO: Support canonical: true — 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/router_js/tests/router_test.ts:5293— // TODO: Review this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/router_js/tests/transition_intent_test.ts:65— // TODO: remove repetition, DRY in to test_helpers. — 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/router_js/lib/router.ts:606— // TODO: Use an assertion? — 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/router_js/lib/transition.ts:55— // Todo: Fix this shit its actually TransitionState | IHandler | undefined | Error — 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/router_js/lib/transition.ts:178— // TODO: this all seems hacky — 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/router_js/lib/transition.ts:338— // TODO: add tests for merged state retry()s — 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/router_js/lib/transition.ts:406— // TODO: Deprecate the current signature — 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/router_js/lib/utils.ts:51— // TODO: Actually check that Dict is QueryParams — 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/internal-test-helpers/lib/build-owner.ts:30— // TODO(SAFETY): this is a lie, and we should use the error thrown below. — 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/internal-test-helpers/lib/node-query.ts:9— // TODO: Can we remove this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/internal-test-helpers/lib/run.ts:26— // TODO: Find a better name 😎 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/internal-test-helpers/lib/test-cases/application.ts:22— // TODO: Review this cast — 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/@glimmer-workspace/integration-tests/test/initial-render-test.ts:224— // TODO handle % % in the testing DSL — 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/@glimmer-workspace/integration-tests/test/initial-render-test.ts:251— // TODO: handle % % in the testing DSL — 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/@glimmer-workspace/integration-tests/test/initial-render-test.ts:285— // TODO: handle % % in the testing DSL — 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/@glimmer-workspace/integration-tests/test/updating-test.ts:1371— // TODO: these type errors reflect real incompatibility with — 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/@glimmer-workspace/integration-tests/test/updating-test.ts:2055— // TODO: port https://github.com/emberjs/ember.js/pull/14082
TodoComment packages/@glimmer-workspace/integration-tests/test/syntax/argument-less-helper-paren-less-invoke-test.ts:86— // TODO: this should work, but doesn't — 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/@glimmer-workspace/integration-tests/test/collections/object-test.ts:83— // TODO: glimmer-vm does not implement each-in, so we can't test this just yet — 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/@glimmer-workspace/integration-tests/test/collections/set-test.ts:300— // TODO: These tests are currently unstable on release, turn back on once — 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/@glimmer-workspace/integration-tests/lib/compile.ts:5— // TODO: This fundamentally has little to do with testing and — 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/@glimmer-workspace/integration-tests/lib/setup-harness.ts:37— // @ts-expect-error TODO: js-reporters not available — 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.
+ 66 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×34
No test reaches this file eslint-rules/no-barrel-imports.cjs: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 lib/overrides.cjs: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/@glimmer/debug/lib/metadata.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 blueprints/component/index.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 blueprints/route/index.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 lib/index.cjs: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/@glimmer/local-debug-babel-plugin/index.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 internal-docs/guides/reactivity/pseudocode/composition.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 blueprints/component-class/index.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 internal-docs/guides/reactivity/pseudocode/primitives.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/loader/lib/index.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 internal-docs/guides/reactivity/pseudocode/tags.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 blueprints/component-addon/index.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 packages/@glimmer/debug/lib/dism/operand-types.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/ember-template-compiler/lib/plugins/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 config/s3ProjectConfig.cjs: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 blueprints/route-addon/index.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 blueprints/component-class-addon/index.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 blueprints/-addon-import.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 packages/ember-template-compiler/lib/system/calculate-location-display.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 blueprints/helper/index.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 blueprints/controller/index.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 blueprints/service/index.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 blueprints/util/index.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 broccoli/glimmer-template-compiler.mjs: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.
Deprecated: @tsconfig/ember package.json:123— @tsconfig/ember 3.0.8, declared in package.json, is marked deprecated by its publisher: "Please use @ember/app-tsconfig or @ember/library-tsconfig instead. These live at https://github.com/ember-cli/tsconfigs". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint package.json:139— eslint 9.39.4, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer-workspace/test-utils/package.json:14— eslint 9.39.4, declared in packages/@glimmer-workspace/test-utils/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/compiler/package.json:57— eslint 9.39.4, declared in packages/@glimmer/compiler/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/constants/package.json:17— eslint 9.39.4, declared in packages/@glimmer/constants/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/debug-util/package.json:19— eslint 9.39.4, declared in packages/@glimmer/debug-util/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/debug/package.json:24— eslint 9.39.4, declared in packages/@glimmer/debug/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/destroyable/package.json:49— eslint 9.39.4, declared in packages/@glimmer/destroyable/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/encoder/package.json:45— eslint 9.39.4, declared in packages/@glimmer/encoder/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/global-context/package.json:41— eslint 9.39.4, declared in packages/@glimmer/global-context/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/interfaces/package.json:30— eslint 9.39.4, declared in packages/@glimmer/interfaces/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/local-debug-flags/package.json:14— eslint 9.39.4, declared in packages/@glimmer/local-debug-flags/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/manager/package.json:52— eslint 9.39.4, declared in packages/@glimmer/manager/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/node/package.json:48— eslint 9.39.4, declared in packages/@glimmer/node/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/opcode-compiler/package.json:53— eslint 9.39.4, declared in packages/@glimmer/opcode-compiler/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/owner/package.json:41— eslint 9.39.4, declared in packages/@glimmer/owner/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/program/package.json:51— eslint 9.39.4, declared in packages/@glimmer/program/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/reference/package.json:50— eslint 9.39.4, declared in packages/@glimmer/reference/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/runtime/package.json:58— eslint 9.39.4, declared in packages/@glimmer/runtime/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/syntax/package.json:55— eslint 9.39.4, declared in packages/@glimmer/syntax/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/util/package.json:47— eslint 9.39.4, declared in packages/@glimmer/util/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/validator/package.json:47— eslint 9.39.4, declared in packages/@glimmer/validator/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/vm/package.json:43— eslint 9.39.4, declared in packages/@glimmer/vm/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/@glimmer/wire-format/package.json:44— eslint 9.39.4, declared in packages/@glimmer/wire-format/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint smoke-tests/app-template/package.json:60— eslint 9.39.4, declared in smoke-tests/app-template/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
+ 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×20
Low cohesion: ClassicRouteManager (LCOM4 11) packages/@ember/-internals/routing/route-managers/classic/manager.ts:60— ClassicRouteManager's methods fall into 11 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 11 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: CurlyComponentManager (LCOM4 9) packages/@ember/-internals/glimmer/lib/component-managers/curly.ts:138— CurlyComponentManager's methods fall into 9 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 9 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: TestRouteManager (LCOM4 8) packages/router_js/tests/test_helpers.ts:177— TestRouteManager's methods fall into 8 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 8 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: Route (LCOM4 7) packages/@ember/routing/route.ts:284— Route's methods fall into 7 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 7 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: Renderer (LCOM4 5) packages/@ember/-internals/glimmer/lib/renderer.ts:182— Renderer's methods fall into 5 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 5 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: Meta (LCOM4 5) packages/@ember/-internals/meta/lib/meta.ts:90— Meta's methods fall into 5 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 5 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: RouterService (LCOM4 5) packages/@ember/routing/router-service.ts:67— RouterService's methods fall into 5 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 5 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: CustomComponentManager (LCOM4 5) packages/@glimmer/manager/lib/public/component.ts:110— CustomComponentManager's methods fall into 5 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 5 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: AbstractTestCase (LCOM4 5) packages/internal-test-helpers/lib/test-cases/abstract.ts:79— AbstractTestCase's methods fall into 5 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 5 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: _LinkTo (LCOM4 4) packages/@ember/-internals/glimmer/lib/components/link-to.ts:269— _LinkTo'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: ResolverImpl (LCOM4 4) packages/@ember/-internals/glimmer/lib/resolver.ts:130— ResolverImpl'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: InternalMixin (LCOM4 4) packages/@ember/object/mixin-internal.ts:459— InternalMixin'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: CustomModifierManager (LCOM4 4) packages/@glimmer/manager/lib/public/modifier.ts:73— CustomModifierManager'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 file (~4 LoC) packages/@glimmer/component/addon-main.cjs— no import path from any entry point (762 application, 66 tooling, 802 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 (~4 LoC) packages/ember-template-compiler/lib/plugins/assert-against-attrs.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/assert-against-named-outlets.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/assert-input-helper-without-block.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/assert-reserved-named-arguments.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/auto-import-builtins.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-each-in-into-each.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-each-track-array.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-in-element.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-quoted-bindings-into-just-bindings.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-resolutions.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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 (~4 LoC) packages/ember-template-compiler/lib/plugins/transform-wrap-mount-and-outlet.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/ember-template-compiler/lib/plugins/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
Off the main sequence: @glimmer/owner — @glimmer/owner: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: @glimmer/util — @glimmer/util: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: ember-testing — ember-testing: abstractness 1.00, instability 0.95, distance 0.95 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: @glimmer/vm — @glimmer/vm: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: @glimmer/syntax — @glimmer/syntax: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @glimmer/destroyable — @glimmer/destroyable: abstractness 0.00, instability 0.16, distance 0.84 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: @ember/canary-features — @ember/canary-features: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @glimmer/validator — @glimmer/validator: abstractness 0.09, instability 0.08, distance 0.83 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: @ember/destroyable — @ember/destroyable: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @glimmer/wire-format — @glimmer/wire-format: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Boundary violation [package:relative-cross-package] broccoli/glimmer-template-compiler.mjs:5— broccoli/glimmer-template-compiler.mjs:5 reaches into another package with a relative path (../packages/ember-template-compiler/minimal.ts) — import the package by name instead.
Boundary violation [package:undeclared-workspace-dep] packages/@glimmer/component/src/-private/component.ts:1— packages/@glimmer/component/src/-private/component.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/@glimmer/component/src/-private/ember-component-manager.ts:1— packages/@glimmer/component/src/-private/ember-component-manager.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/@glimmer/component/src/index.ts:1— packages/@glimmer/component/src/index.ts:1 imports @glimmer/env, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:1— packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:1 reaches into another package with a relative path (../../array.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/managers/internal.d.ts:1— packages/@glimmer/interfaces/lib/managers/internal.d.ts:1 reaches into another package with a relative path (./internal/component.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/managers/internal.d.ts:2— packages/@glimmer/interfaces/lib/managers/internal.d.ts:2 reaches into another package with a relative path (./internal/helper.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/managers/internal/helper.d.ts:2— packages/@glimmer/interfaces/lib/managers/internal/helper.d.ts:2 reaches into another package with a relative path (../helper.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/template.d.ts:1— packages/@glimmer/interfaces/lib/template.d.ts:1 reaches into another package with a relative path (./array.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/@glimmer/interfaces/lib/template.d.ts:5— packages/@glimmer/interfaces/lib/template.d.ts:5 reaches into another package with a relative path (./managers/internal/component.js) — import the package by name instead.
Swallowed exception (empty catch) packages/router_js/lib/route-manager.ts:101— `.then(…, () => {})` 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/router_js/lib/transition-state.ts:113— `.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/@handlebars/parser/lib/exception.js:61— 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/@glimmer/compiler/lib/compiler.ts:54— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/@ember/application/index.ts:676— 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/@ember/-internals/routing/route-managers/outlet-state.ts:53— `.then(…, () => {})` 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/@ember/-internals/routing/route-managers/outlet-state.ts:65— `.then(…, () => {})` 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/@ember/-internals/metal/lib/namespace_search.ts:166— 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/@ember/-internals/container/lib/container.ts:51— 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) eslint-rules/no-barrel-imports.cjs:331— 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.
FileTooLong: lib/parser.js packages/@handlebars/parser/lib/parser.js— FileTooLong — 1717 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 217 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: routing/router.ts packages/@ember/routing/router.ts— FileTooLong — 894 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: EmberRouter (145-1623). The bar is 500 significant lines; this is 394 over it, 1.79× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/router.ts packages/router_js/lib/router.ts— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Router (36-1145). The bar is 500 significant lines; this is 138 over it, 1.28× 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: builder/builder-interface.ts packages/@glimmer/compiler/lib/builder/builder-interface.ts— FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 136 over it, 1.27× 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: opcodes/component.ts packages/@glimmer/runtime/lib/compiled/opcodes/component.ts— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 128 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: v2/normalize.ts packages/@glimmer/syntax/lib/v2/normalize.ts— FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 126 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: routing/route.ts packages/@ember/routing/route.ts— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: Route (284-1831). The bar is 500 significant lines; this is 95 over it, 1.19× 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: builder/builder.ts packages/@glimmer/compiler/lib/builder/builder.ts— FileTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 41 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: EmberRouter packages/@ember/routing/router.ts:145— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: NewTreeBuilder packages/@glimmer/runtime/lib/vm/element-builder.ts:80— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: Router packages/router_js/lib/router.ts:36— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: Route packages/@ember/routing/route.ts:284— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: VM packages/@glimmer/runtime/lib/vm/append.ts:126— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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: Parser packages/@glimmer/syntax/lib/parser.ts:49— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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: StrictModeValidationPass packages/@glimmer/compiler/lib/passes/1-normalization/visitors/strict-mode.ts:19— 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: Printer packages/@glimmer/syntax/lib/generation/printer.ts:62— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
FixmeComment packages/@glimmer/runtime/lib/vm/element-builder.ts:533— // FIXME: All the noops in here indicate a modelling problem — 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.
FixmeComment packages/@glimmer/runtime/lib/dom/operations.ts:64— // FIXME: This does not properly handle <font> with color, face, or — 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.
FixmeComment packages/@glimmer/runtime/lib/compiled/opcodes/expressions.ts:261— // FIXME(mmun): should only need to push the symbol table — 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.
FixmeComment packages/@ember/routing/router.ts:312— // FIXME: Can we remove this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/@ember/array/index-internal.ts:345— // FIXME: When called without initialValue, behavior does not match native behavior — 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.
MethodTooLong: WireFormatDebugger.formatOpcode packages/@glimmer/compiler/lib/wire-format-debug.ts:38— MethodTooLong — formatOpcode 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.
MethodTooLong: TokenizerEventHandlers.parsePossibleBlockParams packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:315— MethodTooLong — parsePossibleBlockParams runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.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.
MethodTooLong: EmberRouter._initRouterJs packages/@ember/routing/router.ts:481— MethodTooLong — _initRouterJs runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: OnModifierState.updateListener packages/@glimmer/runtime/lib/modifiers/on.ts:57— MethodTooLong — updateListener runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: Router.onTransitionSettled packages/router_js/lib/router.ts:189— MethodTooLong — onTransitionSettled runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.
Duplicated block (14 lines × 2 locations) packages/@ember/object/observable-internal.ts:51— packages/@ember/object/observable-internal.ts:51 · packages/@ember/object/observable.ts:329 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) packages/@ember/routing/lib/routing-service.ts:40— packages/@ember/routing/lib/routing-service.ts:40 · packages/@ember/routing/router-service.ts:167 — 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 (14 lines × 2 locations) packages/@glimmer/compiler/lib/builder/builder-interface.ts:202— packages/@glimmer/compiler/lib/builder/builder-interface.ts:202 · packages/@glimmer/compiler/lib/builder/builder-interface.ts:261 — 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 (14 lines × 2 locations) packages/@glimmer/compiler/lib/builder/builder-interface.ts:714— packages/@glimmer/compiler/lib/builder/builder-interface.ts:714 · packages/@glimmer/compiler/lib/builder/builder-interface.ts:786 — 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 (14 lines × 2 locations) packages/@glimmer/validator/lib/collections/weak-map.ts:57— packages/@glimmer/validator/lib/collections/weak-map.ts:57 · packages/@glimmer/validator/lib/collections/weak-set.ts:73 — 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.
Unused dependency '@ember/canary-features' packages/@ember/-internals/package.json:30— Declared in packages/@ember/-internals/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 '@ember/canary-features' packages/@ember/template-compilation/package.json:11— Declared in packages/@ember/template-compilation/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 '@ember/canary-features' packages/@ember/version/package.json:13— Declared in packages/@ember/version/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 '@ember/canary-features' packages/ember/package.json:12— Declared in packages/ember/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 '@ember/canary-features' packages/ember-template-compiler/package.json:14— Declared in packages/ember-template-compiler/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/@ember/routing/router.ts packages/@ember/routing/router.ts:481— packages/@ember/routing/router.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in EmberRouter._initRouterJs at line 481. 1 of those changes was a fix/bug commit, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:13:47 -05:00' --until='2026-11-16 22:13:47 -05:00' --full-history --no-merges -- packages/@ember/routing/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/router_js/lib/router.ts packages/router_js/lib/router.ts:189— packages/router_js/lib/router.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Router.onTransitionSettled at line 189. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:13:47 -05:00' --until='2026-11-16 22:13:47 -05:00' --full-history --no-merges -- packages/router_js/lib/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/router_js/lib/transition-intent/named-transition-intent.ts packages/router_js/lib/transition-intent/named-transition-intent.ts:42— packages/router_js/lib/transition-intent/named-transition-intent.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in NamedTransitionIntent.applyToHandlers at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:13:47 -05:00' --until='2026-11-16 22:13:47 -05:00' --full-history --no-merges -- packages/router_js/lib/transition-intent/named-transition-intent.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/@ember/object/compat.ts packages/@ember/object/compat.ts:127— packages/@ember/object/compat.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in compat.dependentKeyCompat at line 127. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:13:47 -05:00' --until='2026-11-16 22:13:47 -05:00' --full-history --no-merges -- packages/@ember/object/compat.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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap packages/@glimmer/syntax/lib/source/span-list.ts:48— `loc` is exported and takes `span: HasSourceSpan` from its caller, and it calls itself at line 48 (`loc`) with a piece of `span` — and nowhere in `loc` 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 `loc` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/@glimmer/debug/lib/metadata.ts:213— `buildSingleMeta` is exported, takes a document from its caller (line 194) and hands it to `stringify`, which calls itself at line 213 (`stringify`) with a piece of `o` (and at line 219) — and nowhere in `stringify` 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 `stringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/@glimmer/debug/lib/render/fragment.ts:362— `intoFragment` is exported, takes a document from its caller (line 349) and hands it to `intoFragments`, which calls itself at line 362 (`intoFragments`) with a piece of `value` — and nowhere in `intoFragments` 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 `intoFragments` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/@ember/-internals/utils/lib/to-string.ts:29— `toString` is exported and takes `obj: any | undefined | null` from its caller, and it calls itself at line 29 (`toString`) with a piece of `obj` — and nowhere in `toString` 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 `toString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
No assertions: (unnamed test) packages/@glimmer-workspace/integration-tests/test/support.ts:56— 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: checking isDestroying does not trigger assertion packages/@glimmer/destroyable/test/destroyables-test.ts:448— 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: checking isDestroyed does not trigger assertion packages/@glimmer/destroyable/test/destroyables-test.ts:458— 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.
Duplicated block (17 lines × 2 locations) packages/@glimmer/compiler/lib/wire-format-debug.ts:79— packages/@glimmer/compiler/lib/wire-format-debug.ts:79 · packages/@glimmer/compiler/lib/wire-format-debug.ts:101 — 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 (17 lines × 2 locations) packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:131— packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:131 · packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:178 — 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 (17 lines × 2 locations) packages/@glimmer/syntax/lib/v1/parser-builders.ts:341— packages/@glimmer/syntax/lib/v1/parser-builders.ts:341 · packages/@glimmer/syntax/lib/v1/parser-builders.ts:378 — 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.
Dead file (~3 LoC) blueprints/helper-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~3 LoC) blueprints/initializer-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~3 LoC) blueprints/instance-initializer-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~1 LoC) packages/@handlebars/parser/src/parser-suffix.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~1 LoC) packages/ember-template-compiler/lib/-internal.ts— no import path from any entry point (762 application, 66 tooling, 802 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 (~1 LoC) packages/ember-template-compiler/lib/plugins/utils.ts— no import path from any entry point (762 application, 66 tooling, 802 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 '@glimmer/global-context' packages/@glimmer-workspace/integration-tests/package.json:20— Declared in packages/@glimmer-workspace/integration-tests/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 '@glimmer/global-context' packages/@glimmer-workspace/integration-tests/test/package.json:13— Declared in packages/@glimmer-workspace/integration-tests/test/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 '@glimmer/global-context' packages/@glimmer/destroyable/test/package.json:8— Declared in packages/@glimmer/destroyable/test/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 packages/@glimmer/runtime/lib/dom/operations.ts:97— `html` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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/@glimmer/runtime/lib/dom/operations.ts:100— `html` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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/@glimmer/runtime/lib/dom/operations.ts:108— `html` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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.
(anonymous)::(anonymous)::anonymous (cyclomatic 54) packages/@handlebars/parser/lib/parser.js:1756— (anonymous)::(anonymous)::anonymous has cyclomatic complexity 54 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: (anonymous)::anonymous (cyclomatic 80) 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.
(anonymous)::parse (cyclomatic 35) packages/@handlebars/parser/lib/parser.js:1251— (anonymous)::parse has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: (anonymous)::anonymous (cyclomatic 80) 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.
(anonymous)::parse (cognitive 63) packages/@handlebars/parser/lib/parser.js:1251— (anonymous)::parse has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (40 pts), boolean chains 12, loops 3 (5 pts), ternaries 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::(anonymous)::next (cognitive 23) packages/@handlebars/parser/lib/parser.js:1642— (anonymous)::(anonymous)::next has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: EmberRouter packages/@ember/routing/router.ts:145— ClassTooLong — 654 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 254 over it, 1.64× 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: Router packages/router_js/lib/router.ts:36— ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 169 over it, 1.42× 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 hub: wire-format-debug.ts → builder.ts, call.ts, expressions.ts packages/@glimmer/compiler/lib/wire-format-debug.ts— `packages/@glimmer/compiler/lib/wire-format-debug.ts` changes together with 3 other files — `packages/@glimmer/compiler/lib/builder/builder.ts`, `packages/@glimmer/compiler/lib/passes/1-normalization/keywords/call.ts`, `packages/@glimmer/compiler/lib/passes/2-encoding/expressions.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: component.ts → resolution.ts, constants.ts, render.ts packages/@glimmer/runtime/lib/compiled/opcodes/component.ts— `packages/@glimmer/runtime/lib/compiled/opcodes/component.ts` changes together with 3 other files — `packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts`, `packages/@glimmer/program/lib/constants.ts`, `packages/@glimmer/runtime/lib/render.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change coupling: compilable-template.ts ↔ append.ts packages/@glimmer/opcode-compiler/lib/compilable-template.ts:1— `packages/@glimmer/opcode-compiler/lib/compilable-template.ts` and `packages/@glimmer/runtime/lib/vm/append.ts` change together 60% of the time (6 of the 10 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 6 shared commits counted here, the most recent 3 are `00e8785e` Adopt improved terminology and tracing infra; `240e69fb` [REFACTOR] Simplify heap; `e77c7385` convert wireformat objects to arrays — run `git show` on any of them.
Change coupling: call.ts ↔ expressions.ts packages/@glimmer/compiler/lib/passes/1-normalization/keywords/call.ts:1— `packages/@glimmer/compiler/lib/passes/1-normalization/keywords/call.ts` and `packages/@glimmer/runtime/lib/compiled/opcodes/expressions.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 5 shared commits counted here, the most recent 3 are `e7bcee42` Move curried types to constants (#1664); `c1d2b11e` [FEATURE] Upstreams {{log}} keyword; `7923ecba` [REFACTOR] Make `-get-dynamic-var` a keyword — run `git show` on any of them.
End-of-life runtime: Node.js 18 packages/@glimmer/component/package.json:46— packages/@glimmer/component/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.
End-of-life runtime: Node.js 20 package.json:179— package.json declares Node.js 20 as this project's engines.node, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
IC1 · Incompleteness & stubs· Both branches are identical · ×2
Both branches are identical — the condition decides nothing packages/@ember/object/lib/computed/reduce_computed_macros.ts:81— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/@ember/object/lib/computed/reduce_computed_macros.ts:1368— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Hollow method — returns a constant without doing the work packages/@glimmer/manager/lib/internal/api.ts:238— `hasDefaultComponentManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work packages/@glimmer/manager/lib/internal/api.ts:246— `hasDefaultModifierManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Duplication concentrated across 4 sibling directories (6 clone groups) packages/@ember/template-compiler/lib/plugins/index.ts:15— 6 duplicated blocks under packages/ have copies in at least two of the sibling directories @ember, @glimmer, ember-template-compiler, router_js — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (6 clone groups) packages/@ember/-internals/views/lib/views/core_view.ts:79— 6 duplicated blocks under packages/@ember/ have copies in at least two of the sibling directories -internals, controller, routing, service — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×2
Duplicated block with local edits (42 matched lines × 2 locations) REDACTED:25— REDACTED:25 · packages/ember-template-compiler/lib/system/compile-options.ts:10 — the two spans are one implementation copied and then locally edited — 268 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 (42 matched lines × 2 locations) packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:261— packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:261 · packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:351 — the two spans are one implementation copied and then locally edited — 233 tokens are still identical, in the same order in both spans, 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 (36 lines × 2 locations) packages/@ember/-internals/utils/lib/get-debug-name.ts:22— packages/@ember/-internals/utils/lib/get-debug-name.ts:22 · packages/@glimmer/debug-util/lib/debug-to-string.ts:23 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (36 lines × 2 locations) packages/@ember/routing/route.ts:789— packages/@ember/routing/route.ts:789 · packages/@ember/routing/router.ts:226 — 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 (22 lines × 2 locations) blueprints/component-addon/index.js:6— blueprints/component-addon/index.js:6 · blueprints/component-class-addon/index.js:6 — 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) packages/@ember/template-compiler/lib/system/calculate-location-display.ts:3— packages/@ember/template-compiler/lib/system/calculate-location-display.ts:3 · packages/ember-template-compiler/lib/system/calculate-location-display.ts:3 — 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 (21 lines × 2 locations) packages/@ember/object/lib/computed/reduce_computed_macros.ts:417— packages/@ember/object/lib/computed/reduce_computed_macros.ts:417 · packages/@ember/object/lib/computed/reduce_computed_macros.ts:646 — 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 (21 lines × 2 locations) rollup.config.mjs:136— rollup.config.mjs:136 · rollup.config.mjs:157 — 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 (18 lines × 2 locations) packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:319— packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:319 · packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:345 — 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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `kw(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything.
Duplicated block (18 lines × 2 locations) packages/@glimmer/validator/lib/collections/weak-map.ts:78— packages/@glimmer/validator/lib/collections/weak-map.ts:78 · packages/@glimmer/validator/lib/collections/weak-set.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.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×2
Duplicated block with local edits (15 matched lines × 2 locations) packages/@glimmer/manager/lib/public/component.ts:120— packages/@glimmer/manager/lib/public/component.ts:120 · packages/@glimmer/manager/lib/public/helper.ts:82 — the two spans are one implementation copied and then locally edited — 74 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 (15 matched lines × 2 locations) packages/@glimmer/manager/lib/public/helper.ts:82— packages/@glimmer/manager/lib/public/helper.ts:82 · packages/@glimmer/manager/lib/public/modifier.ts:83 — the two spans are one implementation copied and then locally edited — 74 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.
Complex function (anonymous) (cyclomatic 15, cognitive 14) packages/@ember/object/compat.ts:153— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 15, cognitive 14) packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:214— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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.
Dead file (~12 LoC) blueprints/initializer/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~12 LoC) blueprints/instance-initializer/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 'ember-cli-dependency-checker' package.json:136— Declared in the root 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 'ember-cli-dependency-checker' smoke-tests/app-template/package.json:46— Declared in smoke-tests/app-template/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 '@ember/template-factory' packages/@ember/-internals/package.json:46— Declared in packages/@ember/-internals/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 '@ember/template-factory' packages/ember/package.json:30— Declared in packages/ember/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 'type-fest' packages/@glimmer/interfaces/package.json:27— Declared in packages/@glimmer/interfaces/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 'type-fest' packages/@glimmer/opcode-compiler/package.json:56— Declared in packages/@glimmer/opcode-compiler/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 'loader.js' packages/router_js/package.json:19— Declared in packages/router_js/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 'loader.js' smoke-tests/app-template/package.json:66— Declared in smoke-tests/app-template/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 'ember-cli-babel' smoke-tests/app-template/package.json:44— Declared in smoke-tests/app-template/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 'ember-cli-babel' smoke-tests/scenarios/package.json:13— Declared in smoke-tests/scenarios/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 'ember-template-imports' smoke-tests/app-template/package.json:58— Declared in smoke-tests/app-template/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 'ember-template-imports' smoke-tests/scenarios/package.json:14— Declared in smoke-tests/scenarios/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.
WireFormatDebugger.formatOpcode (cyclomatic 49) packages/@glimmer/compiler/lib/wire-format-debug.ts:38— WireFormatDebugger.formatOpcode has cyclomatic complexity 49 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OnModifierState.updateListener (cyclomatic 32) packages/@glimmer/runtime/lib/modifiers/on.ts:57— OnModifierState.updateListener has cyclomatic complexity 32 (threshold 15). Of this number, 31 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.
SerializeBlockContext.#stringify (cyclomatic 30) packages/@glimmer/debug/lib/dism/opcode.ts:80— SerializeBlockContext.#stringify has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TokenizerEventHandlers.parsePossibleBlockParams (cyclomatic 29) packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:315— TokenizerEventHandlers.parsePossibleBlockParams has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 439, 389, 487, …). 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.
Router.onTransitionSettled (cyclomatic 27) packages/router_js/lib/router.ts:189— Router.onTransitionSettled has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 263). 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.
chain-tags.getChainTags (cyclomatic 26) packages/@ember/-internals/metal/lib/chain-tags.ts:59— chain-tags.getChainTags has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
collectNamedExports (cyclomatic 25) eslint-rules/no-barrel-imports.cjs:174— collectNamedExports has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EmberRouter._initRouterJs (cyclomatic 24) packages/@ember/routing/router.ts:481— EmberRouter._initRouterJs has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
compare.compare (cyclomatic 24) packages/@ember/utils/lib/compare.ts:100— compare.compare has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
NamedTransitionIntent.applyToHandlers (cyclomatic 22) packages/router_js/lib/transition-intent/named-transition-intent.ts:42— NamedTransitionIntent.applyToHandlers 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.
core.initialize (cyclomatic 21) packages/@ember/object/core.ts:72— core.initialize 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.
components.InvokeStaticComponent (cyclomatic 21) packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.ts:194— components.InvokeStaticComponent 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.
create.handleImport (cyclomatic 21) eslint-rules/no-barrel-imports.cjs:508— create.handleImport has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compat.dependentKeyCompat (cyclomatic 20) packages/@ember/object/compat.ts:127— compat.dependentKeyCompat has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 153, decorator). 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.
public-builders.buildElement (cyclomatic 20) packages/@glimmer/syntax/lib/v1/public-builders.ts:191— public-builders.buildElement has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Fragment.appendTo (cyclomatic 19) packages/@glimmer/debug/lib/render/fragment.ts:229— Fragment.appendTo has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
whitespace-control.WhitespaceControl.Program (cyclomatic 19) packages/@handlebars/parser/lib/whitespace-control.js:8— whitespace-control.WhitespaceControl.Program 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.
builder.buildStatement (cyclomatic 18) packages/@glimmer/compiler/lib/builder/builder.ts:232— builder.buildStatement has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
component.APPEND_OPCODES.add() (cyclomatic 18) packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:162— component.APPEND_OPCODES.add() has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create.handleExportNamed (cyclomatic 18) eslint-rules/no-barrel-imports.cjs:593— create.handleExportNamed has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
inspect.inspectValue (cyclomatic 17) packages/@ember/debug/lib/inspect.ts:37— inspect.inspectValue 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.
Component.init (cyclomatic 17) packages/@ember/-internals/glimmer/lib/component.ts:915— Component.init has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
query-params.finalizeQueryParamChange (cyclomatic 17) packages/@ember/-internals/routing/route-managers/classic/query-params.ts:103— query-params.finalizeQueryParamChange 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.
array_events.arrayContentDidChange (cyclomatic 16) packages/@ember/-internals/metal/lib/array_events.ts:30— array_events.arrayContentDidChange 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.
mixin-internal.mergeProps (cyclomatic 16) packages/@ember/object/mixin-internal.ts:284— mixin-internal.mergeProps 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.
EmberRouter._hydrateUnsuppliedQueryParams (cyclomatic 16) packages/@ember/routing/router.ts:1424— EmberRouter._hydrateUnsuppliedQueryParams has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VmSnapshotArrayDiff.describe (cyclomatic 16) packages/@glimmer/debug/lib/vm/snapshot.ts:121— VmSnapshotArrayDiff.describe 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.
Printer.BlockStatement (cyclomatic 16) packages/@glimmer/syntax/lib/generation/printer.ts:352— Printer.BlockStatement 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: Printer.Node (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.
handlebars-node-visitors.acceptCallNodes (cyclomatic 16) packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:653— handlebars-node-visitors.acceptCallNodes 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: HandlebarsNodeVisitors.MustacheStatement (cyclomatic 20) 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.
PartialBlockStatement (cyclomatic 16) packages/@handlebars/parser/lib/whitespace-control.js:67— PartialBlockStatement 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.
chain-tags.getChainTags (cognitive 53) packages/@ember/-internals/metal/lib/chain-tags.ts:59— chain-tags.getChainTags has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (40 pts), boolean chains 6, loops 2 (4 pts), ternaries 1 (3 pts) (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.
collectNamedExports (cognitive 49) eslint-rules/no-barrel-imports.cjs:174— collectNamedExports has cognitive complexity 49 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 4 (11 pts), loops 4 (8 pts), boolean chains 5, other 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Meta.flattenedListeners (cognitive 42) packages/@ember/-internals/meta/lib/meta.ts:490— Meta.flattenedListeners has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (37 pts), loops 1 (5 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.
core.initialize (cognitive 40) packages/@ember/object/core.ts:72— core.initialize has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (30 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 19). 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.
OnModifierState.updateListener (cognitive 38) packages/@glimmer/runtime/lib/modifiers/on.ts:57— OnModifierState.updateListener has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (27 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 10). Of this number, 37 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.
Router.onTransitionSettled (cognitive 35) packages/router_js/lib/router.ts:189— Router.onTransitionSettled has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 5, loops 5, error handling 1 (nesting depth added 11). Most of this is not in the body itself: 12 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 263). 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.
TokenizerEventHandlers.parsePossibleBlockParams (cognitive 34) packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:315— TokenizerEventHandlers.parsePossibleBlockParams has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 7, loops 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 389, 439, 487, …). 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.
ListBlockOpcode.sync (cognitive 33) packages/@glimmer/runtime/lib/vm/update.ts:255— ListBlockOpcode.sync has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NamedTransitionIntent.applyToHandlers (cognitive 33) packages/router_js/lib/transition-intent/named-transition-intent.ts:42— NamedTransitionIntent.applyToHandlers has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
query-params.finalizeQueryParamChange (cognitive 31) packages/@ember/-internals/routing/route-managers/classic/query-params.ts:103— query-params.finalizeQueryParamChange has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
components.InvokeStaticComponent (cognitive 31) packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.ts:194— components.InvokeStaticComponent has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 5 (8 pts), ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.getChangelist (cognitive 31) packages/router_js/lib/utils.ts:117— utils.getChangelist has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 3 (7 pts), boolean chains 1, ternaries 1 (nesting depth added 18). 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.
mixin-internal.mergeProps (cognitive 30) packages/@ember/object/mixin-internal.ts:284— mixin-internal.mergeProps has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 3, loops 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EmberRouter._initRouterJs (cognitive 28) packages/@ember/routing/router.ts:481— EmberRouter._initRouterJs has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 6, loops 1 (nesting depth added 4). Of this number, 26 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
whitespace-control.WhitespaceControl.Program (cognitive 28) packages/@handlebars/parser/lib/whitespace-control.js:8— whitespace-control.WhitespaceControl.Program has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 8, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VmSnapshotArrayDiff.describe (cognitive 27) packages/@glimmer/debug/lib/vm/snapshot.ts:121— VmSnapshotArrayDiff.describe has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.handleImport (cognitive 27) eslint-rules/no-barrel-imports.cjs:508— create.handleImport has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, ternaries 3 (5 pts), loops 2 (nesting depth added 7). Of this number, 25 points are the body's own statements and 2 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.
addonsInfoFor (cognitive 26) lib/overrides.cjs:38— addonsInfoFor has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 3 (6 pts), loops 2 (5 pts), boolean chains 3 (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.
array_events.arrayContentDidChange (cognitive 25) packages/@ember/-internals/metal/lib/array_events.ts:30— array_events.arrayContentDidChange has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 3 (6 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.
EmberRouter._hydrateUnsuppliedQueryParams (cognitive 25) packages/@ember/routing/router.ts:1424— EmberRouter._hydrateUnsuppliedQueryParams has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 11). Of this number, 17 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fragment.appendTo (cognitive 25) packages/@glimmer/debug/lib/render/fragment.ts:229— Fragment.appendTo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (5 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 10). Of this number, 16 points are the body's own statements and 9 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.
EmberRouter.getRoute (cognitive 23) packages/@ember/routing/router.ts:387— EmberRouter.getRoute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 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.
Overrides.constructor (cognitive 22) lib/overrides.cjs:105— Overrides.constructor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3, 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.
mixin-internal.mergeMixins (cognitive 22) packages/@ember/object/mixin-internal.ts:226— mixin-internal.mergeMixins has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 2, loops 1 (nesting depth added 12). Of this number, 17 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SerializeBlockContext.#stringify (cognitive 22) packages/@glimmer/debug/lib/dism/opcode.ts:80— SerializeBlockContext.#stringify has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
public-builders.buildElement (cognitive 22) packages/@glimmer/syntax/lib/v1/public-builders.ts:191— public-builders.buildElement has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10 (nesting depth added 1). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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.
HandlebarsNodeVisitors.BlockStatement (cognitive 22) packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:113— HandlebarsNodeVisitors.BlockStatement has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
get-template-locals.getPathName (cognitive 22) packages/@glimmer/syntax/lib/get-template-locals.ts:15— get-template-locals.getPathName has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Component.init (cognitive 21) packages/@ember/-internals/glimmer/lib/component.ts:915— Component.init has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 7). Of this number, 17 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.
create.handleExportNamed (cognitive 21) eslint-rules/no-barrel-imports.cjs:593— create.handleExportNamed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, loops 2, ternaries 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 2 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.
compare.compare (cognitive 20) packages/@ember/utils/lib/compare.ts:100— compare.compare has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8, loops 1 (2 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WireFormatDebugger.formatOpcode (cognitive 20) packages/@glimmer/compiler/lib/wire-format-debug.ts:38— WireFormatDebugger.formatOpcode has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (6 pts), match/switch 1 (2 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.
MonomorphicTagImpl.[COMPUTE] (cognitive 20) packages/@glimmer/validator/lib/validators.ts:132— MonomorphicTagImpl.[COMPUTE] has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 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.
manager.buildClassicInvokable (cognitive 19) packages/@ember/-internals/routing/route-managers/classic/manager.ts:404— manager.buildClassicInvokable has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 1 (4 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.
RehydrateTree.clearMismatch (cognitive 19) packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:164— RehydrateTree.clearMismatch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (6 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
map.trackedMap (cognitive 19) packages/@glimmer/validator/lib/collections/map.ts:11— map.trackedMap has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 49, storageFor, dirtyStorageFor, …). 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.
resolvePackages.resolveId (cognitive 19) rollup.config.mjs:446— resolvePackages.resolveId has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, loops 1 (2 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.
PartialBlockStatement (cognitive 19) packages/@handlebars/parser/lib/whitespace-control.js:67— PartialBlockStatement has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
inspect.inspectValue (cognitive 18) packages/@ember/debug/lib/inspect.ts:37— inspect.inspectValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (6 pts), boolean chains 1, match/switch 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.
HandlebarsNodeVisitors.PathExpression (cognitive 18) packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:451— HandlebarsNodeVisitors.PathExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (18 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
set.trackedSet (cognitive 18) packages/@glimmer/validator/lib/collections/set.ts:11— set.trackedSet has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (18 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 42, storageFor, dirtyStorageFor, …). 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.
helpers.preparePath (cognitive 18) packages/@handlebars/parser/lib/helpers.js:44— helpers.preparePath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Transition.constructor (cognitive 18) packages/router_js/lib/transition.ts:112— Transition.constructor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, loops 1 (2 pts) (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.
query-params.queryParamsDidChange (cognitive 17) packages/@ember/-internals/routing/route-managers/classic/query-params.ts:51— query-params.queryParamsDidChange has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
if-unless.assertIfUnlessInlineKeyword.<returned closure> (cognitive 17) packages/@glimmer/compiler/lib/passes/1-normalization/keywords/utils/if-unless.ts:12— if-unless.assertIfUnlessInlineKeyword.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 4, boolean chains 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.
UpdateDynamicModifierOpcode.evaluate (cognitive 17) packages/@glimmer/runtime/lib/compiled/opcodes/dom.ts:354— UpdateDynamicModifierOpcode.evaluate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 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.
dom.APPEND_OPCODES.add() (cognitive 17) packages/@glimmer/runtime/lib/compiled/opcodes/dom.ts:207— dom.APPEND_OPCODES.add() has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1 (nesting depth added 4). 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 223). 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.
component.APPEND_OPCODES.add() (cognitive 17) packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:304— component.APPEND_OPCODES.add() has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 3 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementChildren.assertComponent (cognitive 17) packages/@glimmer/syntax/lib/v2/normalize.ts:1000— ElementChildren.assertComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
property_get._getProp (cognitive 16) packages/@ember/-internals/metal/lib/property_get.ts:100— property_get._getProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (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.
EmberRouter._queryParamsFor (cognitive 16) packages/@ember/routing/router.ts:1318— EmberRouter._queryParamsFor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 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.
EmberRouter._fullyScopeQueryParams (cognitive 16) packages/@ember/routing/router.ts:1382— EmberRouter._fullyScopeQueryParams has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 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.
component.APPEND_OPCODES.add() (cognitive 16) packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:162— component.APPEND_OPCODES.add() has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the its own test command under node's V8 coverage suite in smoke-tests/node-template/ ran and not one test passed (Error: Failed to load file tests/node/app-boot-test.js), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body — does nothing with its inputs packages/router_js/lib/router.ts:107— `scheduleOutletUpdate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Sync-over-async blocking bin/benchmark/utils.mjs:166— `existsSync` in `prepareApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplication concentrated across 8 sibling directories (6 clone groups) blueprints/component-class/index.js:63— 6 duplicated blocks under blueprints/ have copies in at least two of the sibling directories component, component-addon, component-class, component-class-addon, controller, route (+2 more sibling(s) not listed) — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (44 matched lines × 2 locations) · ×1
Duplicated block with local edits (44 matched lines × 2 locations) packages/@glimmer/validator/lib/collections/map.ts:63— packages/@glimmer/validator/lib/collections/map.ts:63 · packages/@glimmer/validator/lib/collections/set.ts:52 — the two spans are one implementation copied and then locally edited — 242 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 (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) packages/@ember/template-compiler/lib/plugins/index.ts:15— packages/@ember/template-compiler/lib/plugins/index.ts:15 · packages/ember-template-compiler/lib/plugins/index.ts:15 — the two spans are one implementation copied and then locally edited — 112 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 (38 lines × 2 locations) packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:93— packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:93 · packages/@glimmer/compiler/lib/passes/1-normalization/keywords/block.ts:155 — 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 (35 lines × 2 locations) blueprints/component-class/index.js:63— blueprints/component-class/index.js:63 · blueprints/component/index.js:179 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (31 lines × 2 locations) eslint-rules/no-barrel-imports.cjs:554— eslint-rules/no-barrel-imports.cjs:554 · eslint-rules/no-barrel-imports.cjs:628 — 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 (30 lines × 2 locations) packages/@glimmer/debug/lib/debug.ts:101— packages/@glimmer/debug/lib/debug.ts:101 · packages/@glimmer/debug/lib/dism/dism.ts:27 — 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 (24 matched lines × 2 locations) · ×1
Duplicated block with local edits (24 matched lines × 2 locations) packages/@ember/-internals/metal/lib/computed.ts:397— packages/@ember/-internals/metal/lib/computed.ts:397 · packages/@ember/-internals/metal/lib/computed.ts:561 — the two spans are one implementation copied and then locally edited — 174 tokens are still identical, in the same order in both spans, 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 (24 lines × 2 locations) packages/@glimmer/validator/lib/collections/set.ts:17— packages/@glimmer/validator/lib/collections/set.ts:17 · packages/@glimmer/validator/lib/collections/weak-set.ts:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (23 lines × 2 locations) packages/@glimmer/validator/lib/collections/map.ts:24— packages/@glimmer/validator/lib/collections/map.ts:24 · packages/@glimmer/validator/lib/collections/weak-map.ts:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (21 lines × 3 locations) packages/@ember/-internals/views/lib/views/core_view.ts:79— packages/@ember/-internals/views/lib/views/core_view.ts:79 · packages/@ember/routing/route.ts:789 · packages/@ember/routing/router.ts:226 — 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 (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) packages/@ember/object/events.ts:8— packages/@ember/object/events.ts:8 · packages/@ember/object/events.ts:43 — the two spans are one implementation copied and then locally edited — 128 tokens are still identical, in the same order in both spans, 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 (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) packages/@ember/-internals/metal/lib/array_events.ts:5— packages/@ember/-internals/metal/lib/array_events.ts:5 · packages/@ember/-internals/metal/lib/array_events.ts:30 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both spans, 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 (17 lines × 3 locations) packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:394— packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:394 · packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:442 · packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:492 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) packages/@ember/-internals/metal/lib/injected_property.ts:71— packages/@ember/-internals/metal/lib/injected_property.ts:71 · packages/@ember/-internals/metal/lib/injected_property.ts:112 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, 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 (16 lines × 2 locations) packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:94— packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:94 · packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts:122 — 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 (15 lines × 2 locations) packages/@glimmer/runtime/lib/environment.ts:63— packages/@glimmer/runtime/lib/environment.ts:63 · packages/@glimmer/runtime/lib/environment.ts:80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) packages/@ember/-internals/glimmer/lib/components/input.ts:221— packages/@ember/-internals/glimmer/lib/components/input.ts:221 · packages/@ember/-internals/glimmer/lib/components/textarea.ts:133 — the two spans are one implementation copied and then locally edited — 81 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.
Complex function anonymous (cyclomatic 54, cognitive 13) packages/@handlebars/parser/lib/parser.js:1756— anonymous has cyclomatic complexity 54 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 formatOpcode (cyclomatic 49, cognitive 20) packages/@glimmer/compiler/lib/wire-format-debug.ts:38— formatOpcode has cyclomatic complexity 49 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 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 (top-level) (cyclomatic 36, cognitive 57) packages/router_js/lib/transition-intent/named-transition-intent.ts:2— (top-level) has cyclomatic complexity 36 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 parse (cyclomatic 35, cognitive 63) packages/@handlebars/parser/lib/parser.js:1251— parse has cyclomatic complexity 35 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function assert (cyclomatic 33, cognitive 50) packages/internal-test-helpers/lib/ember-dev/method-call-tracker.ts:72— assert has cyclomatic complexity 33 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateListener (cyclomatic 31, cognitive 39) packages/@glimmer/runtime/lib/modifiers/on.ts:57— updateListener has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function #stringify (cyclomatic 30, cognitive 22) packages/@glimmer/debug/lib/dism/opcode.ts:80— #stringify has cyclomatic complexity 30 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getChainTags (cyclomatic 26, cognitive 59) packages/@ember/-internals/metal/lib/chain-tags.ts:59— getChainTags has cyclomatic complexity 26 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 collectNamedExports (cyclomatic 25, cognitive 49) eslint-rules/no-barrel-imports.cjs:174— collectNamedExports has cyclomatic complexity 25 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkCall (cyclomatic 25, cognitive 16) tests/node-vitest/lib/detect.js:190— checkCall has cyclomatic complexity 25 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 compare (cyclomatic 24, cognitive 20) packages/@ember/utils/lib/compare.ts:100— compare has cyclomatic complexity 24 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 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 initialize (cyclomatic 21, cognitive 40) packages/@ember/object/core.ts:72— initialize has cyclomatic complexity 21 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 InvokeStaticComponent (cyclomatic 21, cognitive 31) packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.ts:194— InvokeStaticComponent has cyclomatic complexity 21 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.
R2 · Cyclomatic Complexity· Complex function Program (cyclomatic 19, cognitive 28) · ×1
Complex function Program (cyclomatic 19, cognitive 28) packages/@handlebars/parser/lib/whitespace-control.js:8— Program has cyclomatic complexity 19 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 handleImport (cyclomatic 19, cognitive 25) eslint-rules/no-barrel-imports.cjs:508— handleImport 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 buildElement (cyclomatic 19, cognitive 22) packages/@glimmer/syntax/lib/v1/public-builders.ts:191— buildElement has cyclomatic complexity 19 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 23) packages/router_js/lib/router.ts:263— (anonymous) has cyclomatic complexity 18 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 appendTo (cyclomatic 18, cognitive 18) packages/@glimmer/debug/lib/render/fragment.ts:229— appendTo has cyclomatic complexity 18 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 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/@glimmer/runtime/lib/compiled/opcodes/component.ts:162— (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 buildStatement (cyclomatic 18, cognitive 15) packages/@glimmer/compiler/lib/builder/builder.ts:232— buildStatement has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 (top-level) (cyclomatic 18, cognitive 11) packages/@ember/-internals/browser-environment/lib/has-dom.ts:2— (top-level) has cyclomatic complexity 18 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 finalizeQueryParamChange (cyclomatic 17, cognitive 31) packages/@ember/-internals/routing/route-managers/classic/query-params.ts:103— finalizeQueryParamChange has cyclomatic complexity 17 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 inspectValue (cyclomatic 17, cognitive 17) packages/@ember/debug/lib/inspect.ts:37— inspectValue has cyclomatic complexity 17 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 mergeProps (cyclomatic 16, cognitive 30) packages/@ember/object/mixin-internal.ts:284— mergeProps has cyclomatic complexity 16 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 BlockStatement (cyclomatic 16, cognitive 28) packages/@glimmer/syntax/lib/generation/printer.ts:352— BlockStatement has cyclomatic complexity 16 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 describe (cyclomatic 16, cognitive 27) packages/@glimmer/debug/lib/vm/snapshot.ts:121— describe has cyclomatic complexity 16 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function arrayContentDidChange (cyclomatic 16, cognitive 25) packages/@ember/-internals/metal/lib/array_events.ts:30— arrayContentDidChange has cyclomatic complexity 16 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 handleExportNamed (cyclomatic 16, cognitive 19) eslint-rules/no-barrel-imports.cjs:593— handleExportNamed has cyclomatic complexity 16 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 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 PartialBlockStatement (cyclomatic 16, cognitive 19) packages/@handlebars/parser/lib/whitespace-control.js:67— PartialBlockStatement has cyclomatic complexity 16 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 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 acceptCallNodes (cyclomatic 16, cognitive 11) packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:653— acceptCallNodes has cyclomatic complexity 16 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function next (cyclomatic 15, cognitive 23) · ×1
Complex function next (cyclomatic 15, cognitive 23) packages/@handlebars/parser/lib/parser.js:1642— next has cyclomatic complexity 15 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 getPathName (cyclomatic 15, cognitive 22) packages/@glimmer/syntax/lib/get-template-locals.ts:15— getPathName has cyclomatic complexity 15 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 init (cyclomatic 15, cognitive 18) packages/@ember/-internals/glimmer/lib/component.ts:915— init has cyclomatic complexity 15 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 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 testOverrideGlobalContext (cyclomatic 15, cognitive 15) packages/@glimmer/global-context/index.ts:209— testOverrideGlobalContext has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 sync (cyclomatic 14, cognitive 33) packages/@glimmer/runtime/lib/vm/update.ts:255— sync has cyclomatic complexity 14 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 getRoute (cyclomatic 14, cognitive 23) packages/@ember/routing/router.ts:387— getRoute has cyclomatic complexity 14 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 constructor (cyclomatic 14, cognitive 22) lib/overrides.cjs:105— constructor has cyclomatic complexity 14 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 preparePath (cyclomatic 14, cognitive 18) packages/@handlebars/parser/lib/helpers.js:44— preparePath has cyclomatic complexity 14 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/@handlebars/parser/lib/parser.js · ×1
packages/@handlebars/parser/lib/parser.js: 1979 lines of code packages/@handlebars/parser/lib/parser.js:1— packages/@handlebars/parser/lib/parser.js has 1979 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/@ember/routing/route.ts · ×1
packages/@ember/routing/route.ts: 1736 lines of code packages/@ember/routing/route.ts:1— packages/@ember/routing/route.ts has 1736 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/@ember/routing/router.ts · ×1
packages/@ember/routing/router.ts: 1566 lines of code packages/@ember/routing/router.ts:1— packages/@ember/routing/router.ts has 1566 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/@ember/helper/index.ts · ×1
packages/@ember/helper/index.ts: 1485 lines of code packages/@ember/helper/index.ts:1— packages/@ember/helper/index.ts has 1485 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/@ember/-internals/glimmer/lib/component.ts · ×1
packages/@ember/-internals/glimmer/lib/component.ts: 1339 lines of code packages/@ember/-internals/glimmer/lib/component.ts:1— packages/@ember/-internals/glimmer/lib/component.ts has 1339 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/@ember/array/index.ts · ×1
packages/@ember/array/index.ts: 1322 lines of code packages/@ember/array/index.ts:1— packages/@ember/array/index.ts has 1322 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/@ember/object/lib/computed/reduce_computed_macros.ts · ×1
packages/@ember/object/lib/computed/reduce_computed_macros.ts: 1136 lines of code packages/@ember/object/lib/computed/reduce_computed_macros.ts:1— packages/@ember/object/lib/computed/reduce_computed_macros.ts has 1136 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1109 lines of code REDACTED:1— REDACTED has 1109 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/router_js/lib/router.ts · ×1
packages/router_js/lib/router.ts: 1041 lines of code packages/router_js/lib/router.ts:1— packages/router_js/lib/router.ts has 1041 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/@glimmer/syntax/lib/v2/normalize.ts · ×1
packages/@glimmer/syntax/lib/v2/normalize.ts: 935 lines of code packages/@glimmer/syntax/lib/v2/normalize.ts:1— packages/@glimmer/syntax/lib/v2/normalize.ts has 935 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/@ember/object/core.ts · ×1
packages/@ember/object/core.ts: 919 lines of code packages/@ember/object/core.ts:1— packages/@ember/object/core.ts has 919 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/@ember/application/index.ts · ×1
packages/@ember/application/index.ts: 901 lines of code packages/@ember/application/index.ts:1— packages/@ember/application/index.ts has 901 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/@ember/runloop/index.ts · ×1
packages/@ember/runloop/index.ts: 804 lines of code packages/@ember/runloop/index.ts:1— packages/@ember/runloop/index.ts has 804 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/@glimmer/compiler/lib/builder/builder-interface.ts · ×1
packages/@glimmer/compiler/lib/builder/builder-interface.ts: 803 lines of code packages/@glimmer/compiler/lib/builder/builder-interface.ts:1— packages/@glimmer/compiler/lib/builder/builder-interface.ts has 803 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/@glimmer/runtime/lib/compiled/opcodes/component.ts · ×1
packages/@glimmer/runtime/lib/compiled/opcodes/component.ts: 803 lines of code packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:1— packages/@glimmer/runtime/lib/compiled/opcodes/component.ts has 803 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/@glimmer/runtime/lib/vm/append.ts · ×1
packages/@glimmer/runtime/lib/vm/append.ts: 794 lines of code packages/@glimmer/runtime/lib/vm/append.ts:1— packages/@glimmer/runtime/lib/vm/append.ts has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 778 lines of code REDACTED:1— REDACTED has 778 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/@ember/-internals/metal/lib/computed.ts · ×1
packages/@ember/-internals/metal/lib/computed.ts: 767 lines of code packages/@ember/-internals/metal/lib/computed.ts:1— packages/@ember/-internals/metal/lib/computed.ts has 767 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/@ember/routing/router-service.ts · ×1
packages/@ember/routing/router-service.ts: 729 lines of code packages/@ember/routing/router-service.ts:1— packages/@ember/routing/router-service.ts has 729 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/@ember/object/lib/computed/computed_macros.ts · ×1
packages/@ember/object/lib/computed/computed_macros.ts: 724 lines of code packages/@ember/object/lib/computed/computed_macros.ts:1— packages/@ember/object/lib/computed/computed_macros.ts 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· packages/@ember/-internals/glimmer/lib/base-renderer.ts · ×1
packages/@ember/-internals/glimmer/lib/base-renderer.ts: 718 lines of code packages/@ember/-internals/glimmer/lib/base-renderer.ts:1— packages/@ember/-internals/glimmer/lib/base-renderer.ts has 718 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/@glimmer-workspace/integration-tests/lib/render-test.ts · ×1
packages/@glimmer-workspace/integration-tests/lib/render-test.ts: 693 lines of code packages/@glimmer-workspace/integration-tests/lib/render-test.ts:1— packages/@glimmer-workspace/integration-tests/lib/render-test.ts has 693 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/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts · ×1
packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts: 676 lines of code packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts:1— packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts has 676 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/@glimmer/compiler/lib/builder/builder.ts · ×1
packages/@glimmer/compiler/lib/builder/builder.ts: 668 lines of code packages/@glimmer/compiler/lib/builder/builder.ts:1— packages/@glimmer/compiler/lib/builder/builder.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts · ×1
packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts: 658 lines of code packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts:1— packages/@glimmer/syntax/lib/parser/handlebars-node-visitors.ts has 658 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/@glimmer/debug/lib/opcode-metadata.ts · ×1
packages/@glimmer/debug/lib/opcode-metadata.ts: 629 lines of code packages/@glimmer/debug/lib/opcode-metadata.ts:1— packages/@glimmer/debug/lib/opcode-metadata.ts has 629 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/@ember/-internals/meta/lib/meta.ts · ×1
packages/@ember/-internals/meta/lib/meta.ts: 625 lines of code packages/@ember/-internals/meta/lib/meta.ts:1— packages/@ember/-internals/meta/lib/meta.ts has 625 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/@glimmer-workspace/integration-tests/lib/suites/each.ts · ×1
packages/@glimmer-workspace/integration-tests/lib/suites/each.ts: 621 lines of code packages/@glimmer-workspace/integration-tests/lib/suites/each.ts:1— packages/@glimmer-workspace/integration-tests/lib/suites/each.ts 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· packages/@ember/debug/data-adapter.ts · ×1
packages/@ember/debug/data-adapter.ts: 607 lines of code packages/@ember/debug/data-adapter.ts:1— packages/@ember/debug/data-adapter.ts has 607 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· eslint-rules/no-barrel-imports.cjs · ×1
eslint-rules/no-barrel-imports.cjs: 603 lines of code eslint-rules/no-barrel-imports.cjs:1— eslint-rules/no-barrel-imports.cjs has 603 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/@ember/-internals/owner/index.ts · ×1
packages/@ember/-internals/owner/index.ts: 603 lines of code packages/@ember/-internals/owner/index.ts:1— packages/@ember/-internals/owner/index.ts has 603 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/@ember/object/mixin-internal.ts · ×1
packages/@ember/object/mixin-internal.ts: 593 lines of code packages/@ember/object/mixin-internal.ts:1— packages/@ember/object/mixin-internal.ts has 593 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/@ember/-internals/glimmer/lib/components/link-to.ts · ×1
packages/@ember/-internals/glimmer/lib/components/link-to.ts: 563 lines of code packages/@ember/-internals/glimmer/lib/components/link-to.ts:1— packages/@ember/-internals/glimmer/lib/components/link-to.ts has 563 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/@ember/array/index-internal.ts · ×1
packages/@ember/array/index-internal.ts: 543 lines of code packages/@ember/array/index-internal.ts:1— packages/@ember/array/index-internal.ts has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/router_js/lib/route-info.ts · ×1
packages/router_js/lib/route-info.ts: 520 lines of code packages/router_js/lib/route-info.ts:1— packages/router_js/lib/route-info.ts has 520 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/@ember/-internals/container/lib/container.ts · ×1
packages/@ember/-internals/container/lib/container.ts: 490 lines of code packages/@ember/-internals/container/lib/container.ts:1— packages/@ember/-internals/container/lib/container.ts has 490 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/@glimmer/syntax/lib/source/loc/span.ts · ×1
packages/@glimmer/syntax/lib/source/loc/span.ts: 490 lines of code packages/@glimmer/syntax/lib/source/loc/span.ts:1— packages/@glimmer/syntax/lib/source/loc/span.ts has 490 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/@glimmer/runtime/lib/vm/element-builder.ts · ×1
packages/@glimmer/runtime/lib/vm/element-builder.ts: 481 lines of code packages/@glimmer/runtime/lib/vm/element-builder.ts:1— packages/@glimmer/runtime/lib/vm/element-builder.ts has 481 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/@ember/-internals/glimmer/lib/component-managers/curly.ts · ×1
packages/@ember/-internals/glimmer/lib/component-managers/curly.ts: 469 lines of code packages/@ember/-internals/glimmer/lib/component-managers/curly.ts:1— packages/@ember/-internals/glimmer/lib/component-managers/curly.ts has 469 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/@glimmer/runtime/lib/vm/rehydrate-builder.ts · ×1
packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts: 469 lines of code packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:1— packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts has 469 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job package.json:63— The root package declares the lint script `lint:eslint` (`eslint --report-unused-disable-directives --cache .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint:eslint` in `.` (or the workspace's task runner).
Dead file (~215 LoC) blueprints/route/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~123 LoC) internal-docs/guides/reactivity/pseudocode/composition.ts— no import path from any entry point (762 application, 66 tooling, 802 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 (~106 LoC) blueprints/component-class/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~105 LoC) internal-docs/guides/reactivity/pseudocode/primitives.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (internal-docs/guides/reactivity/pseudocode/composition.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 (~81 LoC) internal-docs/guides/reactivity/pseudocode/tags.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (internal-docs/guides/reactivity/pseudocode/composition.ts, internal-docs/guides/reactivity/pseudocode/primitives.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~73 LoC) blueprints/component-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) testem.browserstack.cjs— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~66 LoC) packages/ember-template-compiler/lib/plugins/index.ts— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~65 LoC) config/s3ProjectConfig.cjs— no import path from any entry point (762 application, 66 tooling, 802 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 (~64 LoC) blueprints/route-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~51 LoC) blueprints/component-class-addon/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~46 LoC) blueprints/-addon-import.js— no import path from any entry point (762 application, 66 tooling, 802 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (blueprints/helper-addon/index.js, blueprints/initializer-addon/index.js, blueprints/instance-initializer-addon/index.js) — 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 (~28 LoC) packages/ember-template-compiler/lib/system/calculate-location-display.ts— no import path from any entry point (762 application, 66 tooling, 802 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 (~16 LoC) testem.ci-browsers.cjs— no import path from any entry point (762 application, 66 tooling, 802 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 (~6 LoC) blueprints/mixin/index.js— no import path from any entry point (762 application, 66 tooling, 802 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 (~0 LoC) generators/license.js— no import path from any entry point (762 application, 66 tooling, 802 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 '@arethetypeswrong/cli' package.json:105— Declared in the root 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 'ember-cli-browserstack' package.json:135— Declared in the root 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 'tracerbench' package.json:169— Declared in the root 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 'dom-types' packages/@glimmer-workspace/integration-tests/package.json:58— Declared in packages/@glimmer-workspace/integration-tests/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 '@glimmer-workspace/test-utils' packages/@glimmer-workspace/integration-tests/test/package.json:8— Declared in packages/@glimmer-workspace/integration-tests/test/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 '@glimmer-workspace/integration-tests' packages/@glimmer/syntax/test/package.json:7— Declared in packages/@glimmer/syntax/test/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 '@ember/version' packages/ember/package.json:33— Declared in packages/ember/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 '@ember/optional-features' smoke-tests/app-template/package.json:33— Declared in smoke-tests/app-template/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 'broccoli-asset-rev' smoke-tests/app-template/package.json:39— Declared in smoke-tests/app-template/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 'ember-auto-import' smoke-tests/app-template/package.json:41— Declared in smoke-tests/app-template/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 'ember-cli-app-version' smoke-tests/app-template/package.json:43— Declared in smoke-tests/app-template/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 'ember-cli-clean-css' smoke-tests/app-template/package.json:45— Declared in smoke-tests/app-template/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 'ember-cli-inject-live-reload' smoke-tests/app-template/package.json:49— Declared in smoke-tests/app-template/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 'ember-cli-sri' smoke-tests/app-template/package.json:50— Declared in smoke-tests/app-template/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 'ember-cli-terser' smoke-tests/app-template/package.json:51— Declared in smoke-tests/app-template/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 'ember-modifier' smoke-tests/app-template/package.json:53— Declared in smoke-tests/app-template/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 'stylelint-config-standard' smoke-tests/app-template/package.json:72— Declared in smoke-tests/app-template/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 'tracked-built-ins' smoke-tests/app-template/package.json:74— Declared in smoke-tests/app-template/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 '@swc/types' smoke-tests/scenarios/package.json:11— Declared in smoke-tests/scenarios/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 'ember-cli-htmlbars-6' smoke-tests/scenarios/package.json:15— Declared in smoke-tests/scenarios/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.
Weak hash algorithm packages/@glimmer/compiler/lib/compiler.ts:45— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Swallowed exception (caught, then discarded) packages/@ember/routing/lib/routing-service.ts:107— `catch (_e)` 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.
Orphaned file packages/@glimmer/runtime/lib/vm/rehydrate-builder.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/@glimmer/syntax/lib/source/loc/span.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/@glimmer/runtime/lib/vm/arguments.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/@ember/-internals/container/lib/registry.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/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.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/@glimmer/syntax/lib/v1/public-builders.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/@glimmer/syntax/lib/generation/printer.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/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.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/@glimmer/debug/lib/stack-check.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/@glimmer/opcode-compiler/lib/syntax/statements.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/@glimmer/compiler/lib/passes/1-normalization/keywords/block.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/@glimmer/compiler/lib/passes/1-normalization/visitors/strict-mode.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/@ember/controller/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 lib/overrides.cjs: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/@glimmer/syntax/lib/v2/builders.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/@glimmer/runtime/lib/compiled/opcodes/expressions.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/@ember/-internals/views/lib/system/event_dispatcher.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/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.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/@glimmer/syntax/lib/source/loc/offset.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/@ember/debug/lib/deprecate.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/@glimmer/program/lib/constants.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/@glimmer-workspace/integration-tests/lib/suites/has-block-params.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/@glimmer/syntax/lib/v1/parser-builders.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/@glimmer/compiler/lib/passes/2-encoding/content.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/@glimmer/syntax/lib/v2/serialize/serialize.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.
No direct assertions: mustache packages/@handlebars/parser/spec/ast.js:7— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: block statements packages/@handlebars/parser/spec/ast.js:14— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: mustache packages/@handlebars/parser/spec/ast.js:23— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: block statements packages/@handlebars/parser/spec/ast.js:30— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: {{this}} packages/@handlebars/parser/spec/ast.js:41— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: {{this.bar}} packages/@handlebars/parser/spec/ast.js:49— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: {{this.#bar}} packages/@handlebars/parser/spec/ast.js:58— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: {{foo.bar}} packages/@handlebars/parser/spec/ast.js:67— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: {{foo.#bar}} packages/@handlebars/parser/spec/ast.js:78— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: does not mark mustaches as standalone packages/@handlebars/parser/spec/ast.js:93— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: block mustaches packages/@handlebars/parser/spec/ast.js:100— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: initial block mustaches packages/@handlebars/parser/spec/ast.js:113— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: mustaches with children packages/@handlebars/parser/spec/ast.js:119— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: nested block mustaches packages/@handlebars/parser/spec/ast.js:127— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: column 0 block mustaches packages/@handlebars/parser/spec/ast.js:139— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks block mustaches as standalone packages/@handlebars/parser/spec/ast.js:154— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks initial block mustaches as standalone packages/@handlebars/parser/spec/ast.js:165— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks mustaches with children as standalone packages/@handlebars/parser/spec/ast.js:171— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks nested block mustaches as standalone packages/@handlebars/parser/spec/ast.js:179— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: does not mark nested block mustaches as standalone packages/@handlebars/parser/spec/ast.js:193— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: does not mark nested initial block mustaches as standalone packages/@handlebars/parser/spec/ast.js:207— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks column 0 block mustaches as standalone packages/@handlebars/parser/spec/ast.js:218— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: simple partial packages/@handlebars/parser/spec/ast.js:231— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: indented partial packages/@handlebars/parser/spec/ast.js:235— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: marks partial as standalone packages/@handlebars/parser/spec/ast.js:243— No conventional assertion call was detected, and 104 of 104 tests in `packages/@handlebars/parser` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:3595— @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:3608— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/command REDACTED:4826— @oclif/command 1.8.36 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/config REDACTED:4831— @oclif/config 1.18.16 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/config REDACTED:4836— @oclif/config 1.18.17 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/errors REDACTED:4845— @oclif/errors 1.3.6 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/help REDACTED:4850— @oclif/help 1.0.15 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/parser REDACTED:4858— @oclif/parser 3.8.17 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/glob REDACTED:5944— @types/glob 9.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. glob provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:6129— @xmldom/xmldom 0.9.10 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:6644— boom 0.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: charm REDACTED:6968— charm 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: cryptiles REDACTED:7479— cryptiles 0.2.2 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: exists-sync REDACTED:8351— exists-sync 0.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Please replace with usage of fs.existsSync". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8788— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8797— glob 5.0.15 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8801— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8805— glob 8.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8810— glob 9.3.5 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hawk REDACTED:8953— hawk 1.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:8978— hoek 0.9.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:9162— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash-node REDACTED:9834— lodash-node 3.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is discontinued. Use lodash@^4.0.0.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.template REDACTED:9871— lodash.template 4.18.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use https://socket.dev/npm/package/eta instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-uuid REDACTED:10302— node-uuid 1.4.8 is resolved in REDACTED and is marked deprecated by its publisher: "Use uuid module instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate packages/@ember/-internals/utils/lib/get-debug-name.ts:27— `'toString' in obj && obj.toString !== Object.prototype.toString && obj.toString !== Function.prototype.toString` appears character-identically in 2 files — packages/@ember/-internals/utils/lib/get-debug-name.ts, packages/@glimmer/debug-util/lib/debug-to-string.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/@ember/-internals/metal/lib/property_get.ts:126— `Array.isArray(value) || isEmberArray(value)` appears character-identically in 2 files — packages/@ember/-internals/metal/lib/property_get.ts, packages/@ember/-internals/metal/lib/tracked.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/@glimmer/manager/lib/public/component.ts:127— `DEBUG && !FROM_CAPABILITIES!.has(delegate.capabilities)` appears character-identically in 3 files — packages/@glimmer/manager/lib/public/component.ts, packages/@glimmer/manager/lib/public/helper.ts, packages/@glimmer/manager/lib/public/modifier.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 blueprints/component/index.js:175— `file.endsWith('.gjs') || file.endsWith('.gts')` appears character-identically in 2 files — blueprints/component/index.js, blueprints/route/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/@ember/-internals/utils/lib/get-debug-name.ts:58— `getFunctionName(value) || `(unknown function)`` appears character-identically in 2 files — packages/@ember/-internals/utils/lib/get-debug-name.ts, packages/@glimmer/debug-util/lib/debug-to-string.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/@ember/-internals/utils/lib/get-debug-name.ts:60— `getObjectName(value) || `(unknown object)`` appears character-identically in 2 files — packages/@ember/-internals/utils/lib/get-debug-name.ts, packages/@glimmer/debug-util/lib/debug-to-string.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/@ember/template-compiler/lib/dasherize-component-name.ts:16— `index === 0 || !ALPHA.test(key[index - 1]!)` appears character-identically in 2 files — packages/@ember/template-compiler/lib/dasherize-component-name.ts, packages/ember-template-compiler/lib/system/dasherize-component-name.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/@ember/template-compiler/lib/system/calculate-location-display.ts:14— `line !== undefined && column !== undefined` appears character-identically in 2 files — packages/@ember/template-compiler/lib/system/calculate-location-display.ts, packages/ember-template-compiler/lib/system/calculate-location-display.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/@ember/routing/lib/utils.ts:110— `manager !== undefined && bucket !== undefined && hasClassicInterop(manager)` appears character-identically in 2 files — packages/@ember/routing/lib/utils.ts, packages/router_js/lib/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/router_js/lib/route-info.ts:176— `manager !== undefined && hasClassicInterop(manager) && bucket !== undefined` appears character-identically in 2 files — packages/router_js/lib/route-info.ts, packages/router_js/lib/transition-state.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/@ember/routing/router.ts:1301— `manager === undefined || bucket === undefined || !hasClassicInterop(manager)` appears character-identically in 2 files — packages/@ember/routing/router.ts, packages/router_js/lib/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 REDACTED:28— `string.indexOf('::') === -1 && string.indexOf(':') > -1` appears character-identically in 2 files — REDACTED, packages/ember-template-compiler/lib/system/compile-options.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/@ember/-internals/glimmer/lib/components/input.ts:254— `supportedArguments.indexOf(name) !== -1 || super.isSupportedArgument(name)` appears character-identically in 3 files — packages/@ember/-internals/glimmer/lib/components/input.ts, packages/@ember/-internals/glimmer/lib/components/link-to.ts, packages/@ember/-internals/glimmer/lib/components/textarea.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/@glimmer/node/lib/serialize-builder.ts:39— `tagName !== 'TITLE' && tagName !== 'SCRIPT' && tagName !== 'STYLE'` appears character-identically in 2 files — packages/@glimmer/node/lib/serialize-builder.ts, packages/@glimmer/runtime/lib/vm/rehydrate-builder.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 blueprints/component-class/index.js:40— `this._super && this._super.init.apply(this, arguments)` appears character-identically in 9 files — blueprints/component-class/index.js, blueprints/component/index.js, blueprints/controller/index.js, blueprints/helper/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/@ember/-internals/runtime/lib/mixins/action_handler-internal.ts:33— `this.actions && this.actions[actionName]` appears character-identically in 2 files — packages/@ember/-internals/runtime/lib/mixins/action_handler-internal.ts, packages/@ember/-internals/views/lib/mixins/action_support-internal.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 blueprints/component/index.js:164— `this.options.isTypeScriptProject || this.options.typescript` appears character-identically in 2 files — blueprints/component/index.js, blueprints/route/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/@ember/-internals/metal/lib/property_get.ts:94— `typeof keyName !== 'string' || keyName.lastIndexOf('this.', 0) !== 0` appears character-identically in 2 files — packages/@ember/-internals/metal/lib/property_get.ts, packages/@ember/-internals/metal/lib/property_set.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/@ember/-internals/metal/lib/property_get.ts:90— `typeof keyName === 'string' || (typeof keyName === 'number' && !isNaN(keyName))` appears character-identically in 2 files — packages/@ember/-internals/metal/lib/property_get.ts, packages/@ember/-internals/metal/lib/property_set.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/@ember/-internals/meta/lib/meta.ts:622— `typeof obj === 'object' || typeof obj === 'function'` appears character-identically in 3 files — packages/@ember/-internals/meta/lib/meta.ts, packages/@ember/-internals/metal/lib/decorator.ts, packages/@ember/-internals/metal/lib/property_get.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/@ember/-internals/metal/lib/tracked.ts:245— `typeof value !== 'object' || value === null` appears character-identically in 2 files — packages/@ember/-internals/metal/lib/tracked.ts, packages/@ember/utils/lib/compare.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/@ember/-internals/utils/lib/get-debug-name.ts:59— `typeof value === 'object' && value !== null` appears character-identically in 3 files — packages/@ember/-internals/utils/lib/get-debug-name.ts, packages/@glimmer/debug-util/lib/debug-to-string.ts, packages/@glimmer/debug/lib/render/fragment.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/@ember/-internals/glimmer/lib/utils/iterator.ts:276— `value !== null && (typeof value === 'object' || typeof value === 'function')` appears character-identically in 3 files — packages/@ember/-internals/glimmer/lib/utils/iterator.ts, packages/@ember/-internals/utils/lib/spec.ts, packages/@glimmer/runtime/lib/opcodes.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/@ember/routing/lib/dsl.ts:42— `value !== null && typeof value === 'object'` appears character-identically in 2 files — packages/@ember/routing/lib/dsl.ts, packages/@glimmer/runtime/lib/dom/normalize.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
redundant comment packages/@ember/-internals/glimmer/tests/integration/components/link-to/routing-angle-test.js:1989— "Set the destinationRoute back to null." repeats the code it sits on: 4 of its 5 words (set, destination, route, null) are already in `runTask(() => controller.set('destinationRoute', null));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/-internals/glimmer/tests/integration/components/link-to/routing-curly-test.js:1928— "Set the destinationRoute back to null." repeats the code it sits on: 4 of its 5 words (set, destination, route, null) are already in `runTask(() => controller.set('destinationRoute', null));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/-internals/metal/lib/computed.ts:896— "@computed with keys and config" repeats the code it sits on: 3 of its 3 words (computed, keys, config) are already in `export function computed(...args: ComputedDecoratorKeysAndConfig): ComputedDecorator;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/-internals/metal/tests/computed_test.js:688— ".......................................................... improved-cp-syntax" repeats the code it sits on: 3 of its 3 words (improved, cp, syntax) are already in `moduleFor(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/-internals/metal/tests/observer_test.js:680— ".......................................................... SETTING IDENTICAL VALUES" repeats the code it sits on: 3 of its 3 words (setting, identical, values) are already in `moduleFor(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/-internals/runtime/tests/mixins/array_test.js:218— ".......................................................... NOTIFY ARRAY OBSERVER" repeats the code it sits on: 3 of its 3 words (notify, array, observer) are already in `moduleFor(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/engine/index.ts:524— "Register the routing service..." repeats the code it sits on: 3 of its 3 words (register, routing, service) are already in `registry.register('service:-routing', RoutingService);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@ember/routing/router.ts:576— "If the error was a transition error or the transition aborted log the abort." repeats the code it sits on: 4 of its 5 words (transition, aborted, log, abort) are already in `return logAbort(transition);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/@glimmer/syntax/test/parser-escape-test.ts:75— "Inside quoted attribute values" repeats the code it sits on: 4 of its 4 words (inside, quoted, attribute, values) are already in `test('\\{{ inside a quoted attribute value emits {{ as literal text', (assert) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/ember/tests/routing/query_params_test.js:185— "`/parent/child?array=["one",2]&string=hello`" repeats the code it sits on: 5 of its 5 words (parent, child, array, string, hello) are already in `return this.visit('/parent/child?array=%5B%22one%22%2C2%5D&string=hello').then(() =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
IC1 · Incompleteness & stubs· Empty method body · ×10
Empty method body packages/@ember/-internals/glimmer/lib/helpers/element.ts:38— `didCreateElement` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/-internals/glimmer/lib/helpers/element.ts:49— `didRenderLayout` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/-internals/glimmer/lib/helpers/element.ts:50— `didUpdateLayout` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/-internals/glimmer/lib/helpers/element.ts:51— `didCreate` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/-internals/glimmer/lib/helpers/element.ts:52— `didUpdate` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/debug/lib/deprecate.ts:77— `registerHandler` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/debug/lib/deprecate.ts:81— `deprecate` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/debug/lib/handlers.ts:27— `invoke` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/debug/lib/warn.ts:19— `registerHandler` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/@ember/debug/lib/warn.ts:20— `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Fat interface: EmberArray (35 required operations) packages/@ember/array/index.ts:55— `EmberArray` declares 35 required operations: `objectAt`, `objectsAt`, `slice`, `indexOf`, `lastIndexOf`, `forEach`, `getEach`, `setEach`, `map`, `mapBy`, `mapBy`, `filter`, `reject`, `filterBy`, `rejectBy`, `find`, `find`, `findBy`, `findBy`, `every`, `isEvery`, `isEvery`, `any`, `isAny`, `isAny`, `reduce`, `invoke`, `toArray`, `compact`, `includes`, `sortBy`, `uniq`, `uniqBy`, `uniqBy`, `without`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 35 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: MutableArray (16 required operations) packages/@ember/array/index.ts:1071— `MutableArray` declares 16 required operations: `replace`, `clear`, `insertAt`, `removeAt`, `pushObject`, `pushObjects`, `popObject`, `shiftObject`, `unshiftObject`, `unshiftObjects`, `reverseObjects`, `setObjects`, `removeObject`, `removeObjects`, `addObject`, `addObjects`. 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: InternalObservable (19 required operations) packages/@ember/object/observable-internal.ts:32— `InternalObservable` declares 19 required operations under just 11 distinct name(s): `get`, `get`, `getProperties`, `getProperties`, `getProperties`, `getProperties`, `set`, `set`, `setProperties`, `setProperties`, `notifyPropertyChange`, `addObserver`, `addObserver`, `removeObserver`, `removeObserver`, `incrementProperty`, `decrementProperty`, `toggleProperty`, `cacheFor`. 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. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 11 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: Observable (19 required operations) packages/@ember/object/observable.ts:87— `Observable` declares 19 required operations under just 11 distinct name(s): `get`, `get`, `getProperties`, `getProperties`, `getProperties`, `getProperties`, `set`, `set`, `setProperties`, `setProperties`, `notifyPropertyChange`, `addObserver`, `addObserver`, `removeObserver`, `removeObserver`, `incrementProperty`, `decrementProperty`, `toggleProperty`, `cacheFor`. 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. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 11 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: RouteManagerWithClassicInterop (22 required operations) packages/router_js/lib/route-manager.ts:337— `RouteManagerWithClassicInterop` declares 22 required operations: `isInaccessibleByURL`, `willEnter`, `enter`, `didEnter`, `willExit`, `exit`, `didExit`, `qp`, `stashNames`, `serializeQueryParam`, `deserializeQueryParam`, `serializeContext`, `queryParamsDidChange`, `finalizeQueryParamChange`, `getContext`, `redirect`, `invokeAction`, `triggerLoadingEvent`, `triggerErrorEvent`, `handleLoadingEvent`, `handleErrorEvent`, `getRouteInfoMetadata`. 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, 15 significant file(s) lose their only recent owner: packages/@ember/object/lib/computed/computed_macros.ts, eslint-rules/no-barrel-imports.cjs, packages/@glimmer/runtime/lib/vm/append.ts, packages/@ember/debug/data-adapter.ts, packages/@ember/array/index-internal.ts, packages/@glimmer/validator/lib/tracking.ts, packages/@glimmer/runtime/lib/vm/update.ts, packages/@glimmer/component/src/-private/component.ts (+7 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 12 significant file(s) lose their only recent owner: REDACTED, packages/@ember/-internals/metal/lib/decorator.ts, packages/@glimmer-workspace/integration-tests/lib/suites/has-block.ts, packages/@glimmer-workspace/integration-tests/lib/test-helpers/module.ts, packages/@glimmer-workspace/integration-tests/lib/modes/rehydration/delegate.ts, packages/@ember/-internals/metal/lib/decorator-util.ts, packages/@glimmer-workspace/integration-tests/lib/modes/jit/delegate.ts, packages/@ember/template-compiler/lib/plugins/transform-resolutions.ts (+4 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 4 significant file(s) lose their only recent owner: packages/@ember/-internals/glimmer/lib/components/input.ts, packages/@ember/-internals/glimmer/lib/syntax/mount.ts, packages/@ember/-internals/glimmer/lib/helpers/readonly.ts, packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts. Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion packages/@ember/-internals/package.json:1— `packages/@ember/-internals` (17600 LoC, 193 module-visible types across 23 directories) overshoots its size bounds. 3 of 57 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 9.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/@glimmer/syntax/package.json:1— `packages/@glimmer/syntax` (8300 LoC, 256 module-visible types across 10 directories) overshoots its size bounds. 3 of 57 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 9.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/@glimmer/runtime/package.json:1— `packages/@glimmer/runtime` (7550 LoC, 127 module-visible types across 11 directories) overshoots its size bounds. 3 of 57 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 9.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/@handlebars/parser packages/@handlebars/parser/spec/ast.js:7— No conventional assertion call was detected in 104 of 104 tests in `packages/@handlebars/parser` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
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 (34 single-owned of 324 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; 324 of the 749 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)), anonymized user #5 (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/@glimmer/syntax/lib/source/source.ts, packages/@glimmer/runtime/lib/compiled/opcodes/debugger.ts.
No ADRs found package.json:68— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `package.json` makes this repository a deployable product (line 68).
D21 · Naming Consistency· `isHBSLiteral` spells `HBS` where 12 names in the project spell it `Hbs` · ×1
`isHBSLiteral` spells `HBS` where 12 names in the project spell it `Hbs` packages/@glimmer/syntax/lib/utils.ts:25— 12 of 13 names in project ember-source spell the token `Hbs` (12 of 13; unit: names in project ember-source containing `Hbs`). Peers: SourceOffset.forHbsPos (packages/@glimmer/syntax/lib/source/loc/offset.ts:47); CharPosition.toHbsPos (packages/@glimmer/syntax/lib/source/loc/offset.ts:179); HbsPosition.toHbsPos (packages/@glimmer/syntax/lib/source/loc/offset.ts:248); SpanData.toHbsSpan (packages/@glimmer/syntax/lib/source/loc/span.ts:55); SourceSpan.forHbsLoc (packages/@glimmer/syntax/lib/source/loc/span.ts:126). Rename to `isHbsLiteral`. [rule N6]
Pass-through layer packages/@glimmer/runtime/lib/vm/element-builder.ts:60— Fragment: all 3 public methods forward their arguments unchanged to bounds and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call bounds 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) — 151 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts, packages/@glimmer/syntax/lib/source/loc/span.ts, packages/@glimmer/runtime/lib/vm/arguments.ts, packages/@ember/-internals/container/lib/registry.ts, packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/components.ts, packages/@glimmer/syntax/lib/v1/public-builders.ts, packages/@glimmer/syntax/lib/generation/printer.ts, packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts (and 143 more) (157 orphaned of 328 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; 328 of the 749 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.
Blanket warning suppression packages/@handlebars/parser/lib/parser.js: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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST .github/workflows/ci.yml:16— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 14 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
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 — 5/6 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 — ~3.6 `!` null assertions per 1k TypeScript source lines — 335 assertion(s) across the 93910 source line(s) of the 590 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/router_js/lib/router.ts (50), packages/@ember/-internals/meta/lib/meta.ts (22), packages/router_js/lib/transition.ts (16). 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.
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/debug-render-tree-test.ts:140— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/debug-render-tree-test.ts:167— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/initial-render-test.ts:915— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/initial-render-test.ts:934— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:103— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:125— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:151— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:164— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:190— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:203— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:508— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:518— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:528— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:1137— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:1238— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/strict-mode-test.ts:1306— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/updating-test.ts:869— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/and-test.ts:129— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/each-test.ts:7— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/eq-test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/gt-test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/gte-test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/lt-test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/lte-test.ts:92— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/@glimmer-workspace/integration-tests/test/keywords/neq-test.ts:80— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
doc comments repeat the names packages/@ember/-internals/glimmer/lib/base-renderer.ts:418— 1 of 106 documented parameters and 2 of 250 summaries in `@ember/-internals` only repeat the member or parameter name (e.g. "---------------------------------------------------------------------------- BaseRenderer ---------------------------------------------------------------------- …" for `BaseRenderer`). 9 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/application/instance.ts:51— 0 of 5 documented parameters and 1 of 36 summaries in `@ember/application` only repeat the member or parameter name (e.g. "The `Application` for which this is an instance." for `application`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/array/index.ts:895— 1 of 68 documented parameters and 0 of 77 summaries in `@ember/array` only repeat the member or parameter name (e.g. "the name of the method" for `methodName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/debug/data-adapter.ts:431— 5 of 20 documented parameters and 1 of 27 summaries in `@ember/debug` only repeat the member or parameter name (e.g. "The model name." for `modelName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/engine/lib/engine-parent.ts:12— 2 of 10 documented parameters and 0 of 17 summaries in `@ember/engine` only repeat the member or parameter name (e.g. "An engine instance." for `engine`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/object/mixin-internal.ts:439— 0 of 47 documented parameters and 0 of 84 summaries in `@ember/object` only repeat the member or parameter name (e.g. "" for `obj`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@ember/routing/history-location.ts:183— 3 of 72 documented parameters and 4 of 113 summaries in `@ember/routing` only repeat the member or parameter name (e.g. "Pushes a new state." for `pushState`). 5 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:259— 0 of 1 documented parameters and 0 of 22 summaries in `@ember/template-compiler` only repeat the member or parameter name (e.g. "" for `options`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@glimmer/component/src/-private/component.ts:234— 0 of 2 documented parameters and 0 of 8 summaries in `@glimmer/component` only repeat the member or parameter name (e.g. "" for `owner`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:62— 1 of 23 documented parameters and 0 of 20 summaries in `@glimmer/opcode-compiler` only repeat the member or parameter name (e.g. "A handle" for `handle`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/@glimmer/validator/lib/tracked-value.ts:19— 0 of 3 documented parameters and 1 of 29 summaries in `@glimmer/validator` only repeat the member or parameter name (e.g. "A reactive value that can only be read." for `ReadOnlyReactive`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names broccoli/build-info.cjs:114— 0 of 0 documented parameters and 1 of 15 summaries in `ember-source` only repeat the member or parameter name (e.g. "Read package version." for `readPackageVersion`). Delete the restating tags, or add what the name does not say.
Outdated (npm): @babel/core — @babel/core is pinned at 7.29.7; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @embroider/addon-shim — @embroider/addon-shim is pinned at 1.10.2; registry.npmjs.org publishes 1.11.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): chalk — chalk is pinned at 4.1.2; registry.npmjs.org publishes 6.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): enhanced-resolve — enhanced-resolve is pinned at 5.22.1; registry.npmjs.org publishes 5.27.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): expect-type — expect-type is pinned at 1.3.0; registry.npmjs.org publishes 1.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): inflection — inflection is pinned at 2.0.1; registry.npmjs.org publishes 3.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): qunit — qunit is pinned at 2.26.0; registry.npmjs.org publishes 3.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): semver — semver is pinned at 7.8.1; registry.npmjs.org publishes 7.8.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): type-fest — type-fest is pinned at 4.41.0; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): vite — vite is pinned at 8.3.4; registry.npmjs.org publishes 8.3.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): vitest — vitest is pinned at 4.1.8; registry.npmjs.org publishes 5.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 52 file(s) — `internal-docs/guides/reactivity/pseudocode/composition.ts`, `packages/@ember/-internals/glimmer/lib/component-managers/curly-brand.ts`, `packages/@ember/-internals/glimmer/lib/component.ts`, `packages/@ember/-internals/glimmer/lib/components/internal.ts`, `packages/@ember/-internals/glimmer/lib/helper-brand.ts`, … (+47 more) — 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 01a1e7df-eb62-7e9c-ab77-2359770eb5b0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 89 · Warnings: 573 · Recommendations: 363 · Info: 56 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 04:59 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.