Public report of webspatial/webspatial-sdk, published 16 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, 16 November 2026, 15:32 UTC · Survey ID cd_9fd6bfce2bd4466580c0cb6806c75896
webspatial/webspatial-sdk
Measured 16 November 2026, 15:28 UTC, at code version 32907b3
First survey, so nothing to compare with yet
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 59,783 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 49.9
Findings by how serious they are
58 critical408 serious217 minor
9 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
16 November 2026, 15:28 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 ▸
79of 79 dimensions measured by tools.
621of 683 findings point to an exact file and line, so you can open each one in the code. The other 62 concern the repository as a whole, such as missing documentation.
79dimensions across 7 lenses, read from 59,783 lines of product code in 11 projects.
webspatial/webspatial-sdk is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 57.7 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 49.9, is the weakest lens and counts most in the score. The best first step is replacing the seven deprecated dependencies, worth about 6.5 points. Tidying the declared packages would lift Production Readiness itself, worth about 6.1 points. Raising Production Readiness to 70 would lift the score to about 64.1.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten known security holes in the packages the code depends on can be used by attackers, and eight places in the code run text as code, which an attacker could use. Pinning each tool to an exact version, updating the vulnerable packages and replacing text run as code with direct calls would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code. The four loops of files that import each other need breaking.
The product code is 59,783 lines, about €100,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 49.9 to 70, the lowest score rated Strong, the score would rise from 57.7 to about 64.1.
Code composition: what the lines of code are
Product code 61%Tests 39%
Rebuild cost: about €100,000 · Estimate
Cost to rebuild
€34,000 to €170,000, for 566 to 1,794 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 58. 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: 59,783 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
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7).
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 €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 49.9 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 7 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 6.5 points for low effort, because it clears the 7 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
144 modules, with 184 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 104 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.
cli.src.lib.cmds uses cli.src.lib.types, so a change to cli.src.lib.types can break cli.src.lib.cmds, while a change to cli.src.lib.cmds can't break cli.src.lib.types.
Position
Below the diagonal: cli.src.lib.cmds uses a module listed above it, which is the healthy direction.
core.src.Ornament uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.Ornament, while a change to core.src.Ornament can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.Ornament uses a module listed above it, which is the healthy direction.
core.src.Ornament uses core.src.types.global, so a change to core.src.types.global can break core.src.Ornament, while a change to core.src.Ornament can't break core.src.types.global.
Position
Below the diagonal: core.src.Ornament uses a module listed above it, which is the healthy direction.
core.src.reality.geometry.SpatialGeometry uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.reality.geometry.SpatialGeometry, while a change to core.src.reality.geometry.SpatialGeometry can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.reality.geometry.SpatialGeometry uses a module listed above it, which is the healthy direction.
9→15 core.src.reality.geometry.SpatialGeometry uses core.src.types.typespart of a loop✕
Connections
2 pairs of types, where a type in core.src.reality.geometry.SpatialGeometry uses a type in core.src.types.types.
core.src.reality.geometry.SpatialGeometry uses core.src.types.types, so a change to core.src.types.types can break core.src.reality.geometry.SpatialGeometry, while a change to core.src.reality.geometry.SpatialGeometry can't break core.src.types.types.
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.
core.src.types.motion.spatializedMotion uses core.src.types.motion.spatializedVisual, so a change to core.src.types.motion.spatializedVisual can break core.src.types.motion.spatializedMotion, while a change to core.src.types.motion.spatializedMotion can't break core.src.types.motion.spatializedVisual.
Position
Below the diagonal: core.src.types.motion.spatializedMotion uses a module listed above it, which is the healthy direction.
react.src.facades uses core.src.types.global, so a change to core.src.types.global can break react.src.facades, while a change to react.src.facades can't break core.src.types.global.
Position
Below the diagonal: react.src.facades uses a module listed above it, which is the healthy direction.
react.src.facades uses react.src.jsx.jsx-namespace, so a change to react.src.jsx.jsx-namespace can break react.src.facades, while a change to react.src.facades can't break react.src.jsx.jsx-namespace.
Position
Below the diagonal: react.src.facades uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.types uses react.src.jsx.jsx-namespace, so a change to react.src.jsx.jsx-namespace can break react.src.spatialized-container.types, while a change to react.src.spatialized-container.types can't break react.src.jsx.jsx-namespace.
Position
Below the diagonal: react.src.spatialized-container.types uses a module listed above it, which is the healthy direction.
core.src.motion.AnimationObject uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.motion.AnimationObject, while a change to core.src.motion.AnimationObject can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.motion.AnimationObject uses a module listed above it, which is the healthy direction.
core.src.motion.AnimationObject uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break core.src.motion.AnimationObject, while a change to core.src.motion.AnimationObject can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: core.src.motion.AnimationObject uses a module listed above it, which is the healthy direction.
core.src.types.motion.spatializedElementMotion uses core.src.types.motion.spatializedVisual, so a change to core.src.types.motion.spatializedVisual can break core.src.types.motion.spatializedElementMotion, while a change to core.src.types.motion.spatializedElementMotion can't break core.src.types.motion.spatializedVisual.
Position
Below the diagonal: core.src.types.motion.spatializedElementMotion uses a module listed above it, which is the healthy direction.
core.src.types.motion.spatializedElementMotion uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break core.src.types.motion.spatializedElementMotion, while a change to core.src.types.motion.spatializedElementMotion can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: core.src.types.motion.spatializedElementMotion uses a module listed above it, which is the healthy direction.
core.src.types.types uses core.src.reality.geometry.SpatialGeometry, so a change to core.src.reality.geometry.SpatialGeometry can break core.src.types.types, while a change to core.src.types.types can't break core.src.reality.geometry.SpatialGeometry.
Position
Below the diagonal: core.src.types.types uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.context.SpatializedContainerContext uses core.src.types.global, so a change to core.src.types.global can break react.src.spatialized-container.context.SpatializedContainerContext, while a change to react.src.spatialized-container.context.SpatializedContainerContext can't break core.src.types.global.
Position
Below the diagonal: react.src.spatialized-container.context.SpatializedContainerContext uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in react.src.spatialized-container.context.SpatializedContainerContext uses a type in react.src.spatialized-container.types.
react.src.spatialized-container.context.SpatializedContainerContext uses react.src.spatialized-container.types, so a change to react.src.spatialized-container.types can break react.src.spatialized-container.context.SpatializedContainerContext, while a change to react.src.spatialized-container.context.SpatializedContainerContext can't break react.src.spatialized-container.types.
Position
Below the diagonal: react.src.spatialized-container.context.SpatializedContainerContext uses a module listed above it, which is the healthy direction.
core.src.SpatializedElement uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.SpatializedElement, while a change to core.src.SpatializedElement can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.SpatializedElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedElement uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break core.src.SpatializedElement, while a change to core.src.SpatializedElement can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: core.src.SpatializedElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedElement uses core.src.motion.AnimationObject, so a change to core.src.motion.AnimationObject can break core.src.SpatializedElement, while a change to core.src.SpatializedElement can't break core.src.motion.AnimationObject.
Position
Below the diagonal: core.src.SpatializedElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedElement uses core.src.types.types, so a change to core.src.types.types can break core.src.SpatializedElement, while a change to core.src.SpatializedElement can't break core.src.types.types.
Position
Below the diagonal: core.src.SpatializedElement uses a module listed above it, which is the healthy direction.
core.src.WebMsgCommand uses core.src.types.types, so a change to core.src.types.types can break core.src.WebMsgCommand, while a change to core.src.WebMsgCommand can't break core.src.types.types.
Position
Below the diagonal: core.src.WebMsgCommand uses a module listed above it, which is the healthy direction.
core.src.platform-adapter.interface uses core.src.types.types, so a change to core.src.types.types can break core.src.platform-adapter.interface, while a change to core.src.platform-adapter.interface can't break core.src.types.types.
Position
Below the diagonal: core.src.platform-adapter.interface uses a module listed above it, which is the healthy direction.
core.src.reality.Attachment uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.reality.Attachment, while a change to core.src.reality.Attachment can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.reality.Attachment uses a module listed above it, which is the healthy direction.
core.src.reality.Attachment uses core.src.types.global, so a change to core.src.types.global can break core.src.reality.Attachment, while a change to core.src.reality.Attachment can't break core.src.types.global.
Position
Below the diagonal: core.src.reality.Attachment uses a module listed above it, which is the healthy direction.
core.src.reality.Attachment uses core.src.types.types, so a change to core.src.types.types can break core.src.reality.Attachment, while a change to core.src.reality.Attachment can't break core.src.types.types.
Position
Below the diagonal: core.src.reality.Attachment uses a module listed above it, which is the healthy direction.
core.src.types.motion.entityMotion uses core.src.types.types, so a change to core.src.types.types can break core.src.types.motion.entityMotion, while a change to core.src.types.motion.entityMotion can't break core.src.types.types.
Position
Below the diagonal: core.src.types.motion.entityMotion uses a module listed above it, which is the healthy direction.
core.src.SpatialScene uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.SpatialScene, while a change to core.src.SpatialScene can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.SpatialScene uses a module listed above it, which is the healthy direction.
core.src.SpatialScene uses core.src.types.types, so a change to core.src.types.types can break core.src.SpatialScene, while a change to core.src.SpatialScene can't break core.src.types.types.
Position
Below the diagonal: core.src.SpatialScene uses a module listed above it, which is the healthy direction.
core.src.SpatialScene uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break core.src.SpatialScene, while a change to core.src.SpatialScene can't break core.src.SpatializedElement.
Position
Below the diagonal: core.src.SpatialScene uses a module listed above it, which is the healthy direction.
core.src.Spatialized2DElement uses core.src.types.types, so a change to core.src.types.types can break core.src.Spatialized2DElement, while a change to core.src.Spatialized2DElement can't break core.src.types.types.
Position
Below the diagonal: core.src.Spatialized2DElement uses a module listed above it, which is the healthy direction.
core.src.Spatialized2DElement uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break core.src.Spatialized2DElement, while a change to core.src.Spatialized2DElement can't break core.src.SpatializedElement.
Position
Below the diagonal: core.src.Spatialized2DElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedStatic3DElement uses core.src.types.types, so a change to core.src.types.types can break core.src.SpatializedStatic3DElement, while a change to core.src.SpatializedStatic3DElement can't break core.src.types.types.
Position
Below the diagonal: core.src.SpatializedStatic3DElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedStatic3DElement uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break core.src.SpatializedStatic3DElement, while a change to core.src.SpatializedStatic3DElement can't break core.src.SpatializedElement.
Position
Below the diagonal: core.src.SpatializedStatic3DElement uses a module listed above it, which is the healthy direction.
core.src.motion.entity.EntityAnimationObject uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.motion.entity.EntityAnimationObject, while a change to core.src.motion.entity.EntityAnimationObject can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.motion.entity.EntityAnimationObject uses a module listed above it, which is the healthy direction.
core.src.motion.entity.EntityAnimationObject uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break core.src.motion.entity.EntityAnimationObject, while a change to core.src.motion.entity.EntityAnimationObject can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: core.src.motion.entity.EntityAnimationObject uses a module listed above it, which is the healthy direction.
core.src.motion.entity.EntityAnimationObject uses core.src.types.motion.entityMotion, so a change to core.src.types.motion.entityMotion can break core.src.motion.entity.EntityAnimationObject, while a change to core.src.motion.entity.EntityAnimationObject can't break core.src.types.motion.entityMotion.
Position
Below the diagonal: core.src.motion.entity.EntityAnimationObject uses a module listed above it, which is the healthy direction.
core.src.reality.component.SpatialComponent uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.reality.component.SpatialComponent, while a change to core.src.reality.component.SpatialComponent can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.reality.component.SpatialComponent uses a module listed above it, which is the healthy direction.
core.src.reality.component.SpatialComponent uses core.src.WebMsgCommand, so a change to core.src.WebMsgCommand can break core.src.reality.component.SpatialComponent, while a change to core.src.reality.component.SpatialComponent can't break core.src.WebMsgCommand.
Position
Below the diagonal: core.src.reality.component.SpatialComponent uses a module listed above it, which is the healthy direction.
core.src.reality.material.SpatialMaterial uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.reality.material.SpatialMaterial, while a change to core.src.reality.material.SpatialMaterial can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.reality.material.SpatialMaterial uses a module listed above it, which is the healthy direction.
core.src.reality.material.SpatialMaterial uses core.src.platform-adapter.interface, so a change to core.src.platform-adapter.interface can break core.src.reality.material.SpatialMaterial, while a change to core.src.reality.material.SpatialMaterial can't break core.src.platform-adapter.interface.
Position
Below the diagonal: core.src.reality.material.SpatialMaterial uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.context.PortalInstanceContext uses react.src.spatialized-container.types, so a change to react.src.spatialized-container.types can break react.src.spatialized-container.context.PortalInstanceContext, while a change to react.src.spatialized-container.context.PortalInstanceContext can't break react.src.spatialized-container.types.
Position
Below the diagonal: react.src.spatialized-container.context.PortalInstanceContext uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in react.src.spatialized-container.context.PortalInstanceContext uses a type in react.src.spatialized-container.context.SpatializedContainerContext.
react.src.spatialized-container.context.PortalInstanceContext uses react.src.spatialized-container.context.SpatializedContainerContext, so a change to react.src.spatialized-container.context.SpatializedContainerContext can break react.src.spatialized-container.context.PortalInstanceContext, while a change to react.src.spatialized-container.context.PortalInstanceContext can't break react.src.spatialized-container.context.SpatializedContainerContext.
Position
Below the diagonal: react.src.spatialized-container.context.PortalInstanceContext uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.context.PortalInstanceContext uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break react.src.spatialized-container.context.PortalInstanceContext, while a change to react.src.spatialized-container.context.PortalInstanceContext can't break core.src.SpatializedElement.
Position
Below the diagonal: react.src.spatialized-container.context.PortalInstanceContext uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion uses core.src.types.motion.spatializedVisual, so a change to core.src.types.motion.spatializedVisual can break react.src.spatialized-container.motion, while a change to react.src.spatialized-container.motion can't break core.src.types.motion.spatializedVisual.
Position
Below the diagonal: react.src.spatialized-container.motion uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion uses react.src.jsx.jsx-namespace, so a change to react.src.jsx.jsx-namespace can break react.src.spatialized-container.motion, while a change to react.src.spatialized-container.motion can't break react.src.jsx.jsx-namespace.
Position
Below the diagonal: react.src.spatialized-container.motion uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break react.src.spatialized-container.motion, while a change to react.src.spatialized-container.motion can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: react.src.spatialized-container.motion uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break react.src.spatialized-container.motion, while a change to react.src.spatialized-container.motion can't break core.src.SpatializedElement.
Position
Below the diagonal: react.src.spatialized-container.motion uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion.AnimationBinding uses core.src.types.motion.spatializedVisual, so a change to core.src.types.motion.spatializedVisual can break react.src.spatialized-container.motion.AnimationBinding, while a change to react.src.spatialized-container.motion.AnimationBinding can't break core.src.types.motion.spatializedVisual.
Position
Below the diagonal: react.src.spatialized-container.motion.AnimationBinding uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion.AnimationBinding uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break react.src.spatialized-container.motion.AnimationBinding, while a change to react.src.spatialized-container.motion.AnimationBinding can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: react.src.spatialized-container.motion.AnimationBinding uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion.AnimationBinding uses core.src.motion.AnimationObject, so a change to core.src.motion.AnimationObject can break react.src.spatialized-container.motion.AnimationBinding, while a change to react.src.spatialized-container.motion.AnimationBinding can't break core.src.motion.AnimationObject.
Position
Below the diagonal: react.src.spatialized-container.motion.AnimationBinding uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.motion.AnimationBinding uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break react.src.spatialized-container.motion.AnimationBinding, while a change to react.src.spatialized-container.motion.AnimationBinding can't break core.src.SpatializedElement.
Position
Below the diagonal: react.src.spatialized-container.motion.AnimationBinding uses a module listed above it, which is the healthy direction.
core.src.reality.entity.SpatialEntity uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.reality.entity.SpatialEntity, while a change to core.src.reality.entity.SpatialEntity can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.reality.entity.SpatialEntity uses a module listed above it, which is the healthy direction.
core.src.reality.entity.SpatialEntity uses core.src.types.types, so a change to core.src.types.types can break core.src.reality.entity.SpatialEntity, while a change to core.src.reality.entity.SpatialEntity can't break core.src.types.types.
Position
Below the diagonal: core.src.reality.entity.SpatialEntity uses a module listed above it, which is the healthy direction.
core.src.reality.entity.SpatialEntity uses core.src.types.motion.entityMotion, so a change to core.src.types.motion.entityMotion can break core.src.reality.entity.SpatialEntity, while a change to core.src.reality.entity.SpatialEntity can't break core.src.types.motion.entityMotion.
Position
Below the diagonal: core.src.reality.entity.SpatialEntity uses a module listed above it, which is the healthy direction.
core.src.reality.entity.SpatialEntity uses core.src.motion.entity.EntityAnimationObject, so a change to core.src.motion.entity.EntityAnimationObject can break core.src.reality.entity.SpatialEntity, while a change to core.src.reality.entity.SpatialEntity can't break core.src.motion.entity.EntityAnimationObject.
Position
Below the diagonal: core.src.reality.entity.SpatialEntity uses a module listed above it, which is the healthy direction.
core.src.reality.entity.SpatialEntity uses core.src.reality.component.SpatialComponent, so a change to core.src.reality.component.SpatialComponent can break core.src.reality.entity.SpatialEntity, while a change to core.src.reality.entity.SpatialEntity can't break core.src.reality.component.SpatialComponent.
Position
Below the diagonal: core.src.reality.entity.SpatialEntity uses a module listed above it, which is the healthy direction.
react.src.spatialized-container uses react.src.jsx.jsx-namespace, so a change to react.src.jsx.jsx-namespace can break react.src.spatialized-container, while a change to react.src.spatialized-container can't break react.src.jsx.jsx-namespace.
Position
Below the diagonal: react.src.spatialized-container uses a module listed above it, which is the healthy direction.
react.src.spatialized-container uses react.src.spatialized-container.types, so a change to react.src.spatialized-container.types can break react.src.spatialized-container, while a change to react.src.spatialized-container can't break react.src.spatialized-container.types.
Position
Below the diagonal: react.src.spatialized-container uses a module listed above it, which is the healthy direction.
react.src.spatialized-container uses core.src.types.types, so a change to core.src.types.types can break react.src.spatialized-container, while a change to react.src.spatialized-container can't break core.src.types.types.
Position
Below the diagonal: react.src.spatialized-container uses a module listed above it, which is the healthy direction.
react.src.spatialized-container uses core.src.Spatialized2DElement, so a change to core.src.Spatialized2DElement can break react.src.spatialized-container, while a change to react.src.spatialized-container can't break core.src.Spatialized2DElement.
Position
Below the diagonal: react.src.spatialized-container uses a module listed above it, which is the healthy direction.
react.src.spatialized-container uses react.src.spatialized-container.context.PortalInstanceContext, so a change to react.src.spatialized-container.context.PortalInstanceContext can break react.src.spatialized-container, while a change to react.src.spatialized-container can't break react.src.spatialized-container.context.PortalInstanceContext.
Position
Below the diagonal: react.src.spatialized-container uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.hooks uses core.src.types.global, so a change to core.src.types.global can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break core.src.types.global.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.hooks uses react.src.spatialized-container.types, so a change to react.src.spatialized-container.types can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break react.src.spatialized-container.types.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.hooks uses core.src.types.types, so a change to core.src.types.types can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break core.src.types.types.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in react.src.spatialized-container.hooks uses a type in react.src.spatialized-container.context.SpatializedContainerContext.
react.src.spatialized-container.hooks uses react.src.spatialized-container.context.SpatializedContainerContext, so a change to react.src.spatialized-container.context.SpatializedContainerContext can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break react.src.spatialized-container.context.SpatializedContainerContext.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.hooks uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break core.src.SpatializedElement.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
react.src.spatialized-container.hooks uses react.src.spatialized-container.context.PortalInstanceContext, so a change to react.src.spatialized-container.context.PortalInstanceContext can break react.src.spatialized-container.hooks, while a change to react.src.spatialized-container.hooks can't break react.src.spatialized-container.context.PortalInstanceContext.
Position
Below the diagonal: react.src.spatialized-container.hooks uses a module listed above it, which is the healthy direction.
react.src.utils uses core.src.types.types, so a change to core.src.types.types can break react.src.utils, while a change to react.src.utils can't break core.src.types.types.
Position
Below the diagonal: react.src.utils uses a module listed above it, which is the healthy direction.
react.src.utils uses core.src.Spatialized2DElement, so a change to core.src.Spatialized2DElement can break react.src.utils, while a change to react.src.utils can't break core.src.Spatialized2DElement.
Position
Below the diagonal: react.src.utils uses a module listed above it, which is the healthy direction.
core.src.SpatializedDynamic3DElement uses core.src.types.types, so a change to core.src.types.types can break core.src.SpatializedDynamic3DElement, while a change to core.src.SpatializedDynamic3DElement can't break core.src.types.types.
Position
Below the diagonal: core.src.SpatializedDynamic3DElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedDynamic3DElement uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break core.src.SpatializedDynamic3DElement, while a change to core.src.SpatializedDynamic3DElement can't break core.src.SpatializedElement.
Position
Below the diagonal: core.src.SpatializedDynamic3DElement uses a module listed above it, which is the healthy direction.
core.src.SpatializedDynamic3DElement uses core.src.reality.entity.SpatialEntity, so a change to core.src.reality.entity.SpatialEntity can break core.src.SpatializedDynamic3DElement, while a change to core.src.SpatializedDynamic3DElement can't break core.src.reality.entity.SpatialEntity.
Position
Below the diagonal: core.src.SpatializedDynamic3DElement uses a module listed above it, which is the healthy direction.
core.src.reality uses core.src.types.types, so a change to core.src.types.types can break core.src.reality, while a change to core.src.reality can't break core.src.types.types.
Position
Below the diagonal: core.src.reality uses a module listed above it, which is the healthy direction.
core.src.reality uses core.src.reality.Attachment, so a change to core.src.reality.Attachment can break core.src.reality, while a change to core.src.reality can't break core.src.reality.Attachment.
Position
Below the diagonal: core.src.reality uses a module listed above it, which is the healthy direction.
core.src.reality uses core.src.reality.entity.SpatialEntity, so a change to core.src.reality.entity.SpatialEntity can break core.src.reality, while a change to core.src.reality can't break core.src.reality.entity.SpatialEntity.
Position
Below the diagonal: core.src.reality uses a module listed above it, which is the healthy direction.
react.src.reality.hooks.EntityMotionBinding uses core.src.types.motion.spatializedMotion, so a change to core.src.types.motion.spatializedMotion can break react.src.reality.hooks.EntityMotionBinding, while a change to react.src.reality.hooks.EntityMotionBinding can't break core.src.types.motion.spatializedMotion.
Position
Below the diagonal: react.src.reality.hooks.EntityMotionBinding uses a module listed above it, which is the healthy direction.
react.src.reality.hooks.EntityMotionBinding uses core.src.types.motion.entityMotion, so a change to core.src.types.motion.entityMotion can break react.src.reality.hooks.EntityMotionBinding, while a change to react.src.reality.hooks.EntityMotionBinding can't break core.src.types.motion.entityMotion.
Position
Below the diagonal: react.src.reality.hooks.EntityMotionBinding uses a module listed above it, which is the healthy direction.
react.src.reality.hooks.EntityMotionBinding uses core.src.motion.entity.EntityAnimationObject, so a change to core.src.motion.entity.EntityAnimationObject can break react.src.reality.hooks.EntityMotionBinding, while a change to react.src.reality.hooks.EntityMotionBinding can't break core.src.motion.entity.EntityAnimationObject.
Position
Below the diagonal: react.src.reality.hooks.EntityMotionBinding uses a module listed above it, which is the healthy direction.
react.src.reality.hooks.EntityMotionBinding uses core.src.reality.entity.SpatialEntity, so a change to core.src.reality.entity.SpatialEntity can break react.src.reality.hooks.EntityMotionBinding, while a change to react.src.reality.hooks.EntityMotionBinding can't break core.src.reality.entity.SpatialEntity.
Position
Below the diagonal: react.src.reality.hooks.EntityMotionBinding uses a module listed above it, which is the healthy direction.
core.src uses cli.src.lib.utils.sceneUtils, so a change to cli.src.lib.utils.sceneUtils can break core.src, while a change to core.src can't break cli.src.lib.utils.sceneUtils.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.types.types, so a change to core.src.types.types can break core.src, while a change to core.src can't break core.src.types.types.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.WebMsgCommand, so a change to core.src.WebMsgCommand can break core.src, while a change to core.src can't break core.src.WebMsgCommand.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.platform-adapter.interface, so a change to core.src.platform-adapter.interface can break core.src, while a change to core.src can't break core.src.platform-adapter.interface.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.Spatialized2DElement, so a change to core.src.Spatialized2DElement can break core.src, while a change to core.src can't break core.src.Spatialized2DElement.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.SpatializedStatic3DElement, so a change to core.src.SpatializedStatic3DElement can break core.src, while a change to core.src can't break core.src.SpatializedStatic3DElement.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src uses core.src.SpatializedDynamic3DElement, so a change to core.src.SpatializedDynamic3DElement can break core.src, while a change to core.src can't break core.src.SpatializedDynamic3DElement.
Position
Below the diagonal: core.src uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses cli.src.lib.utils.sceneUtils, so a change to cli.src.lib.utils.sceneUtils can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break cli.src.lib.utils.sceneUtils.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.SpatialObject, so a change to core.src.SpatialObject can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.SpatialObject.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.types.motion.spatializedElementMotion, so a change to core.src.types.motion.spatializedElementMotion can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.types.motion.spatializedElementMotion.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in core.src.JSBCommand uses a type in core.src.types.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
core.src.JSBCommand uses core.src.types.types, so a change to core.src.types.types can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.types.types.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.SpatializedElement, so a change to core.src.SpatializedElement can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.SpatializedElement.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.types.motion.entityMotion, so a change to core.src.types.motion.entityMotion can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.types.motion.entityMotion.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.reality.component.SpatialComponent, so a change to core.src.reality.component.SpatialComponent can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.reality.component.SpatialComponent.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.reality.entity.SpatialEntity, so a change to core.src.reality.entity.SpatialEntity can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.reality.entity.SpatialEntity.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.JSBCommand uses core.src.SpatializedDynamic3DElement, so a change to core.src.SpatializedDynamic3DElement can break core.src.JSBCommand, while a change to core.src.JSBCommand can't break core.src.SpatializedDynamic3DElement.
Position
Below the diagonal: core.src.JSBCommand uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.Ornament, so a change to core.src.Ornament can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.Ornament.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.types.types, so a change to core.src.types.types can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.types.types.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.reality.Attachment, so a change to core.src.reality.Attachment can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.reality.Attachment.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.SpatialScene, so a change to core.src.SpatialScene can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.SpatialScene.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.Spatialized2DElement, so a change to core.src.Spatialized2DElement can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.Spatialized2DElement.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.SpatializedStatic3DElement, so a change to core.src.SpatializedStatic3DElement can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.SpatializedStatic3DElement.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.reality.entity.SpatialEntity, so a change to core.src.reality.entity.SpatialEntity can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.reality.entity.SpatialEntity.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
core.src.SpatialSession uses core.src.SpatializedDynamic3DElement, so a change to core.src.SpatializedDynamic3DElement can break core.src.SpatialSession, while a change to core.src.SpatialSession can't break core.src.SpatializedDynamic3DElement.
Position
Below the diagonal: core.src.SpatialSession uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
45
High / Critical
A03:2025 — Software Supply Chain Failures
31
High / Critical
A02:2025 — Security Misconfiguration
5
High / Critical
Roadmap
Top priorities: Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7); Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Enable Dependabot/Renovate or a dependency-review gate.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7).
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.
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 — 58
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 — 408
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 — 217
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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 79 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 79 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, 621 of 683 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.
D8 Code Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 24 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 195 production file(s) those files import are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 94.2% whatever they read, rather than published as low coverage or counted toward the figure. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from it.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its SwiftPM package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 1369 sampled here came from .js/.mjs/.ts/.tsx files. This repository's .swift source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
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. `apps/spatial-remix-min/app/routes.ts`, `apps/spatial-remix-min/react-router.config.ts`, `packages/core/src/runtime/keys.ts`, `packages/react/src/MaterialPresets.ts`, `packages/react/src/eager.ts`, … (+8 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.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
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/visionOS/web-spatial/manager/OrnamentManager.swift, 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 dev`) 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: "> npm run testServer / > webspatial-sdk@1.0.0 testServer / > cd apps/test-server/ && npm run dev -- --host / > web-content@0.2.1 dev / > node esbuild.mjs --host / Preparing dist folder... / Assets copied to dist. / HTTP server is running on http://localhost:5173 / esbuild ready! / 🌼 daisyUI 4.12.24 / ├─ ✔︎ 2 themes added https://daisyui.com/docs/themes / ╰─ ★ Star daisyUI on GitHub https://github.com/saadeghi/daisyui / (node:11548) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated / (Use `node --trace-deprecation ...` to show where the warning was created)" 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 (dev). the dev server (`npm run dev`) 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: "> npm run testServer / > webspatial-sdk@1.0.0 testServer / > cd apps/test-server/ && npm run dev -- --host / > web-content@0.2.1 dev / > node esbuild.mjs --host / Preparing dist folder... / Assets copied to dist. / HTTP server is running on http://localhost:5173 / esbuild ready! / 🌼 daisyUI 4.12.24 / ├─ ✔︎ 2 themes added https://daisyui.com/docs/themes / ╰─ ★ Star daisyUI on GitHub https://github.com/saadeghi/daisyui / (node:11548) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated / (Use `node --trace-deprecation ...` to show where the warning was created)" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — 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. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. 32 further occurrence(s) are not listed individually; the score already reflects all 72.
X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X12 Unreachable branch — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X16 Unfloored truncation loop — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X17 Uncapped recursion over a caller-supplied document — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X2 Cancellation propagation — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X21 Side-effecting pattern guard — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X24 Document value interpolated into markup unescaped — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X25 Inert configuration knob — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X29 Per-element action decided by a fixed element — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X30 Support guard that admits what it rejects — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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: 4 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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WebSpatialInspector.WebSpatialInspector at 36. A further 3 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 OrnamentElement.contentAlignment3D at 27 — 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/visionOS/web-spatial/model/OrnamentElement.swift (OrnamentElement.contentAlignment3D at 27), packages/cli/src/lib/xcode/xcodeproject.ts (XcodeProject.fixProjectFunction 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.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with WebSpatialInspector.WebSpatialInspector (cyclomatic 36), useEntityEvent.createEventProxy (cyclomatic 34), useRealityEvents.createEventProxy (cyclomatic 34). — 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 28 together lifts Cyclomatic Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with WebSpatialInspector.WebSpatialInspector (cognitive 55), useEntityEvent.createEventProxy (cognitive 48), useRealityEvents.createEventProxy (cognitive 48). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 6.6 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: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.0 / 10Stronggated by 17 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 FunctionTooLong finding(s) in God Classes — start with WebSpatialInspector.tsx (3), SpatializedContainer.tsx, Ornament.tsx. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with SpatialScene.swift, SpatialWebViewModel.swift, SpatialWebController.swift. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 FileTooLong finding(s) in God Classes — start with SpatialScene.swift, WebSpatialInspector.tsx, JSBCommand.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
11 duplicated block group(s) detected. 1.0 % of the production lines (581 of 59,783) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx, .ts (83% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (3 corresponding lines) · ×3packages/visionOS/web-spatial/webview/SpatialWebController.swift:33
Edited copy of a member (14 corresponding lines) · ×2packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:73
Edited copy of a member (8 corresponding lines) · ×2packages/visionOS/web-spatial/model/SpatializedElement.swift:97
Edited copy of a member (10 corresponding lines) · ×2packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:34
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with SpatialWebController.swift (2), SpatialScene.swift. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with SpatializedDynamic3DView.swift, SpatialObject.swift. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with SpatializedElement.swift, SpatialObject.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.6 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
10 production modules (npm+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 9 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @webspatial/platform-visionos · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SpatialScene.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 94.2%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/react/, the 3 run(s) test reliability made; vitest in tests/marginal-delta-vite/: not run). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 6 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
4 skipped (4 with a documented reason), 10 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 926 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions: keeps binding methods outside the public opaque animation type · ×6packages/react/src/reality/hooks/useEntityAnimation.redesign.test.ts:166
Mock-dominated test: use2DFrameDetector notifies and wires observers/listeners · ×21packages/react/src/coverage-boost.test.ts:395
No direct assertions: should pass · ×4tests/ci-test/test/e2e.test.ts:11
Skipped (documented): Reality parity — real-impl does NOT render the documented <div aria-hidden> placeholder; align via §15.8 follow-up · ×4packages/react/src/__tests__/parity.test.tsx:240
What to do
Resolve the 21 Mock-dominated test finding(s) in Test Quality — start with useEntity.race.test.tsx (5), coverage-boost.test.ts (4), PortalInstanceContext.coverage.test.ts (3). — One of this dimension's main actionable groups (21 recommendation-level).
Resolve the 6 No assertions finding(s) in Test Quality — start with useEntityAnimation.redesign.test.ts (2), entityMotionTypes.test.ts (2), scene-polyfill.test.ts. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 No direct assertions finding(s) in Test Quality — start with core-api.spec.tsx (2), e2e.test.ts, webspatial-builder.test.ts. — One of this dimension's main actionable groups (4 recommendation-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 (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (879 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/ (388 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/react/ (590 tests); mocha via `pnpm install --frozen-lockfile --ignore-scripts` in tests/autoTest/ (8 tests); mocha via `pnpm install --frozen-lockfile --ignore-scripts` in tests/ci-test/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in tests/marginal-delta-vite/ (4 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.
43 outdated direct production npm dependency(ies) of 62 graded, 1 pinning defect(s), across 15 package.json (10 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 5 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 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7). — One of this dimension's main actionable groups (7 recommendation-level).
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with package.json (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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 0 third-party package(s) use a banned license. This repository's 1 SwiftPM file(s) declare no third-party dependencies and no committed resolution pins any, so there is no third-party package licence to grade — a complete answer, not a gap in coverage. It also commits no CocoaPods or Carthage manifest, so SwiftPM is the only package manager it takes dependencies through. This repository's OWN licence is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's SwiftPM package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: apps/test-server/src/pages/reality/gestures.tsx (2×58=116); packages/react/src/reality/hooks/useEntity.tsx (4×25=100); packages/react/src/reality/hooks/useSpatialMaterial.tsx (4×20=80) Repeated repair below the complexity floor: packages/react/src/reality/hooks/EntityMotionBinding.ts (8 of 14 changes were fixes); packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift (4 of 4 changes were fixes); packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift (3 of 5 changes were fixes)
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with gestures.tsx, useEntity.tsx, useSpatialMaterial.tsx. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with EntityMotionBinding.ts, SpatializedDynamic3DView.swift, SpatializedStatic3DView.swift. — One of this dimension's main actionable groups (3 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 Factor6.9 / 10Adequate✓ 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.
70 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/visionOS/web-spatial/model/entity-motion/EntityMotionAnimationObject.swift. Counted over 224 of the 494 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)
What to do
Resolve the 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 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.
14 deducted task-comment markers across 58958 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 12 TodoComment finding(s) in Explicit Debt — start with WKWebViewManager.swift (2), SpatialWebViewModel.swift, Spatialized2DElementView.swift. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with SpatialScene.swift. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with build.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
5 naming inconsistencies among 123 declarations measured against a convention their peers follow.
`resolveJsbAdapterPlatform` spells `Jsb` where 25 names in the project spell it `JSB`packages/core/src/runtime/jsbAdapterPlatform.ts:34
`deepCloneJSON` spells `JSON` where 14 names in the project spell it `Json`packages/core/src/utils.ts:70
`jsxDEV` spells `DEV` where 12 names in the project spell it `Dev`packages/react/src/jsx/jsx-shared.ts:174
`sceneID` spells `ID` where 76 names in the project spell it `Id`packages/visionOS/web-spatial/model/SpatialApp.swift:20
`navigationStateListenerID` spells `ID` where 76 names in the project spell it `Id`packages/visionOS/web-spatial/view/SpatialNavView.swift:81
What to do
Resolve the 1 `resolveJsbAdapterPlatform` spells `Jsb` where 25 names in the project… finding(s) in Naming Consistency — start with jsbAdapterPlatform.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `deepCloneJSON` spells `JSON` where 14 names in the project spell it… finding(s) in Naming Consistency — start with utils.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `jsxDEV` spells `DEV` where 12 names in the project spell it `Dev` finding(s) in Naming Consistency — start with jsx-shared.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.
Do you agree with this assessment?
D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×3packages/cli/src/lib/utils/Log.ts:103
What to do
Resolve the 41 redundant comment finding(s) in Comment Value — start with materialapi.tsx (4), load.ts (3), JSBCommand.ts (3). — One of this dimension's main actionable groups (41 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion4.5 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
3 of 11 build units (SwiftPM, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3packages/visionOS/package.json:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
1 % of calls cross a namespace and 1 % go through an interface, but 92 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .js/.mjs/.ts/.tsx source only — this repository's .swift was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
45 finding(s): 0 critical, 43 high, 2 medium, 0 low. 30 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 13 file(s) — `apps/spatial-remix-min/app/routes.ts` (lines 3–7), `apps/spatial-remix-min/react-router.config.ts` (lines 3–7), `packages/core/src/runtime/keys.ts` (line 106), `packages/core/src/scene-polyfill.test.ts` (lines 25–26, lines 51–52, lines 66–77, …), `packages/react/src/MaterialPresets.ts` (line 46), … (+8 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
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 30 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (30 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
1 of 224 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is apps/test-server/src/pages/memoryStats/index.tsx. Counted over 224 of the 494 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 13 Change coupling finding(s) in Change Coupling — start with index.tsx (3), BoxEntity.tsx (2), JSBCommand.ts (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with SpatialScene.swift, AttachmentManager.swift. — 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 the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure7.2 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/visionOS/web-spatial/static-web/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<div> moves — its inline style sets `transition: width 0.2s ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — apps/spatial-vite-min/src/xr-monitor-demo.tsx:99
<input> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator. — packages/react/src/inspector/WebSpatialInspector.tsx:449
`.xterm.focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/test-server/public/css/xterm.css:48
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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.
`help` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/lib/cmds/help.ts:59
`launch` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/lib/cmds/launch.ts:3
`shutdown` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/lib/cmds/shutdown.ts:3
`moveProjectFrom` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:24
`upload` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/lib/xcode/index.ts:19
`runWithSimulator` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:78
`runWithHistory` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:107
`shutdownSimulator` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:159
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — tests/ci-test/test/webspatial-builder.test.ts:1
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
1 ADR-shaped document(s) detected by content — `openspec/changes/archive/2026-06-30-lazy-load-spatial-runtime/REVIEW.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
`openspec/changes/add-entity-transform-animation/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/react-sdk`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — openspec/changes/add-entity-transform-animation/design.md:417
`openspec/changes/add-entity-transform-animation/design.zh.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/react-sdk`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — openspec/changes/add-entity-transform-animation/design.zh.md:413
`openspec/changes/redesign-entity-motion-api/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/platform-visionos`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — openspec/changes/redesign-entity-motion-api/design.md:118
`openspec/changes/redesign-entity-motion-api/design.zh.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/platform-visionos`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — openspec/changes/redesign-entity-motion-api/design.zh.md:118
`openspec/changes/spatialized-element-motion-api/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — openspec/changes/spatialized-element-motion-api/design.md:76
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Update openspec/changes/add-entity-transform-animation/design.md so it draws the parts the code has today: add @webspatial/builder, @webspatial/react-sdk.
Update openspec/changes/add-entity-transform-animation/design.zh.md so it draws the parts the code has today: add @webspatial/builder, @webspatial/react-sdk.
Update openspec/changes/redesign-entity-motion-api/design.md so it draws the parts the code has today: add @webspatial/builder, @webspatial/platform-visionos.
Update openspec/changes/redesign-entity-motion-api/design.zh.md so it draws the parts the code has today: add @webspatial/builder, @webspatial/platform-visionos.
Update openspec/changes/spatialized-element-motion-api/design.md so it draws the parts the code has today: add @webspatial/builder.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
CONTRIBUTING.md names Xcode 26, but the manifest declares `xcode` ^3.0.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:10
packages/react/README.md links to `../../openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md`, but `openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/react/README.md:148
What to do
Reconcile the README with reality: CONTRIBUTING.md names Xcode 26, but the manifest declares `xcode` ^3.0.1; packages/react/README.md links to `../../openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md`, but `openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.8 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/spatial-next-eager-min`, `apps/spatial-next-min`.
`apps/test-server/src/pages/Home.tsx` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/Home.tsx:48
`apps/test-server/src/pages/styledComponentsSpatialTest/index.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/styledComponentsSpatialTest/index.tsx:24
`apps/test-server/src/pages/spatialCorner/index.tsx` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatialCorner/index.tsx:43
`apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:24
`apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:29
`apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:35
`apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:54
`apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:66
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:14
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:34
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:66
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:94
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:100
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:108
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:136
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:164
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 170 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:170
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 179 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:179
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 207 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:207
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 238 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:238
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:266
`apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 297 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-guesture/index.tsx:297
`apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx` reports through `console.*` at line 286 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:286
`apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx` reports through `console.*` at line 290 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:290
`apps/test-server/src/pages/spatial-element-motion/transform-translate.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-element-motion/transform-translate.tsx:66
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:50
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:58
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:62
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:66
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:70
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 76 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:76
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 80 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:80
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 146 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:146
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 150 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:150
`apps/test-server/src/pages/spatial-converter/index.tsx` reports through `console.*` at line 154 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/spatial-converter/index.tsx:154
`apps/test-server/src/pages/scene/index.tsx` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/scene/index.tsx:50
`apps/test-server/src/pages/reality-test/index.tsx` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/reality-test/index.tsx:49
`apps/test-server/src/pages/reality-test/index.tsx` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/reality-test/index.tsx:77
`apps/test-server/src/pages/reality-test/index.tsx` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/test-server/src/pages/reality-test/index.tsx:94
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:72
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.existsSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/cli/src/lib/pwa/index.ts:62, packages/cli/src/lib/pwa/index.ts:66
`fs.existsSync` in `moveProjectFrom` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:29
`fs.mkdirSync` in `moveProjectFrom` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:30
`execSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/cli/src/lib/xcode/xcodebuild.ts:18, packages/cli/src/lib/xcode/xcodebuild.ts:33, packages/cli/src/lib/xcode/xcodebuild.ts:53, …
`fs.existsSync` in `archive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodebuild.ts:47
`fs.mkdirSync` in `archive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodebuild.ts:48
`fs.existsSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodebuild.ts:81
`fs.mkdirSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodebuild.ts:82
`fs.writeFileSync` in `modify` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodeproject.ts:106
`project.writeSync` in `modify` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodeproject.ts:106
`fs.writeFileSync` in `bindIcon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/cli/src/lib/xcode/xcodeproject.ts:202, packages/cli/src/lib/xcode/xcodeproject.ts:222, packages/cli/src/lib/xcode/xcodeproject.ts:231
`fs.writeFileSync` in `modifySwift` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/lib/xcode/xcodeproject.ts:390
`execSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:31
`execSync` in `uploadPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:50
`execSync` in `uploadApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:68
`execSync` in `shutdownSimulator` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:165
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 Safety9.7 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
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.
12 duplicated blocks under apps/ have copies in at least two of the sibling directories spatial-next-eager-min, spatial-next-min, spatial-remix-min, spatial-rspack-min, spatial-vite-min — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20
6 duplicated blocks under packages/ have copies in at least two of the sibling directories cli, core, react — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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/cli/src/lib/utils/sceneUtils.ts:68
packages/react/src/reality/hooks/useEntityEvent.tsx:10 · packages/react/src/reality/hooks/useRealityEvents.tsx:10 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/react/src/reality/hooks/useEntityEvent.tsx:10
apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20 · apps/spatial-next-min/components/LazyDemo.tsx:39 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20
packages/cli/src/lib/utils/sceneUtils.ts:68 · packages/core/src/scene-polyfill.ts:499 — 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/cli/src/lib/utils/sceneUtils.ts:68
apps/spatial-next-min/components/LazyRealityScene.tsx:16 · apps/spatial-remix-min/app/components/LazyRealityScene.tsx:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/spatial-next-min/components/LazyRealityScene.tsx:16
apps/spatial-next-eager-min/app/layout.tsx:7 · apps/spatial-next-min/app/layout.tsx:7 — 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. — apps/spatial-next-eager-min/app/layout.tsx:7
packages/core/src/JSBCommand.ts:576 · packages/core/src/JSBCommand.ts:613 — 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/core/src/JSBCommand.ts:576
packages/core/src/JSBCommand.ts:204 · packages/core/src/JSBCommand.ts:241 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/core/src/JSBCommand.ts:204
packages/core/src/utils.ts:13 · packages/react/src/spatialized-container/utils.ts:94 — 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/core/src/utils.ts:13
packages/cli/src/lib/utils/sceneUtils.ts:162 · packages/core/src/types/types.ts:184 — 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/cli/src/lib/utils/sceneUtils.ts:162
apps/spatial-next-eager-min/app/eager/page.tsx:5 · apps/spatial-next-eager-min/app/server-only-util/page.tsx:4 — 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. — apps/spatial-next-eager-min/app/eager/page.tsx:5
apps/spatial-next-min/components/LazyRealityScene.tsx:26 · apps/spatial-remix-min/app/components/LazyRealityScene.tsx:24 · apps/spatial-vite-min/src/lazy-reality-scene.tsx:18 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — apps/spatial-next-min/components/LazyRealityScene.tsx:26
packages/cli/src/lib/utils/sceneUtils.ts:24 · packages/core/src/types/types.ts:149 — 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/cli/src/lib/utils/sceneUtils.ts:24
apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:15 · apps/spatial-vite-min/src/spatial-app.tsx:84 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:15
packages/react/src/reality/components/BoxEntity.tsx:2 · packages/react/src/reality/components/ConeEntity.tsx:2 · packages/react/src/reality/components/CylinderEntity.tsx:2 · packages/react/src/reality/components/PlaneEntity.tsx:2 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react/src/reality/components/BoxEntity.tsx:2
REDACTED:17 · REDACTED:54 — 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. — REDACTED:17
packages/react/src/spatialized-container/StandardSpatializedContainer.tsx:44 · packages/react/src/spatialized-container/TransformVisibilityTaskContainer.tsx:32 — 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/react/src/spatialized-container/StandardSpatializedContainer.tsx:44
apps/spatial-next-eager-min/app/eager/page.tsx:21 · apps/spatial-remix-min/app/routes/server-ua.tsx:34 — 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. — apps/spatial-next-eager-min/app/eager/page.tsx:21
packages/core/src/motion/AnimationObject.ts:93 · packages/core/src/motion/entity/EntityAnimationObject.ts:135 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — packages/core/src/motion/AnimationObject.ts:93
packages/core/src/platform-adapter/pico-os/PicoOSPlatform.ts:69 · packages/core/src/platform-adapter/vision-os/VisionOSPlatform.ts:41 — 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/core/src/platform-adapter/pico-os/PicoOSPlatform.ts:69
packages/react/src/reality/components/BoxEntity.tsx:8 · packages/react/src/reality/components/PlaneEntity.tsx:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/react/src/reality/components/BoxEntity.tsx:8
packages/react/src/reality/components/ConeEntity.tsx:14 · packages/react/src/reality/components/CylinderEntity.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/react/src/reality/components/ConeEntity.tsx:14
apps/spatial-next-eager-min/app/server-only-util/page.tsx:19 · apps/spatial-next-min/app/server-only-util/page.tsx:37 — 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. — apps/spatial-next-eager-min/app/server-only-util/page.tsx:19
packages/cli/src/lib/xcode/xcodebuild.ts:14 · packages/cli/src/lib/xcode/xcodebuild.ts:29 — 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/cli/src/lib/xcode/xcodebuild.ts:14
packages/react/src/reality/hooks/useEntityRef.tsx:86 · packages/react/src/reality/hooks/useEntityRef.tsx:101 — 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/react/src/reality/hooks/useEntityRef.tsx:86
packages/react/src/spatialized-container/SpatializedContainer.tsx:162 · packages/react/src/spatialized-container/SpatializedContainer.tsx:220 — 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/react/src/spatialized-container/SpatializedContainer.tsx:162
packages/cli/src/lib/resource/load.ts:25 · packages/cli/src/lib/resource/load.ts:89 — 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/cli/src/lib/resource/load.ts:25
packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:60 · packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:72 — 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/react/src/spatialized-container/hooks/useSpatialEvents.ts:60
apps/spatial-rspack-min/src/main.tsx:6 · apps/spatial-vite-min/src/main.tsx:7 — 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. — apps/spatial-rspack-min/src/main.tsx:6
REDACTED:57 · REDACTED:88 — the two spans are one implementation copied and then locally edited — 52 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. — REDACTED:57
packages/core/src/runtime/capability-data.ts:60 · packages/core/src/runtime/capability-data.ts:78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/core/src/runtime/capability-data.ts:60
packages/cli/src/lib/pwa/config.ts:41 · packages/cli/src/lib/pwa/config.ts:78 — 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/cli/src/lib/pwa/config.ts:41
packages/react/src/ornament/Ornament.tsx:167 · packages/react/src/reality/components/AttachmentEntity.tsx:87 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/react/src/ornament/Ornament.tsx:167
packages/react/src/inspector/WebSpatialInspector.tsx:123 · packages/react/src/inspector/sceneGraph.ts:98 — 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/react/src/inspector/WebSpatialInspector.tsx:123
packages/cli/src/lib/utils/sceneUtils.ts:128 · packages/cli/src/lib/utils/sceneUtils.ts:143 — 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/cli/src/lib/utils/sceneUtils.ts:128
packages/core/src/motion/compute/normalize.ts:48 · packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:208 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/motion/compute/normalize.ts:48
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 · 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.
classifyTopLevelStatement has cyclomatic complexity 52 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/__tests__/default-entry-side-effects.test.ts:305
isPureExpression has cyclomatic complexity 49 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/__tests__/default-entry-side-effects.test.ts:94
get has cyclomatic complexity 48 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — packages/react/src/reality/hooks/useEntityEvent.tsx:16, packages/react/src/reality/hooks/useRealityEvents.tsx:19
get has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:50
EntityGestureCoordinates has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/test-server/src/pages/reality/entityGestureCoordinates.tsx:56
(anonymous) has cyclomatic complexity 26 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tests/autoTest/src/WebSpatial.ts:100
updateSpatializedElementProperties has cyclomatic complexity 25 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — tests/autoTest/src/model/SpatialScene.ts:508
buildFrames has cyclomatic complexity 24 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:223
PerfComparisonPage has cyclomatic complexity 24 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:220
validateCommonConfig has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:125
collectStaticGraph has cyclomatic complexity 22 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/__tests__/default-entry-side-effects.test.ts:500
checkIcons has cyclomatic complexity 21 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/lib/pwa/validate.ts:69
configStartUrl has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/lib/pwa/config.ts:29
desugarTimelineConfig has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/motion/compute/normalize.ts:144
replaceToSpatialPrimitiveType has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react/src/jsx/jsx-shared.ts:101
supports has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×3) — packages/core/src/runtime/supports.ts:70, packages/core/src/runtime/supports.ts:74, packages/core/src/runtime/supports.ts:75
valuesToMotionStyle has cyclomatic complexity 19 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/react/src/spatialized-container/motion/style.ts:5
(anonymous) has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/SpatializedStatic3DElement.ts:55
configMainScene has cyclomatic complexity 17 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/cli/src/lib/pwa/config.ts:147
formatSceneConfig has cyclomatic complexity 17 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/scene-polyfill.ts:545
collectTopLevelLocals has cyclomatic complexity 17 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/react/src/__tests__/default-entry-side-effects.test.ts:218
onReceiveEvent 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/core/src/motion/AnimationObject.ts:137
fmtValues has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/test-server/src/pages/spatial-element-motion/shared.tsx:22
formatToNumber has cyclomatic complexity 16 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. (×2) — packages/cli/src/lib/utils/sceneUtils.ts:68, packages/core/src/scene-polyfill.ts:499
WebSpatialInspector has cyclomatic complexity 16 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/react/src/inspector/WebSpatialInspector.tsx:687
normalizeOrnamentOptions has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/autoTest/src/model/Ornament.ts:86
updateBuildProperty has cyclomatic complexity 15 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/cli/src/lib/xcode/xcodeproject.ts:131
buildApp 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. — tests/marginal-delta-vite/marginal-delta.test.ts:96
getPWAManifest has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/scene-polyfill.ts:410
RealityGestures 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. — apps/test-server/src/pages/reality/gestures.tsx:22
InspectorTreeNode 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. — packages/react/src/inspector/WebSpatialInspector.tsx:222
CSSApiTest 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. — tests/autoTest/src/testApp/CssAPITest/cssapi.tsx:45
validateNormalizedMotionConfig has cyclomatic complexity 15 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/core/src/motion/compute/validate.ts:41
syncStyleSheetRulesToChild 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/react/src/utils/windowStyleSync.ts:189
validateTrack has cyclomatic complexity 14 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/core/src/motion/compute/validate.ts:85
(anonymous) has cyclomatic complexity 14 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. — tests/autoTest/tests/cssApi.test.ts:1407
Do you agree with this assessment?
R3 · Large Files7.7 / 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/react/src/inspector/WebSpatialInspector.tsx has 1047 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/inspector/WebSpatialInspector.tsx:1
packages/core/src/JSBCommand.ts has 828 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/JSBCommand.ts:1
apps/test-server/src/pages/jsapi-refresh-validation/index.tsx has 788 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/jsapi-refresh-validation/index.tsx:1
apps/test-server/src/pages/reality/attachments.tsx has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/reality/attachments.tsx:1
packages/react/src/utils/windowStyleSync.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/react/src/utils/windowStyleSync.ts:1
packages/core/src/scene-polyfill.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/scene-polyfill.ts:1
apps/test-server/src/pages/page-properties-corner/index.tsx has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/page-properties-corner/index.tsx:1
apps/test-server/src/pages/runtime-capabilities/index.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/runtime-capabilities/index.tsx:1
apps/test-server/src/pages/transform-verify/index.tsx has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/transform-verify/index.tsx:1
apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx:1
packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts has 525 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts:1
apps/test-server/index.tsx has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/index.tsx:1
REDACTED has 493 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/core/src/motion/entity/EntityAnimationObject.ts has 485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/motion/entity/EntityAnimationObject.ts:1
apps/test-server/src/pages/static-3d-model/index.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/static-3d-model/index.tsx:1
apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx:1
apps/test-server/src/pages/reality/texturedUnlitBox.tsx has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/reality/texturedUnlitBox.tsx:1
apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx:1
apps/test-server/src/pages/ornament-test/index.tsx has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/ornament-test/index.tsx:1
apps/test-server/src/pages/spatial-content-ready-three/index.tsx has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/spatial-content-ready-three/index.tsx:1
apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx has 448 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx:1
apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx has 437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:1
packages/react/src/spatialized-container/hooks/useDomProxy.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/spatialized-container/hooks/useDomProxy.ts:1
packages/core/src/types/types.ts has 431 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/types/types.ts:1
packages/core/src/SpatializedStatic3DElement.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/SpatializedStatic3DElement.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 Coverage8.6 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×35) — packages/cli/src/lib/utils/messages.ts:1, apps/spatial-vite-min/src/xr-monitor-demo.tsx:1, apps/spatial-vite-min/src/spatial-app.tsx: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.
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.
4 file(s) (~337 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/marginal-delta-vite
Unreachable from the 224 application, 34 tooling and 297 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 (224 application, 34 tooling, 297 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 (×6) — packages/cli/src/lib/utils/messages.ts, REDACTED, packages/react/src/spatialized-container/motion/useAnimation.typecheck.ts, …
Nothing imports this binding — it is safe to review for removal. (×3) — packages/cli/src/lib/utils/sceneUtils.ts:51, packages/cli/src/lib/utils/sceneUtils.ts:114, packages/react/src/jsx/jsx-namespace.ts:72
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/react/src/reality/context/index.tsx, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/react/src/reality/context/index.tsx in the same commit, or the barrel will import a name that no longer exists. — packages/react/src/reality/context/AttachmentContext.tsx:67
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — tests/autoTest/src/webview/ProtocolHandlerManager.ts:12
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 apps/spatial-remix-min/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) — apps/spatial-remix-min/package.json:18, apps/spatial-remix-min/package.json:22
Declared in apps/test-server/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. (×9) — apps/test-server/package.json:19, apps/test-server/package.json:26, apps/test-server/package.json:63, …
Declared in packages/cli/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. (×5) — packages/cli/package.json:50, packages/cli/package.json:54, packages/cli/package.json:56, …
Declared in packages/react/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/react/package.json:99, packages/react/package.json:100, packages/react/package.json:107
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/core/src/JSBCommand.ts → packages/core/src/SpatialObject.ts → packages/core/src/JSBCommand.ts (one verified cycle inside a mutually-dependent group of 29 files) — packages/core/src/JSBCommand.ts:7
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — apps/test-server/vercel.json:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
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.3 / 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.
`normalizeSpatialSceneInspect` is exported, takes a document from its caller (line 239) and hands it to `sortNodeTree`, which calls itself at line 121 (`sortNodeTree`) with a piece of `node` — and nowhere in `sortNodeTree` 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 `sortNodeTree` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/react/src/inspector/sceneGraph.ts:121
`normalizeSpatialSceneInspect` is exported, takes a document from its caller (line 239) and hands it to `countNodes`, which calls itself at line 234 (`countNodes`) with a piece of `node` — and nowhere in `countNodes` 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 `countNodes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/react/src/inspector/sceneGraph.ts:234
`checkManifest` is exported, takes a document from its caller (line 87) and hands it to `compareObjects`, which calls itself at line 126 (`this.compareObjects`) with a piece of `obj1` — and nowhere in `compareObjects` 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 `compareObjects` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/cli/src/lib/utils/history.ts:126
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`getPWAManifest` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/core/src/scene-polyfill.ts:410
`transferBlob` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/core/src/blob/blobTransfer.ts:15
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.3 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`document.baseURI` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — packages/core/src/Ornament.ts:268, packages/core/src/SpatializedElementCreator.ts:19
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?
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.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift:222
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. (×5) — packages/react/src/utils/windowStyleSync.ts:107, packages/react/src/utils/windowStyleSync.ts:178, packages/react/src/jsx/primitive-marker.ts:41, …
`.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. (×4) — packages/react/src/spatialized-container/motion/AnimationBinding.ts:230, packages/react/src/reality/utils/ResourceRegistry.ts:102, packages/react/src/reality/hooks/EntityMotionBinding.ts:197, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — packages/core/src/scene-polyfill.ts:431, packages/core/src/scene-polyfill.ts:456
What to do
Swallowed exception (caught, then discarded)
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.
~2.1 `!` null assertions per 1k TypeScript source lines — 59 assertion(s) across the 28173 source line(s) of the 287 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/react/src/utils/windowStyleSync.ts (10), packages/react/src/spatialized-container/context/PortalInstanceContext.ts (6), packages/core/src/motion/entity/EntityAnimationObject.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 4 observation(s) recorded · 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'.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 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 — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. 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
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 dev`) 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: "> npm run testServer / > webspatial-sdk@1.0.0 testServer / > cd apps/test-server/ && npm run dev -- --host / > web-content@0.2.1 dev / > node esbuild.mjs --host / Preparing dist folder... / Assets copied to dist. / HTTP server is running on http://localhost:5173 / esbuild ready! / 🌼 daisyUI 4.12.24 / ├─ ✔︎ 2 themes added https://daisyui.com/docs/themes / ╰─ ★ Star daisyUI on GitHub https://github.com/saadeghi/daisyui / (node:11548) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated / (Use `node --trace-deprecation ...` to show where the warning was created)" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
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.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 219 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Import cycle (3 files) packages/react/src/spatialized-container/StandardSpatializedContainer.tsx:21— packages/react/src/spatialized-container/StandardSpatializedContainer.tsx → packages/react/src/spatialized-container/context/SpatializedContainerContext.ts → packages/react/src/spatialized-container/hooks/useDomProxy.ts → packages/react/src/spatialized-container/StandardSpatializedContainer.tsx (one verified cycle inside a mutually-dependent group of 4 files)
Serious — 408 finding(s)
R4 · Test Coverage· No test reaches this file · ×35
No test reaches this file packages/cli/src/lib/utils/messages.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-vite-min/src/xr-monitor-demo.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-vite-min/src/spatial-app.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-remix-min/app/components/LazySpatialDemo.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/components/LazyDemo.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/components/CapabilityDemo.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-rspack-min/src/App.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/spatialized-container/motion/useAnimation.typecheck.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/app/server-only-util/page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-remix-min/app/root.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/src/lib/cmds/help.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-vite-min/src/lazy-reality-scene.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-remix-min/app/routes/server-ua.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/core/src/types/global.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/app/page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/components/LazyRealityScene.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-remix-min/app/components/LazyRealityScene.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-remix-min/app/routes/home.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-eager-min/app/eager/page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-min/app/layout.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-eager-min/app/layout.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/_shared/webspatial-request.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-eager-min/app/server-only-util/page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/spatial-next-eager-min/app/page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Sync-over-async blocking packages/cli/src/lib/pwa/index.ts:62— `fs.existsSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/pwa/index.ts:66— `fs.existsSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:29— `fs.existsSync` in `moveProjectFrom` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:30— `fs.mkdirSync` in `moveProjectFrom` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:18— `execSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:33— `execSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:47— `fs.existsSync` in `archive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:48— `fs.mkdirSync` in `archive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:53— `execSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:67— `execSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:81— `fs.existsSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodebuild.ts:82— `fs.mkdirSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:106— `fs.writeFileSync` in `modify` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:106— `project.writeSync` in `modify` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:202— `fs.writeFileSync` in `bindIcon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:222— `fs.writeFileSync` in `bindIcon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:231— `fs.writeFileSync` in `bindIcon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/lib/xcode/xcodeproject.ts:390— `fs.writeFileSync` in `modifySwift` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:31— `execSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:50— `execSync` in `uploadPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:68— `execSync` in `uploadApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:165— `execSync` in `shutdownSimulator` 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.
Change coupling: BoxEntity.tsx ↔ ModelEntity.tsx packages/react/src/reality/components/BoxEntity.tsx:1— `packages/react/src/reality/components/BoxEntity.tsx` and `packages/react/src/reality/components/ModelEntity.tsx` 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `17703c20` chore:(EntityRef) share entityRef instance in event and ref; `bec98bb5` let spatailTapEvent return target and currentTarget from entityRef.cu…; `87d8f35d` expose userData{id,name} from entity — run `git show` on any of them.
Change coupling: BoxEntity.tsx ↔ Entity.tsx packages/react/src/reality/components/BoxEntity.tsx:1— `packages/react/src/reality/components/BoxEntity.tsx` and `packages/react/src/reality/components/Entity.tsx` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `17703c20` chore:(EntityRef) share entityRef instance in event and ref; `bec98bb5` let spatailTapEvent return target and currentTarget from entityRef.cu…; `87d8f35d` expose userData{id,name} from entity — run `git show` on any of them.
Change coupling: UnlitMaterial.tsx ↔ ResourceRegistry.ts packages/react/src/reality/components/UnlitMaterial.tsx:1— `packages/react/src/reality/components/UnlitMaterial.tsx` and `packages/react/src/reality/utils/ResourceRegistry.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1f4d52cc` fix non-exist texture id to unlitmaterial; `118f59e3` fix(react): fallback unlit material when texture id is missing; `685b545d` add changeset — run `git show` on any of them.
Change coupling: JSBCommand.ts ↔ SpatialSession.ts packages/core/src/JSBCommand.ts:1— `packages/core/src/JSBCommand.ts` and `packages/core/src/SpatialSession.ts` change together 65% of the time (15 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `9801a071` feat: add lazy loading support to Model (#1192); `40350a3c` feat: add PBRMaterial with emissive support for visionOS; `d6da4111` add textures — run `git show` on any of them.
Change coupling: WebSpatialApp.swift ↔ SceneHandlerUIView.swift packages/visionOS/web-spatial/WebSpatialApp.swift:1— `packages/visionOS/web-spatial/WebSpatialApp.swift` and `packages/visionOS/web-spatial/view/SceneHandlerUIView.swift` change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `491dff33` fix: change sceneid to scene instance; `2be1dc17` fix: revert window scene resize to requestGeometryUpdate; `f5683c06` native impl for volume feature without 3 param — run `git show` on any of them.
Change coupling: index.tsx ↔ WebMsgCommand.ts apps/test-server/src/pages/spatial-converter/index.tsx:1— `apps/test-server/src/pages/spatial-converter/index.tsx` and `packages/core/src/WebMsgCommand.ts` change together 57% of the time (13 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `0def1ef7` Remove deprecated spatial measurement APIs; `fc41f55d` adjust spatial drag implementation for avp (at that commit the file was still `apps/test-server/src/spatial-converter/index.tsx`); `e949a3de` support model onLoad (at that commit the file was still `apps/test-server/src/spatial-converter/index.tsx`) — run `git show` on any of them.
Change coupling: jsapi.ts ↔ JSBCommand.swift apps/test-server/src/pages/jsapi-test/jsapi.ts:1— `apps/test-server/src/pages/jsapi-test/jsapi.ts` and `packages/visionOS/web-spatial/JSBCommand.swift` change together 56% of the time (14 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `810a1804` expose spatializedElement enableGesture property (at that commit the file was still `apps/test-server/src/jsapi-test/jsapi.ts`); `eaebcd77` support spatialdiv (at that commit the files were still `apps/test-server/src/jsapi-test/jsapi.ts` and `packages/visionOS/web-spatial/refactor/JSBCommand.swift`); `43c89d8f` make SpatialSceneContentView work when multiple SpatializedElement ch… (at that commit the files were still `apps/test-server/src/jsapi-test/jsapi.ts` and `packages/visionOS/web-spatial/refactor/JSBCommand.swift`) — run `git show` on any of them.
Change coupling: useAnimation.ts ↔ useBindSpatializedMotion.ts packages/react/src/spatialized-container/motion/useAnimation.ts:1— `packages/react/src/spatialized-container/motion/useAnimation.ts` and `packages/react/src/spatialized-container/motion/useBindSpatializedMotion.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `bec1bf70` move suppressing logic from react-sdk into native; `678b6ea6` refactor; `69f65f5e` fix spatialdiv and react stop not persist transform on native side — run `git show` on any of them.
Change coupling: JSBCommand.ts ↔ VisionOSPlatform.ts packages/core/src/JSBCommand.ts:1— `packages/core/src/JSBCommand.ts` and `packages/core/src/platform-adapter/vision-os/VisionOSPlatform.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `72fe377c` chore: executeSync should return WebSpatialProtocolResult (at that commit the files were still `packages/core/src/refactor/JSBCommand.ts` and `packages/core/src/refactor/platform-adapter/vision-os/VisionOSPlatform.ts`); `88e8d763` fix: add target features back for window.open cmd (at that commit the files were still `packages/core/src/refactor/JSBCommand.ts` and `packages/core/src/refactor/platform-adapter/vision-os/VisionOSPlatform.ts`); `00496ab5` support spatialized2DElement.updateSpatialMaterial (at that commit the files were still `packages/core/src/refactor/JSBCommand.ts` and `packages/core/src/refactor/platform-adapter/vision-os/VisionOSPlatform.ts`) — run `git show` on any of them.
Change coupling: index.tsx ↔ SpatializedStatic3DElement.swift apps/test-server/src/pages/static-3d-model/index.tsx:1— `apps/test-server/src/pages/static-3d-model/index.tsx` and `packages/visionOS/web-spatial/model/SpatializedStatic3DElement.swift` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `9801a071` feat: add lazy loading support to Model (#1192); `550b3fe9` feat: add currentTime property to Model to read and seek animation ti…; `9be9a9f5` feat: add poster attribute to <Model> (#1147) — run `git show` on any of them.
Change coupling: PortalSpatializedContainer.tsx ↔ useSpatialEvents.ts packages/react/src/spatialized-container/PortalSpatializedContainer.tsx:1— `packages/react/src/spatialized-container/PortalSpatializedContainer.tsx` and `packages/react/src/spatialized-container/hooks/useSpatialEvents.ts` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `fc41f55d` adjust spatial drag implementation for avp; `47aed982` support onSpatialMagnifyStart Event; `dbf0f54b` support onRotateStartEvent — run `git show` on any of them.
Change coupling: WebMsgCommand.ts ↔ SpatializedContainer.tsx packages/core/src/WebMsgCommand.ts:1— `packages/core/src/WebMsgCommand.ts` and `packages/react/src/spatialized-container/SpatializedContainer.tsx` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `fc41f55d` adjust spatial drag implementation for avp; `e949a3de` support model onLoad; `47aed982` support onSpatialMagnifyStart Event — run `git show` on any of them.
Change coupling: index.tsx ↔ SpatializedStatic3DElement.ts apps/test-server/src/pages/static-3d-model/index.tsx:1— `apps/test-server/src/pages/static-3d-model/index.tsx` and `packages/core/src/SpatializedStatic3DElement.ts` change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `f9c25021` feat: implement Model boundingBoxCenter and boundingBoxExtents (#1411); `9450ae3f` feat: Model support blob URLs web changes (#1350); `f3a49752` feat: Model add stagemode property web changes (#1285) — run `git show` on any of them.
TodoComment packages/visionOS/web-spatial/webview/SpatialWebViewModel.swift:98— // See TODO in AttachmentManager — async destroy() during SwiftUI teardown — 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/visionOS/web-spatial/view/Spatialized2DElementView.swift:84— // TODO: this should have velocity — 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/visionOS/web-spatial/view/SpatializedStatic3DView.swift:180— // TODO: Use FileManager.temporaryDirectory and FileManager.removeItem for auto cleanup — 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/visionOS/web-spatial/model/dynamic3d/SpatialComponent.swift:92— // TODO(P2): `mesh` is a registered `Geometry` spatial object; clearing the reference does not — 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/visionOS/web-spatial/model/dynamic3d/SpatialModelEntity.swift:39— // TODO(P1): Clearing overrides (`setMaterials([])`) assigns an empty material list here; there is — 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/visionOS/web-spatial/manager/AttachmentManager.swift:42— // TODO: AttachmentManager.remove() dispatches destroy() asynchronously while — 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/visionOS/web-spatial/manager/WKWebViewManager.swift:16— // TODO: get native api instead of using the injected WS_SDK_VERSION placeholder — 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/visionOS/web-spatial/manager/WKWebViewManager.swift:37— // TODO: get native api instead of relying on injected shell/sdk versions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/spatialized-container/SpatializedStatic3DElementContainer.tsx:151— // TODO: Can native side handle null instead of '' — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/reality/components/GeometryEntity.tsx:76— // TODO(P2): Rebuild removes/destroys the model component but not the previous mesh — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/reality/components/ModelEntity.tsx:25— // TODO(P2): Material overrides run async (`Promise.all` + `setMaterials`) with no generation/abort — 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/core/src/JSBCommand.ts:119— // todo: to be used in SpatialEntity — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×12
Swallowed exception (empty catch) packages/react/src/utils/windowStyleSync.ts:107— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/react/src/utils/windowStyleSync.ts:178— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/react/src/spatialized-container/motion/AnimationBinding.ts:230— `.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/react/src/reality/utils/ResourceRegistry.ts:102— `.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/react/src/reality/hooks/EntityMotionBinding.ts:197— `.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/react/src/reality/hooks/EntityMotionBinding.ts:240— `.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/react/src/jsx/primitive-marker.ts:41— 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/core/src/utils.ts:76— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:148— 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.
FunctionTooLong: WebSpatialInspector.WebSpatialInspector packages/react/src/inspector/WebSpatialInspector.tsx:687— FunctionTooLong — WebSpatialInspector runs 344 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 244 over it, 3.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SpatializedContainer.SpatializedContainerBase packages/react/src/spatialized-container/SpatializedContainer.tsx:83— FunctionTooLong — SpatializedContainerBase runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: WebSpatialInspector.Editor packages/react/src/inspector/WebSpatialInspector.tsx:474— FunctionTooLong — Editor runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Ornament.Ornament packages/react/src/ornament/Ornament.tsx:208— FunctionTooLong — Ornament runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: WebSpatialInspector.InspectorTreeNode packages/react/src/inspector/WebSpatialInspector.tsx:222— FunctionTooLong — InspectorTreeNode runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useEntity.useEntity packages/react/src/reality/hooks/useEntity.tsx:25— FunctionTooLong — useEntity runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AttachmentEntity.AttachmentEntity packages/react/src/reality/components/AttachmentEntity.tsx:27— FunctionTooLong — AttachmentEntity runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: xr-monitor-demo.XrMonitorDemo apps/spatial-vite-min/src/xr-monitor-demo.tsx:33— FunctionTooLong — XrMonitorDemo runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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.
Fake-async — async method never awaits packages/cli/src/lib/cmds/help.ts:59— `help` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/lib/cmds/launch.ts:3— `launch` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/lib/cmds/shutdown.ts:3— `shutdown` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:24— `moveProjectFrom` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/lib/xcode/index.ts:19— `upload` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:78— `runWithSimulator` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:107— `runWithHistory` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:159— `shutdownSimulator` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
No assertions: keeps binding methods outside the public opaque animation type packages/react/src/reality/hooks/useEntityAnimation.redesign.test.ts:166— 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: exports the Entity playback error from the experimental entry packages/react/src/reality/hooks/useEntityAnimation.redesign.test.ts:171— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not type removed window scene globals packages/core/src/scene-polyfill.test.ts:302— 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: exports authoring and playback types from the package entry packages/core/src/types/motion/entityMotion.publicApi.test.ts:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: exposes transform-only config, values, and playback controls packages/core/src/motion/entity/entityMotionTypes.test.ts:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keeps Element and Entity playback error contracts independent packages/core/src/motion/entity/entityMotionTypes.test.ts:27— 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.
Deprecated: react-fps apps/test-server/package.json:40— react-fps 1.0.6, declared in apps/test-server/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @types/redux apps/test-server/package.json:57— @types/redux 3.6.0, declared in apps/test-server/package.json, is marked deprecated by its publisher: "This is a stub types definition for Redux (https://github.com/reactjs/redux). Redux provides its own type definitions, so you don't need @types/redux installed!". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint package.json:79— eslint 9.39.5, 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: glob packages/cli/package.json:77— glob 10.5.0, declared in packages/cli/package.json, 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". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @testing-library/jest-dom packages/react/package.json:89— @testing-library/jest-dom 6.10.0, declared in packages/react/package.json, is marked deprecated by its publisher: "Incorrect minor release with breaking changes (Node >=22 and required @testing-library/dom peer). Use 6.9.1 for the 6.x line, or upgrade to 7.0.0.". Replace it with the package or version that message names, or record why this one must stay.
Hotspot: apps/test-server/src/pages/reality/gestures.tsx apps/test-server/src/pages/reality/gestures.tsx:22— apps/test-server/src/pages/reality/gestures.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in gestures.RealityGestures at line 22. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- apps/test-server/src/pages/reality/gestures.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/reality/hooks/useEntity.tsx packages/react/src/reality/hooks/useEntity.tsx:25— packages/react/src/reality/hooks/useEntity.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in useEntity.useEntity at line 25. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/react/src/reality/hooks/useEntity.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/reality/hooks/useSpatialMaterial.tsx packages/react/src/reality/hooks/useSpatialMaterial.tsx:56— packages/react/src/reality/hooks/useSpatialMaterial.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in useSpatialMaterial.useSpatialMaterial at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/react/src/reality/hooks/useSpatialMaterial.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/test-server/src/pages/jsapi-refresh-validation/index.tsx apps/test-server/src/pages/jsapi-refresh-validation/index.tsx:423— apps/test-server/src/pages/jsapi-refresh-validation/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in index.SpatialDivRefreshValidation at line 423. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- apps/test-server/src/pages/jsapi-refresh-validation/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/spatialized-container/motion/AnimationBinding.ts packages/react/src/spatialized-container/motion/AnimationBinding.ts:209— packages/react/src/spatialized-container/motion/AnimationBinding.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in AnimationBinding.ensureAnimationObject at line 209. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/react/src/spatialized-container/motion/AnimationBinding.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.
Duplicated block (16 lines × 2 locations) apps/spatial-next-eager-min/app/eager/page.tsx:21— apps/spatial-next-eager-min/app/eager/page.tsx:21 · apps/spatial-remix-min/app/routes/server-ua.tsx:34 — 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 (16 lines × 2 locations) packages/core/src/motion/AnimationObject.ts:93— packages/core/src/motion/AnimationObject.ts:93 · packages/core/src/motion/entity/EntityAnimationObject.ts:135 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (16 lines × 2 locations) packages/core/src/platform-adapter/pico-os/PicoOSPlatform.ts:69— packages/core/src/platform-adapter/pico-os/PicoOSPlatform.ts:69 · packages/core/src/platform-adapter/vision-os/VisionOSPlatform.ts:41 — 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 (16 lines × 2 locations) packages/react/src/reality/components/BoxEntity.tsx:8— packages/react/src/reality/components/BoxEntity.tsx:8 · packages/react/src/reality/components/PlaneEntity.tsx:8 — 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 (16 lines × 2 locations) packages/react/src/reality/components/ConeEntity.tsx:14— packages/react/src/reality/components/ConeEntity.tsx:14 · packages/react/src/reality/components/CylinderEntity.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Repeated repair: packages/react/src/reality/hooks/EntityMotionBinding.ts packages/react/src/reality/hooks/EntityMotionBinding.ts:202— packages/react/src/reality/hooks/EntityMotionBinding.ts changed 14 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is EntityMotionBinding.createAnimationObject at line 202), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(react): restore declared transform after animation unbind”; “fix(react): avoid duplicate entity motion precedence warnings”; “fix(core): hide entity animation implementation from public entry”; “fix(react): rollback Entity binding after sync creation failure”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/react/src/reality/hooks/EntityMotionBinding.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:135— packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is SpatializedDynamic3DView.orthogonalBasisPreservingReflection at line 135), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(visionos): preserve nested parent rotation axes”; “fix(visionos): preserve mirrored parent rotation axes”; “fix(visionos): report gestures in parent-local coordinates”; “fix(visionos): normalize gesture hit-point coordinates”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift:29— packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is SpatializedStatic3DView.body at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: animation end state for Model (#1416)”; “fix: Model entityTransform shouldn't affect poster (#1373)”; “fix: changing Model source from empty value doesn't re-render (#1339)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 17:10:02 -08:00' --until='2026-11-04 17:10:02 -08:00' --full-history --no-merges -- packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift`: 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.
TooManyMethods: SpatialScene packages/visionOS/web-spatial/model/SpatialScene.swift:83— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× 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: SpatialWebViewModel packages/visionOS/web-spatial/webview/SpatialWebViewModel.swift:13— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× 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: SpatialWebController packages/visionOS/web-spatial/webview/SpatialWebController.swift:4— 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.
FileTooLong: model/SpatialScene.swift packages/visionOS/web-spatial/model/SpatialScene.swift— FileTooLong — 1227 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: SpatialScene (84-1934). The bar is 500 significant lines; this is 727 over it, 2.45× 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: inspector/WebSpatialInspector.tsx packages/react/src/inspector/WebSpatialInspector.tsx— FileTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 426 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/JSBCommand.ts packages/core/src/JSBCommand.ts— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 75 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×3
Edited copy of a member (3 corresponding lines) packages/visionOS/web-spatial/webview/SpatialWebController.swift:33— packages/visionOS/web-spatial/webview/SpatialWebController.swift:33-35 | packages/visionOS/web-spatial/webview/SpatialWebViewModel.swift:161-163 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) packages/visionOS/web-spatial/webview/SpatialWebController.swift:37— packages/visionOS/web-spatial/webview/SpatialWebController.swift:37-39 | packages/visionOS/web-spatial/webview/SpatialWebViewModel.swift:165-167 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1109— packages/visionOS/web-spatial/model/SpatialScene.swift:1109-1111 | packages/visionOS/web-spatial/model/Spatialized2DElement.swift:77-79 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Off the main sequence: @webspatial/platform-visionos — @webspatial/platform-visionos: abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @webspatial/core-sdk — @webspatial/core-sdk: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @webspatial/react-sdk — @webspatial/react-sdk: abstractness 0.04, instability 0.17, distance 0.79 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
P12 · CI test-gate honesty· Workspace package's tests never run by CI · ×3
Workspace package's tests never run by CI packages/core/package.json:33— `packages/core` is a workspace package with 307 test(s) in 29 file(s) (e.g. `packages/core/src/Ornament.test.ts`, `packages/core/src/SpatialObject.destroy.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/react/package.json:52— `packages/react` is a workspace package with 498 test(s) in 56 file(s) (e.g. `packages/react/src/coverage-boost.test.ts`, `packages/react/src/default-entry-public-surface.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI tests/ci-test/package.json:8— `tests/ci-test` is a workspace package with 6 test(s) in 4 file(s) (e.g. `tests/ci-test/test/e2e.test.ts`, `tests/ci-test/test/webspatial-builder.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Duplicated block (14 lines × 2 locations) packages/cli/src/lib/xcode/xcodebuild.ts:14— packages/cli/src/lib/xcode/xcodebuild.ts:14 · packages/cli/src/lib/xcode/xcodebuild.ts:29 — 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/react/src/reality/hooks/useEntityRef.tsx:86— packages/react/src/reality/hooks/useEntityRef.tsx:86 · packages/react/src/reality/hooks/useEntityRef.tsx:101 — 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/react/src/spatialized-container/SpatializedContainer.tsx:162— packages/react/src/spatialized-container/SpatializedContainer.tsx:162 · packages/react/src/spatialized-container/SpatializedContainer.tsx:220 — 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.
Complex function supports (cyclomatic 20, cognitive 22) packages/core/src/runtime/supports.ts:70— supports has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function supports (cyclomatic 20, cognitive 22) packages/core/src/runtime/supports.ts:74— supports has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function supports (cyclomatic 20, cognitive 22) packages/core/src/runtime/supports.ts:75— supports has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap packages/react/src/inspector/sceneGraph.ts:121— `normalizeSpatialSceneInspect` is exported, takes a document from its caller (line 239) and hands it to `sortNodeTree`, which calls itself at line 121 (`sortNodeTree`) with a piece of `node` — and nowhere in `sortNodeTree` 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 `sortNodeTree` 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/react/src/inspector/sceneGraph.ts:234— `normalizeSpatialSceneInspect` is exported, takes a document from its caller (line 239) and hands it to `countNodes`, which calls itself at line 234 (`countNodes`) with a piece of `node` — and nowhere in `countNodes` 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 `countNodes` 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/cli/src/lib/utils/history.ts:126— `checkManifest` is exported, takes a document from its caller (line 87) and hands it to `compareObjects`, which calls itself at line 126 (`this.compareObjects`) with a piece of `obj1` — and nowhere in `compareObjects` 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 `compareObjects` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Swallowed exception (caught, then discarded) packages/visionOS/web-spatial/view/SpatializedStatic3DView.swift:222— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/core/src/scene-polyfill.ts:431— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/core/src/scene-polyfill.ts:456— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
MethodTooLong: SpatialContainerRefProxy.installSpatialRefBehavior packages/react/src/spatialized-container/hooks/useDomProxy.ts:205— MethodTooLong — installSpatialRefBehavior runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: SpatialNavView.body packages/visionOS/web-spatial/view/SpatialNavView.swift:137— MethodTooLong — body runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change-coupling hub: SpatialScene.swift → index.tsx, SpatializedElementCreator.ts, VisionOSPlatform.ts packages/visionOS/web-spatial/model/SpatialScene.swift— `packages/visionOS/web-spatial/model/SpatialScene.swift` changes together with 3 other files — `apps/test-server/src/pages/jsapi-test/index.tsx`, `packages/core/src/SpatializedElementCreator.ts`, `packages/core/src/platform-adapter/vision-os/VisionOSPlatform.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: AttachmentManager.swift → JSBCommand.ts, AttachmentEntity.tsx, JSBCommand.swift, SpatializedDynamic3DView.swift packages/visionOS/web-spatial/manager/AttachmentManager.swift— `packages/visionOS/web-spatial/manager/AttachmentManager.swift` changes together with 4 other files — `packages/core/src/JSBCommand.ts`, `packages/react/src/reality/components/AttachmentEntity.tsx`, `packages/visionOS/web-spatial/JSBCommand.swift`, `packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:73— packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:73-86 | packages/visionOS/web-spatial/view/SpatializedElementView.swift:41-54 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) packages/visionOS/web-spatial/SpatialObject.swift:106— packages/visionOS/web-spatial/SpatialObject.swift:106-121 | packages/visionOS/web-spatial/model/dynamic3d/SpatialEntity.swift:269-282 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) packages/visionOS/web-spatial/model/SpatializedElement.swift:97— packages/visionOS/web-spatial/model/SpatializedElement.swift:97-104 | packages/visionOS/web-spatial/view/SpatializedElementView.swift:120-127 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) packages/visionOS/web-spatial/SpatialObject.swift:79— packages/visionOS/web-spatial/SpatialObject.swift:79-86 | packages/visionOS/web-spatial/model/dynamic3d/SpatialEntity.swift:97-105 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:34— packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:34-43 | packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:88-107 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) packages/visionOS/web-spatial/model/dynamic3d/SpatialTextureResource.swift:17— packages/visionOS/web-spatial/model/dynamic3d/SpatialTextureResource.swift:17-26 | packages/visionOS/web-spatial/model/dynamic3d/SpatialTextureResource.swift:28-38 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (7 lines × 2) packages/visionOS/web-spatial/model/OrnamentElement.swift:175— packages/visionOS/web-spatial/model/OrnamentElement.swift:175-181 | packages/visionOS/web-spatial/model/OrnamentElement.swift:206-212 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/model/OrnamentElement.swift:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) packages/visionOS/web-spatial/model/SpatialScene.swift:1638— packages/visionOS/web-spatial/model/SpatialScene.swift:1638-1644 | packages/visionOS/web-spatial/model/SpatialScene.swift:1688-1694 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/model/SpatialScene.swift:1638` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `UpdateEntityAnimationCommand` in one and `SetEntityAnimationCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (34 lines × 2 locations) apps/spatial-next-eager-min/app/layout.tsx:7— apps/spatial-next-eager-min/app/layout.tsx:7 · apps/spatial-next-min/app/layout.tsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) packages/core/src/JSBCommand.ts:576— packages/core/src/JSBCommand.ts:576 · packages/core/src/JSBCommand.ts:613 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) packages/core/src/JSBCommand.ts:204— packages/core/src/JSBCommand.ts:204 · packages/core/src/JSBCommand.ts:241 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (25 lines × 2 locations) packages/core/src/utils.ts:13— packages/core/src/utils.ts:13 · packages/react/src/spatialized-container/utils.ts:94 — 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 (17 lines × 2 locations) REDACTED:17— REDACTED:17 · REDACTED:54 — 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/react/src/spatialized-container/StandardSpatializedContainer.tsx:44— packages/react/src/spatialized-container/StandardSpatializedContainer.tsx:44 · packages/react/src/spatialized-container/TransformVisibilityTaskContainer.tsx:32 — 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 (11 lines × 2 locations) packages/cli/src/lib/resource/load.ts:25— packages/cli/src/lib/resource/load.ts:25 · packages/cli/src/lib/resource/load.ts:89 — 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 (11 lines × 2 locations) packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:60— packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:60 · packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:72 — 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 (10 lines × 2 locations) apps/spatial-rspack-min/src/main.tsx:6— apps/spatial-rspack-min/src/main.tsx:6 · apps/spatial-vite-min/src/main.tsx:7 — 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 (10 lines × 2 locations) packages/core/src/runtime/capability-data.ts:60— packages/core/src/runtime/capability-data.ts:60 · packages/core/src/runtime/capability-data.ts:78 — 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.
R2 · Cyclomatic Complexity· Complex function get (cyclomatic 48, cognitive 62) · ×2
Complex function get (cyclomatic 48, cognitive 62) packages/react/src/reality/hooks/useEntityEvent.tsx:16— get has cyclomatic complexity 48 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function get (cyclomatic 48, cognitive 62) packages/react/src/reality/hooks/useRealityEvents.tsx:19— get has cyclomatic complexity 48 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function formatToNumber (cyclomatic 16, cognitive 22) packages/cli/src/lib/utils/sceneUtils.ts:68— formatToNumber has cyclomatic complexity 16 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 formatToNumber (cyclomatic 16, cognitive 22) packages/core/src/scene-polyfill.ts:499— formatToNumber has cyclomatic complexity 16 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: getPWAManifest packages/core/src/scene-polyfill.ts:410— `getPWAManifest` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: transferBlob packages/core/src/blob/blobTransfer.ts:15— `transferBlob` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped packages/core/src/Ornament.ts:268— `document.baseURI` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped packages/core/src/SpatializedElementCreator.ts:19— `document.baseURI` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/visionOS/web-spatial/static-web/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard apps/spatial-vite-min/src/xr-monitor-demo.tsx:99— <div> moves — its inline style sets `transition: width 0.2s ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Focus outline removed inline packages/react/src/inspector/WebSpatialInspector.tsx:449— <input> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement apps/test-server/public/css/xterm.css:48— `.xterm.focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
WebSpatialInspector.WebSpatialInspector (cyclomatic 36) packages/react/src/inspector/WebSpatialInspector.tsx:687— WebSpatialInspector.WebSpatialInspector has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 15 of the 36 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 721, 746, 797, …). 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.
useEntityEvent.createEventProxy (cyclomatic 34) packages/react/src/reality/hooks/useEntityEvent.tsx:14— useEntityEvent.createEventProxy has cyclomatic complexity 34 (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.
useRealityEvents.createEventProxy (cyclomatic 34) packages/react/src/reality/hooks/useRealityEvents.tsx:17— useRealityEvents.createEventProxy has cyclomatic complexity 34 (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.
useSpatialEvents.createEventProxy (cyclomatic 26) packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:29— useSpatialEvents.createEventProxy has cyclomatic complexity 26 (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.
useEntity.useEntity (cyclomatic 25) packages/react/src/reality/hooks/useEntity.tsx:25— useEntity.useEntity has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 63, 116, 146, …). 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.
validate.checkIcons (cyclomatic 24) packages/cli/src/lib/pwa/validate.ts:69— validate.checkIcons has cyclomatic complexity 24 (threshold 15). Of this number, 21 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.
normalizeEntityMotionConfig.buildFrames (cyclomatic 24) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:223— normalizeEntityMotionConfig.buildFrames has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
normalize.desugarTimelineConfig (cyclomatic 23) packages/core/src/motion/compute/normalize.ts:144— normalize.desugarTimelineConfig has cyclomatic complexity 23 (threshold 15). Of this number, 18 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.
SpatialContainerRefProxy.installSpatialRefBehavior (cyclomatic 23) packages/react/src/spatialized-container/hooks/useDomProxy.ts:205— SpatialContainerRefProxy.installSpatialRefBehavior has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Ornament.Ornament (cyclomatic 23) packages/react/src/ornament/Ornament.tsx:208— Ornament.Ornament has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 290, 271, 254, …). 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.
SpatialScene.updateSpatializedElementProperties (cyclomatic 23) packages/visionOS/web-spatial/model/SpatialScene.swift:939— SpatialScene.updateSpatializedElementProperties has cyclomatic complexity 23 (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.
EntityMotionTimelineCompiler.parse (cyclomatic 23) packages/visionOS/web-spatial/model/entity-motion/EntityMotionTimelineCompiler.swift:157— EntityMotionTimelineCompiler.parse has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Dynamic3DManager.createGeometry (cyclomatic 22) packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:110— Dynamic3DManager.createGeometry 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.
normalizeEntityMotionConfig.validateCommonConfig (cyclomatic 21) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:125— normalizeEntityMotionConfig.validateCommonConfig 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.
supports.supports (cyclomatic 20) packages/core/src/runtime/supports.ts:75— supports.supports has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
spatial-window-polyfill.hijackDocumentElementStyle (cyclomatic 20) packages/core/src/spatial-window-polyfill.ts:77— spatial-window-polyfill.hijackDocumentElementStyle has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 80, 126, 118). 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.
jsx-shared.replaceToSpatialPrimitiveType (cyclomatic 20) packages/react/src/jsx/jsx-shared.ts:101— jsx-shared.replaceToSpatialPrimitiveType has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useSpatialMaterial.useSpatialMaterial (cyclomatic 20) packages/react/src/reality/hooks/useSpatialMaterial.tsx:56— useSpatialMaterial.useSpatialMaterial has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 115, 80, 111, …). 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.
config.configStartUrl (cyclomatic 19) packages/cli/src/lib/pwa/config.ts:29— config.configStartUrl 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.
config.configMainScene (cyclomatic 17) packages/cli/src/lib/pwa/config.ts:147— config.configMainScene 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.
scene-polyfill.formatSceneConfig (cyclomatic 17) packages/core/src/scene-polyfill.ts:545— scene-polyfill.formatSceneConfig 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.
AnimationBinding.ensureAnimationObject (cyclomatic 17) packages/react/src/spatialized-container/motion/AnimationBinding.ts:209— AnimationBinding.ensureAnimationObject has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 223, 255). 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.
sceneUtils.formatToNumber (cyclomatic 16) packages/cli/src/lib/utils/sceneUtils.ts:68— sceneUtils.formatToNumber 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.
scene-polyfill.formatToNumber (cyclomatic 16) packages/core/src/scene-polyfill.ts:499— scene-polyfill.formatToNumber 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.
WebSpatialInspector.InspectorTreeNode (cyclomatic 16) packages/react/src/inspector/WebSpatialInspector.tsx:222— WebSpatialInspector.InspectorTreeNode has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
style.valuesToMotionStyle (cyclomatic 16) packages/react/src/spatialized-container/motion/style.ts:5— style.valuesToMotionStyle 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.
SpatialScene.onUpdateSpatializedStatic3DElementProperties (cyclomatic 16) packages/visionOS/web-spatial/model/SpatialScene.swift:795— SpatialScene.onUpdateSpatializedStatic3DElementProperties 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.
SpatialNavView.body (cyclomatic 16) packages/visionOS/web-spatial/view/SpatialNavView.swift:137— SpatialNavView.body 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.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×1
One package at two majors across the workspace: react-router-dom — `react-router-dom` is maintained at 2 different major versions inside this one repository — major 6 in apps/test-server/package.json; major 7 in apps/spatial-remix-min/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
HackComment packages/visionOS/web-spatial/model/SpatialScene.swift:320— // hack to fix windowGroup floating, we need it stay in place of loadingView — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
FixmeComment packages/cli/src/lib/cmds/build.ts:54— // fixme: the cache not invalidate when npm version change — 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.
WebSpatialInspector.WebSpatialInspector (cognitive 55) packages/react/src/inspector/WebSpatialInspector.tsx:687— WebSpatialInspector.WebSpatialInspector has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 16 (28 pts), if/else 15 (20 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 18). Of this number, 22 points are the body's own statements and 33 belong to 12 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useEntityEvent.createEventProxy (cognitive 48) packages/react/src/reality/hooks/useEntityEvent.tsx:14— useEntityEvent.createEventProxy has cognitive complexity 48 (threshold 15). Drivers by points: if/else 29 (44 pts), boolean chains 3, ternaries 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useRealityEvents.createEventProxy (cognitive 48) packages/react/src/reality/hooks/useRealityEvents.tsx:17— useRealityEvents.createEventProxy has cognitive complexity 48 (threshold 15). Drivers by points: if/else 29 (44 pts), boolean chains 3, ternaries 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate.checkIcons (cognitive 40) packages/cli/src/lib/pwa/validate.ts:69— validate.checkIcons has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (34 pts), boolean chains 5, loops 1 (nesting depth added 18). Of this number, 32 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.
normalize.desugarTimelineConfig (cognitive 32) packages/core/src/motion/compute/normalize.ts:144— normalize.desugarTimelineConfig has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 6, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 11). Of this number, 28 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.
Dynamic3DManager.createGeometry (cognitive 32) packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:110— Dynamic3DManager.createGeometry has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (31 pts), match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scene-polyfill.formatSceneConfig (cognitive 30) packages/core/src/scene-polyfill.ts:545— scene-polyfill.formatSceneConfig has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (26 pts), loops 2 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpatialContainerRefProxy.installSpatialRefBehavior (cognitive 30) packages/react/src/spatialized-container/hooks/useDomProxy.ts:205— SpatialContainerRefProxy.installSpatialRefBehavior has cognitive complexity 30 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). Of this number, 18 points are the body's own statements and 12 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
style.valuesToMotionStyle (cognitive 30) packages/react/src/spatialized-container/motion/style.ts:5— style.valuesToMotionStyle has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (28 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.
normalizeEntityMotionConfig.buildFrames (cognitive 29) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:223— normalizeEntityMotionConfig.buildFrames has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 9, ternaries 4 (9 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useEntity.useEntity (cognitive 28) packages/react/src/reality/hooks/useEntity.tsx:25— useEntity.useEntity has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (17 pts), ternaries 3 (6 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 116, 63, 146, …). 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.
config.configStartUrl (cognitive 27) packages/cli/src/lib/pwa/config.ts:29— config.configStartUrl has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 6 (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.
config.configMainScene (cognitive 27) packages/cli/src/lib/pwa/config.ts:147— config.configMainScene has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (21 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalizeEntityMotionConfig.validateCommonConfig (cognitive 27) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:125— normalizeEntityMotionConfig.validateCommonConfig has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, loops 3 (4 pts), ternaries 3 (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.
EntityMotionTimelineCompiler.parse (cognitive 26) packages/visionOS/web-spatial/model/entity-motion/EntityMotionTimelineCompiler.swift:157— EntityMotionTimelineCompiler.parse has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 16, if/else 4 (7 pts), loops 2 (3 pts) (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
windowStyleSync.getSyncTiming (cognitive 25) packages/react/src/utils/windowStyleSync.ts:460— windowStyleSync.getSyncTiming has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useSpatialEvents.createEventProxy (cognitive 25) packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:29— useSpatialEvents.createEventProxy has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14, boolean chains 11. 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.
jsx-shared.replaceToSpatialPrimitiveType (cognitive 24) packages/react/src/jsx/jsx-shared.ts:101— jsx-shared.replaceToSpatialPrimitiveType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 7 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
supports.supports (cognitive 23) packages/core/src/runtime/supports.ts:75— supports.supports has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (18 pts), ternaries 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SpatialScene.updateSpatializedElementProperties (cognitive 23) packages/visionOS/web-spatial/model/SpatialScene.swift:939— SpatialScene.updateSpatializedElementProperties has cognitive complexity 23 (threshold 15). Drivers by points: if/else 22 (23 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sceneUtils.formatToNumber (cognitive 22) packages/cli/src/lib/utils/sceneUtils.ts:68— sceneUtils.formatToNumber has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
scene-polyfill.formatToNumber (cognitive 22) packages/core/src/scene-polyfill.ts:499— scene-polyfill.formatToNumber has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Ornament.Ornament (cognitive 22) packages/react/src/ornament/Ornament.tsx:208— Ornament.Ornament has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 3, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 290, 271, 254, …). 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.
JSBManager.handlerMessage (cognitive 22) packages/visionOS/web-spatial/manager/JSBManager.swift:95— JSBManager.handlerMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, match/switch 1 (2 pts), error handling 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.
SpatializedDynamic3DView.body (cognitive 22) packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:214— SpatializedDynamic3DView.body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SceneManager.getPWAManifest (cognitive 20) packages/core/src/scene-polyfill.ts:410— SceneManager.getPWAManifest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 5 (8 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useSpatialMaterial.useSpatialMaterial (cognitive 20) packages/react/src/reality/hooks/useSpatialMaterial.tsx:56— useSpatialMaterial.useSpatialMaterial has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3, error handling 2 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 5 function literals inside it that branch (lines 115, 80, 68, …). 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.
SpatialNavView.body (cognitive 20) packages/visionOS/web-spatial/view/SpatialNavView.swift:137— SpatialNavView.body has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 4, if/else 4 (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.
check.checkBuildParams (cognitive 19) packages/cli/src/lib/cmds/check.ts:2— check.checkBuildParams has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, error handling 1 (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.
SceneManager.open (cognitive 19) packages/core/src/scene-polyfill.ts:287— SceneManager.open has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, ternaries 1 (nesting depth added 8). Of this number, 15 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.
SpatializedContainer.SpatializedContainerBase (cognitive 19) packages/react/src/spatialized-container/SpatializedContainer.tsx:83— SpatializedContainer.SpatializedContainerBase has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 6). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CliHistory.compareObjects (cognitive 18) packages/cli/src/lib/utils/history.ts:102— CliHistory.compareObjects has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalizeEntityMotionConfig.collectPatch (cognitive 18) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:72— normalizeEntityMotionConfig.collectPatch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 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.
WebSpatialInspector.InspectorTreeNode (cognitive 18) packages/react/src/inspector/WebSpatialInspector.tsx:222— WebSpatialInspector.InspectorTreeNode has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 13 (16 pts), boolean chains 1, if/else 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
SpatialScene.onUpdateSpatializedStatic3DElementProperties (cognitive 18) packages/visionOS/web-spatial/model/SpatialScene.swift:795— SpatialScene.onUpdateSpatializedStatic3DElementProperties has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
validate.validateTrack (cognitive 17) packages/core/src/motion/compute/validate.ts:85— validate.validateTrack has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
spatial-window-polyfill.hijackDocumentElementStyle (cognitive 17) packages/core/src/spatial-window-polyfill.ts:77— spatial-window-polyfill.hijackDocumentElementStyle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 80, 126, 118). 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.
windowStyleSync.syncStyleSheetRulesToChild (cognitive 17) packages/react/src/utils/windowStyleSync.ts:189— windowStyleSync.syncStyleSheetRulesToChild has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (4 pts), loops 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpatialScene.handleWindowOpenCustom (cognitive 17) packages/visionOS/web-spatial/model/SpatialScene.swift:225— SpatialScene.handleWindowOpenCustom has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PWAGenerator.validate (cognitive 16) packages/cli/src/lib/pwa/index.ts:44— PWAGenerator.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityAnimationObject.getConfirmedValuesError (cognitive 16) packages/core/src/motion/entity/EntityAnimationObject.ts:497— EntityAnimationObject.getConfirmedValuesError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: SpatialScene packages/visionOS/web-spatial/model/SpatialScene.swift:83— ClassTooLong — 1170 significant lines (blank, comment-only and punctuation-only lines excluded), 97 methods. The bar is 400 significant lines; this is 770 over it, 2.93× 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.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1735— packages/visionOS/web-spatial/model/SpatialScene.swift:1735-1757 | packages/visionOS/web-spatial/model/SpatialScene.swift:1759-1788 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) packages/visionOS/web-spatial/model/OrnamentElement.swift:161— packages/visionOS/web-spatial/model/OrnamentElement.swift:161-188 | packages/visionOS/web-spatial/model/OrnamentElement.swift:190-220 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1636— packages/visionOS/web-spatial/model/SpatialScene.swift:1636-1653 | packages/visionOS/web-spatial/model/SpatialScene.swift:1655-1684 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1434— packages/visionOS/web-spatial/model/SpatialScene.swift:1434-1447 | packages/visionOS/web-spatial/model/SpatialScene.swift:1449-1457 | packages/visionOS/web-spatial/model/SpatialScene.swift:1459-1467 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1279— packages/visionOS/web-spatial/model/SpatialScene.swift:1279-1289 | packages/visionOS/web-spatial/model/SpatialScene.swift:1291-1301 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:58— packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:58-72 | packages/visionOS/web-spatial/model/dynamic3d/SpatialMaterial.swift:124-151 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:180— packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:180-192 | packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:194-208 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1322— packages/visionOS/web-spatial/model/SpatialScene.swift:1322-1331 | packages/visionOS/web-spatial/model/SpatialScene.swift:1333-1342 | packages/visionOS/web-spatial/model/SpatialScene.swift:1344-1353 | packages/visionOS/web-spatial/model/SpatialScene.swift:1392-1401 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) packages/visionOS/web-spatial/model/SpatializedElement.swift:107— packages/visionOS/web-spatial/model/SpatializedElement.swift:107-111 | packages/visionOS/web-spatial/model/SpatializedElement.swift:114-119 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) packages/visionOS/web-spatial/model/SpatialScene.swift:1053— packages/visionOS/web-spatial/model/SpatialScene.swift:1053-1061 | packages/visionOS/web-spatial/model/SpatialScene.swift:1425-1432 | packages/visionOS/web-spatial/model/SpatialScene.swift:1790-1799 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) packages/visionOS/web-spatial/model/OrnamentElement.swift:231— packages/visionOS/web-spatial/model/OrnamentElement.swift:231-237 | packages/visionOS/web-spatial/model/SpatializedDynamic3DElement.swift:39-44 | packages/visionOS/web-spatial/model/SpatializedStatic3DElement.swift:94-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (14–17 lines × 2) packages/visionOS/web-spatial/model/SpatialScene.swift:1737— packages/visionOS/web-spatial/model/SpatialScene.swift:1737-1750 | packages/visionOS/web-spatial/model/SpatialScene.swift:1761-1777 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/model/SpatialScene.swift:1737` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `UpdateUnlitMaterialProperties` in one and `UpdatePBRMaterialProperties` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12–15 lines × 2) packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:138— packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:138-152 | packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:154-165 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:112— packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:112-122 | packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:185-197 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/view/SpatialSceneContentView.swift:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:75— packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:75-86 | packages/visionOS/web-spatial/view/SpatializedElementView.swift:43-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:152— packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:152-161 | packages/visionOS/web-spatial/manager/Dynamic3DManager.swift:164-173 — 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 (8 lines × 2) packages/visionOS/web-spatial/model/OrnamentElement.swift:166— packages/visionOS/web-spatial/model/OrnamentElement.swift:166-173 | packages/visionOS/web-spatial/model/OrnamentElement.swift:198-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/model/OrnamentElement.swift:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–8 lines × 2) packages/visionOS/web-spatial/view/SpatialNavView.swift:34— packages/visionOS/web-spatial/view/SpatialNavView.swift:34-41 | packages/visionOS/web-spatial/view/SpatialNavView.swift:45-51 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 2) packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:221— packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:221-226 | packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:236-242 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/visionOS/web-spatial/view/SpatializedDynamic3DView.swift:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) packages/visionOS/web-spatial/model/SpatialScene.swift:817— packages/visionOS/web-spatial/model/SpatialScene.swift:817-822 | packages/visionOS/web-spatial/model/SpatialScene.swift:1042-1047 — 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.
Low cohesion: SpatialScene (LCOM4 7) tests/autoTest/src/model/SpatialScene.ts:38— SpatialScene'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.
P12 · CI test-gate honesty· Test failure does not fail the CI gate · ×1
Test failure does not fail the CI gate REDACTED:62— `continue-on-error: true` lets the step or job that runs `pnpm run test:auto` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Duplication concentrated across 5 sibling directories (12 clone groups) apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20— 12 duplicated blocks under apps/ have copies in at least two of the sibling directories spatial-next-eager-min, spatial-next-min, spatial-remix-min, spatial-rspack-min, spatial-vite-min — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (6 clone groups) packages/cli/src/lib/utils/sceneUtils.ts:68— 6 duplicated blocks under packages/ have copies in at least two of the sibling directories cli, core, react — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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.
Wholesale file copy (79 identical lines × 2 files) packages/react/src/reality/hooks/useEntityEvent.tsx:10— packages/react/src/reality/hooks/useEntityEvent.tsx:10 · packages/react/src/reality/hooks/useRealityEvents.tsx:10 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (50 lines × 2 locations) apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20— apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:20 · apps/spatial-next-min/components/LazyDemo.tsx:39 — 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 (45 lines × 2 locations) packages/cli/src/lib/utils/sceneUtils.ts:68— packages/cli/src/lib/utils/sceneUtils.ts:68 · packages/core/src/scene-polyfill.ts:499 — 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) apps/spatial-next-min/components/LazyRealityScene.tsx:16— apps/spatial-next-min/components/LazyRealityScene.tsx:16 · apps/spatial-remix-min/app/components/LazyRealityScene.tsx:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (24 lines × 2 locations) packages/cli/src/lib/utils/sceneUtils.ts:162— packages/cli/src/lib/utils/sceneUtils.ts:162 · packages/core/src/types/types.ts:184 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (23 lines × 2 locations) apps/spatial-next-eager-min/app/eager/page.tsx:5— apps/spatial-next-eager-min/app/eager/page.tsx:5 · apps/spatial-next-eager-min/app/server-only-util/page.tsx:4 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (23 lines × 3 locations) apps/spatial-next-min/components/LazyRealityScene.tsx:26— apps/spatial-next-min/components/LazyRealityScene.tsx:26 · apps/spatial-remix-min/app/components/LazyRealityScene.tsx:24 · apps/spatial-vite-min/src/lazy-reality-scene.tsx:18 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (22 lines × 2 locations) packages/cli/src/lib/utils/sceneUtils.ts:24— packages/cli/src/lib/utils/sceneUtils.ts:24 · packages/core/src/types/types.ts:149 — 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 (19 lines × 2 locations) apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:15— apps/spatial-next-eager-min/components/EagerSpatialIsland.tsx:15 · apps/spatial-vite-min/src/spatial-app.tsx:84 — 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 (19 lines × 5 locations) packages/react/src/reality/components/BoxEntity.tsx:2— packages/react/src/reality/components/BoxEntity.tsx:2 · packages/react/src/reality/components/ConeEntity.tsx:2 · packages/react/src/reality/components/CylinderEntity.tsx:2 · packages/react/src/reality/components/PlaneEntity.tsx:2 · +1 more site(s) not listed — the 5 copies are spread across 5 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 (15 lines × 2 locations) apps/spatial-next-eager-min/app/server-only-util/page.tsx:19— apps/spatial-next-eager-min/app/server-only-util/page.tsx:19 · apps/spatial-next-min/app/server-only-util/page.tsx:37 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×1
Duplicated block with local edits (10 matched lines × 2 locations) REDACTED:57— REDACTED:57 · REDACTED:88 — the two spans are one implementation copied and then locally edited — 52 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 (9 lines × 2 locations) packages/cli/src/lib/pwa/config.ts:41— packages/cli/src/lib/pwa/config.ts:41 · packages/cli/src/lib/pwa/config.ts:78 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (9 matched lines × 2 locations) · ×1
Duplicated block with local edits (9 matched lines × 2 locations) packages/react/src/ornament/Ornament.tsx:167— packages/react/src/ornament/Ornament.tsx:167 · packages/react/src/reality/components/AttachmentEntity.tsx:87 — the two spans are one implementation copied and then locally edited — 62 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 (7 lines × 2 locations) packages/react/src/inspector/WebSpatialInspector.tsx:123— packages/react/src/inspector/WebSpatialInspector.tsx:123 · packages/react/src/inspector/sceneGraph.ts:98 — 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 (6 lines × 2 locations) packages/cli/src/lib/utils/sceneUtils.ts:128— packages/cli/src/lib/utils/sceneUtils.ts:128 · packages/cli/src/lib/utils/sceneUtils.ts:143 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (6 matched lines × 2 locations) · ×1
Duplicated block with local edits (6 matched lines × 2 locations) packages/core/src/motion/compute/normalize.ts:48— packages/core/src/motion/compute/normalize.ts:48 · packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:208 — the two spans are one implementation copied and then locally edited — 50 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 classifyTopLevelStatement (cyclomatic 52, cognitive 36) packages/react/src/__tests__/default-entry-side-effects.test.ts:305— classifyTopLevelStatement has cyclomatic complexity 52 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isPureExpression (cyclomatic 49, cognitive 18) packages/react/src/__tests__/default-entry-side-effects.test.ts:94— isPureExpression has cyclomatic complexity 49 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function get (cyclomatic 37, cognitive 36) · ×1
Complex function get (cyclomatic 37, cognitive 36) packages/react/src/spatialized-container/hooks/useSpatialEvents.ts:50— get has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function EntityGestureCoordinates (cyclomatic 37, cognitive 29) apps/test-server/src/pages/reality/entityGestureCoordinates.tsx:56— EntityGestureCoordinates has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 26, cognitive 48) tests/autoTest/src/WebSpatial.ts:100— (anonymous) has cyclomatic complexity 26 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateSpatializedElementProperties (cyclomatic 25, cognitive 46) tests/autoTest/src/model/SpatialScene.ts:508— updateSpatializedElementProperties has cyclomatic complexity 25 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 buildFrames (cyclomatic 24, cognitive 29) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:223— buildFrames has cyclomatic complexity 24 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PerfComparisonPage (cyclomatic 24, cognitive 21) apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:220— PerfComparisonPage has cyclomatic complexity 24 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateCommonConfig (cyclomatic 23, cognitive 29) packages/core/src/motion/entity/normalizeEntityMotionConfig.ts:125— validateCommonConfig has cyclomatic complexity 23 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectStaticGraph (cyclomatic 22, cognitive 47) packages/react/src/__tests__/default-entry-side-effects.test.ts:500— collectStaticGraph has cyclomatic complexity 22 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkIcons (cyclomatic 21, cognitive 37) packages/cli/src/lib/pwa/validate.ts:69— checkIcons has cyclomatic complexity 21 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function configStartUrl (cyclomatic 20, cognitive 30) packages/cli/src/lib/pwa/config.ts:29— configStartUrl has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function desugarTimelineConfig (cyclomatic 20, cognitive 30) packages/core/src/motion/compute/normalize.ts:144— desugarTimelineConfig has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function replaceToSpatialPrimitiveType (cyclomatic 20, cognitive 25) packages/react/src/jsx/jsx-shared.ts:101— replaceToSpatialPrimitiveType has cyclomatic complexity 20 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 valuesToMotionStyle (cyclomatic 19, cognitive 31) packages/react/src/spatialized-container/motion/style.ts:5— valuesToMotionStyle has cyclomatic complexity 19 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 21) packages/core/src/SpatializedStatic3DElement.ts:55— (anonymous) has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function configMainScene (cyclomatic 17, cognitive 40) packages/cli/src/lib/pwa/config.ts:147— configMainScene has cyclomatic complexity 17 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 formatSceneConfig (cyclomatic 17, cognitive 34) packages/core/src/scene-polyfill.ts:545— formatSceneConfig has cyclomatic complexity 17 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectTopLevelLocals (cyclomatic 17, cognitive 27) packages/react/src/__tests__/default-entry-side-effects.test.ts:218— collectTopLevelLocals has cyclomatic complexity 17 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 onReceiveEvent (cyclomatic 17, cognitive 17) packages/core/src/motion/AnimationObject.ts:137— onReceiveEvent 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 fmtValues (cyclomatic 17, cognitive 16) apps/test-server/src/pages/spatial-element-motion/shared.tsx:22— fmtValues has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function WebSpatialInspector (cyclomatic 16, cognitive 15) packages/react/src/inspector/WebSpatialInspector.tsx:687— WebSpatialInspector has cyclomatic complexity 16 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 normalizeOrnamentOptions (cyclomatic 16, cognitive 12) tests/autoTest/src/model/Ornament.ts:86— normalizeOrnamentOptions has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 updateBuildProperty (cyclomatic 15, cognitive 25) packages/cli/src/lib/xcode/xcodeproject.ts:131— updateBuildProperty has cyclomatic complexity 15 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 buildApp (cyclomatic 15, cognitive 23) tests/marginal-delta-vite/marginal-delta.test.ts:96— buildApp 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 getPWAManifest (cyclomatic 15, cognitive 20) packages/core/src/scene-polyfill.ts:410— getPWAManifest has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function RealityGestures (cyclomatic 15, cognitive 14) apps/test-server/src/pages/reality/gestures.tsx:22— RealityGestures 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 InspectorTreeNode (cyclomatic 15, cognitive 14) packages/react/src/inspector/WebSpatialInspector.tsx:222— InspectorTreeNode 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 CSSApiTest (cyclomatic 15, cognitive 14) tests/autoTest/src/testApp/CssAPITest/cssapi.tsx:45— CSSApiTest 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 validateNormalizedMotionConfig (cyclomatic 15, cognitive 13) packages/core/src/motion/compute/validate.ts:41— validateNormalizedMotionConfig has cyclomatic complexity 15 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 syncStyleSheetRulesToChild (cyclomatic 14, cognitive 18) packages/react/src/utils/windowStyleSync.ts:189— syncStyleSheetRulesToChild 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.
Complex function validateTrack (cyclomatic 14, cognitive 17) packages/core/src/motion/compute/validate.ts:85— validateTrack has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 13) tests/autoTest/tests/cssApi.test.ts:1407— (anonymous) has cyclomatic complexity 14 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.
R3 · Large Files· packages/react/src/inspector/WebSpatialInspector.tsx · ×1
packages/react/src/inspector/WebSpatialInspector.tsx: 1047 lines of code packages/react/src/inspector/WebSpatialInspector.tsx:1— packages/react/src/inspector/WebSpatialInspector.tsx has 1047 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/JSBCommand.ts · ×1
packages/core/src/JSBCommand.ts: 828 lines of code packages/core/src/JSBCommand.ts:1— packages/core/src/JSBCommand.ts has 828 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/jsapi-refresh-validation/index.tsx · ×1
apps/test-server/src/pages/jsapi-refresh-validation/index.tsx: 788 lines of code apps/test-server/src/pages/jsapi-refresh-validation/index.tsx:1— apps/test-server/src/pages/jsapi-refresh-validation/index.tsx has 788 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/reality/attachments.tsx · ×1
apps/test-server/src/pages/reality/attachments.tsx: 755 lines of code apps/test-server/src/pages/reality/attachments.tsx:1— apps/test-server/src/pages/reality/attachments.tsx has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react/src/utils/windowStyleSync.ts · ×1
packages/react/src/utils/windowStyleSync.ts: 668 lines of code packages/react/src/utils/windowStyleSync.ts:1— packages/react/src/utils/windowStyleSync.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/core/src/scene-polyfill.ts · ×1
packages/core/src/scene-polyfill.ts: 635 lines of code packages/core/src/scene-polyfill.ts:1— packages/core/src/scene-polyfill.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/page-properties-corner/index.tsx · ×1
apps/test-server/src/pages/page-properties-corner/index.tsx: 577 lines of code apps/test-server/src/pages/page-properties-corner/index.tsx:1— apps/test-server/src/pages/page-properties-corner/index.tsx has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/runtime-capabilities/index.tsx · ×1
apps/test-server/src/pages/runtime-capabilities/index.tsx: 544 lines of code apps/test-server/src/pages/runtime-capabilities/index.tsx:1— apps/test-server/src/pages/runtime-capabilities/index.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/transform-verify/index.tsx · ×1
apps/test-server/src/pages/transform-verify/index.tsx: 536 lines of code apps/test-server/src/pages/transform-verify/index.tsx:1— apps/test-server/src/pages/transform-verify/index.tsx has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx · ×1
apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx: 529 lines of code apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx:1— apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts · ×1
packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts: 525 lines of code packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts:1— packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts has 525 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
apps/test-server/index.tsx: 513 lines of code apps/test-server/index.tsx:1— apps/test-server/index.tsx has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 493 lines of code REDACTED:1— REDACTED has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/motion/entity/EntityAnimationObject.ts · ×1
packages/core/src/motion/entity/EntityAnimationObject.ts: 485 lines of code packages/core/src/motion/entity/EntityAnimationObject.ts:1— packages/core/src/motion/entity/EntityAnimationObject.ts has 485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/static-3d-model/index.tsx · ×1
apps/test-server/src/pages/static-3d-model/index.tsx: 482 lines of code apps/test-server/src/pages/static-3d-model/index.tsx:1— apps/test-server/src/pages/static-3d-model/index.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx · ×1
apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx: 478 lines of code apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx:1— apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/reality/texturedUnlitBox.tsx · ×1
apps/test-server/src/pages/reality/texturedUnlitBox.tsx: 475 lines of code apps/test-server/src/pages/reality/texturedUnlitBox.tsx:1— apps/test-server/src/pages/reality/texturedUnlitBox.tsx has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx · ×1
apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx: 474 lines of code apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx:1— apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/ornament-test/index.tsx · ×1
apps/test-server/src/pages/ornament-test/index.tsx: 455 lines of code apps/test-server/src/pages/ornament-test/index.tsx:1— apps/test-server/src/pages/ornament-test/index.tsx has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/spatial-content-ready-three/index.tsx · ×1
apps/test-server/src/pages/spatial-content-ready-three/index.tsx: 450 lines of code apps/test-server/src/pages/spatial-content-ready-three/index.tsx:1— apps/test-server/src/pages/spatial-content-ready-three/index.tsx has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx · ×1
apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx: 448 lines of code apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx:1— apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx has 448 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx · ×1
apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx: 437 lines of code apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:1— apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx has 437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/react/src/spatialized-container/hooks/useDomProxy.ts · ×1
packages/react/src/spatialized-container/hooks/useDomProxy.ts: 435 lines of code packages/react/src/spatialized-container/hooks/useDomProxy.ts:1— packages/react/src/spatialized-container/hooks/useDomProxy.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/types/types.ts · ×1
packages/core/src/types/types.ts: 431 lines of code packages/core/src/types/types.ts:1— packages/core/src/types/types.ts has 431 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/SpatializedStatic3DElement.ts · ×1
packages/core/src/SpatializedStatic3DElement.ts: 402 lines of code packages/core/src/SpatializedStatic3DElement.ts:1— packages/core/src/SpatializedStatic3DElement.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~172 LoC) packages/cli/src/lib/utils/messages.ts— no import path from any entry point (224 application, 34 tooling, 297 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 (~87 LoC) REDACTED— no import path from any entry point (224 application, 34 tooling, 297 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 (~86 LoC) packages/react/src/spatialized-container/motion/useAnimation.typecheck.ts— no import path from any entry point (224 application, 34 tooling, 297 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 (~70 LoC) packages/cli/src/lib/cmds/help.ts— no import path from any entry point (224 application, 34 tooling, 297 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 (~11 LoC) packages/react/src/runtime/index.ts— no import path from any entry point (224 application, 34 tooling, 297 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 (~10 LoC) tools/scripts/check-filesize.js— no import path from any entry point (224 application, 34 tooling, 297 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 'isbot' apps/spatial-remix-min/package.json:18— Declared in apps/spatial-remix-min/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 'react-router-dom' apps/spatial-remix-min/package.json:22— Declared in apps/spatial-remix-min/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 '@reduxjs/toolkit' apps/test-server/package.json:19— Declared in apps/test-server/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 '@xterm/addon-fit' apps/test-server/package.json:26— Declared in apps/test-server/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 'esbuild-css-modules-plugin' apps/test-server/package.json:63— Declared in apps/test-server/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 'loglevel' apps/test-server/package.json:34— Declared in apps/test-server/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 'motion' apps/test-server/package.json:35— Declared in apps/test-server/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 'react-fps' apps/test-server/package.json:40— Declared in apps/test-server/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 'react-markdown' apps/test-server/package.json:41— Declared in apps/test-server/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 'react-syntax-highlighter' apps/test-server/package.json:44— Declared in apps/test-server/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 'redux-state-sync' apps/test-server/package.json:46— Declared in apps/test-server/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 'cli-progress' packages/cli/package.json:50— Declared in packages/cli/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 'inquirer' packages/cli/package.json:54— Declared in packages/cli/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 'mime-types' packages/cli/package.json:56— Declared in packages/cli/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 'node-fetch' packages/cli/package.json:58— Declared in packages/cli/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 'valid-url' packages/cli/package.json:61— Declared in packages/cli/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 'esbuild-plugin-d.ts' packages/react/package.json:99— Declared in packages/react/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 'esbuild-plugin-define' packages/react/package.json:100— Declared in packages/react/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 'typedoc-plugin-markdown' packages/react/package.json:107— Declared in packages/react/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.
redundant comment packages/cli/src/index.ts:61— "run-pico command" repeats the code it sits on: 3 of its 3 words (run, pico, command) are already in `program`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/cli/src/lib/pwa/index.ts:82— "check manifest.json" repeats the code it sits on: 3 of its 3 words (check, manifest, json) are already in `checkManifestJson(manifest, isDev)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/cli/src/lib/resource/load.ts:64— "throw new Error( `Failed to download icon ${iconUrl}. Responded with status ${response.status}`);" repeats the code it sits on: 10 of its 10 words (throw, new, error, failed, download, icon, url, responded, status, response) are already in `throw new CustomError({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/cli/src/lib/resource/load.ts:78— "throw new Error(`Received icon "${iconUrl}" with invalid Content-Type.` + ` Responded with Content-Type "${contentType}"`);" repeats the code it sits on: 9 of its 10 words (throw, new, error, received, icon, invalid, content, type, responded) are already in `throw new CustomError({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/cli/src/lib/resource/load.ts:110— "throw new Error(`Problem reading ${iconUrl}: ${error}`);" repeats the code it sits on: 7 of its 7 words (throw, new, error, problem, reading, icon, url) are already in `throw new CustomError({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:401— "use device and runtime to create simulator" repeats the code it sits on: 5 of its 5 words (use, device, runtime, create, simulator) are already in `CliLog.info(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/core/src/JSBCommand.ts:569— "childId, parentId" repeats the code it sits on: 3 of its 3 words (child, id, parent) are already in `constructor(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/core/src/JSBCommand.ts:622— "let entityId: String let position:Vec3" repeats the code it sits on: 5 of its 6 words (entity, id, string, position, vec) are already in `constructor(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/core/src/platform-adapter/puppeteer/PuppeteerPlatform.ts:52— 6 comments in this file only repeat the code they sit on (lines 52, 276, 312, 315, 322, 427), for example "check __handleJSBMessage exist". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/react/src/spatialized-container/context/PortalInstanceContext.ts:71— "used for get extra spatialized element properties" repeats the code it sits on: 5 of its 6 words (get, extra, spatialized, element, properties) are already in `private getExtraSpatializedElementProperties?: (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/react/src/spatialized-container/context/PortalInstanceContext.ts:123— "called when 2D frame change" repeats the code it sits on: 3 of its 3 words (called, frame, change) are already in `async notify2DFrameChange()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/WebSpatial.ts:35— "Get current scene" repeats the code it sits on: 3 of its 3 words (get, current, scene) are already in `getCurrentScene(): SpatialScene | null`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/WebSpatial.ts:52— "Inspect current spatial scene" repeats the code it sits on: 4 of its 4 words (inspect, current, spatial, scene) are already in `inspectCurrentSpatialScene(): any`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/manager/JSBManager.ts:59— "Register Command Handler with Data" repeats the code it sits on: 4 of its 4 words (register, command, handler, data) are already in `registerWithData<T extends CommandDataProtocol>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/manager/JSBManager.ts:69— "Register Command Handler without Data" repeats the code it sits on: 5 of its 5 words (register, command, handler, without, data) are already in `registerWithoutData<T extends CommandDataProtocol>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/model/SpatialScene.ts:235— "Register into ProtocolHandlerManager" repeats the code it sits on: 4 of its 4 words (register, protocol, handler, manager) are already in `ProtocolHandlerManager.getInstance().registerScene(this)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/model/SpatialScene.ts:253— "Call updateSpatializedElementProperties to update common properties" repeats the code it sits on: 5 of its 6 words (call, update, spatialized, element, properties) are already in `this.updateSpatializedElementProperties(elementId, data)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/model/SpatializedElement.ts:58— "Remove from old parent" repeats the code it sits on: 3 of its 3 words (remove, old, parent) are already in `oldParent.removeChild(this)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/runtime/puppeteerRunner.ts:168— 5 comments in this file only repeat the code they sit on (lines 168, 674, 765, 828, 922), for example "Set default timeout". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/CssAPITest/cssapi.tsx:339— "Get the current TransformOrigin value" repeats the code it sits on: 5 of its 5 words (get, current, transform, origin, value) are already in `const currentTransformOrigin =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/domapiTest/domapi.tsx:65— 8 comments in this file only repeat the code they sit on (lines 65, 97, 125, 180, 227, 250, 261, 280), for example "Get the current borderRadius value". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/materialApiTest/materialapi.tsx:60— "remove --xr-background-material style property" repeats the code it sits on: 6 of its 6 words (remove, xr, background, material, style, property) are already in `testElementRef.current.style.removeProperty('--xr-background-material')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/materialApiTest/materialapi.tsx:67— "remove --xr-background-material style property" repeats the code it sits on: 6 of its 6 words (remove, xr, background, material, style, property) are already in `testElementRefParent.current.style.removeProperty(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/materialApiTest/materialapi.tsx:120— "Observe the <html> element for style attribute changes" repeats the code it sits on: 5 of its 6 words (observe, html, element, style, attribute) are already in `observer.observe(htmlElement, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/autoTest/src/testApp/materialApiTest/materialapi.tsx:260— "document.documentElement.style.setProperty( '--xr-background-material', selectedHtmlMaterial, )" repeats the code it sits on: 10 of its 10 words (document, element, style, set, property, xr, background, material, selected, html) are already in `document.documentElement.style.setProperty(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
+ 16 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel apps/test-server/src/pages/Home.tsx:48— `apps/test-server/src/pages/Home.tsx` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/styledComponentsSpatialTest/index.tsx:24— `apps/test-server/src/pages/styledComponentsSpatialTest/index.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatialCorner/index.tsx:43— `apps/test-server/src/pages/spatialCorner/index.tsx` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:24— `apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:29— `apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:35— `apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:54— `apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-magnify-gesture/index.tsx:66— `apps/test-server/src/pages/spatial-magnify-gesture/index.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:14— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:34— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:66— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:94— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:100— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:108— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:136— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:164— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:170— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 170 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:179— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 179 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:207— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 207 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:238— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 238 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:266— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-guesture/index.tsx:297— `apps/test-server/src/pages/spatial-guesture/index.tsx` reports through `console.*` at line 297 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:286— `apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx` reports through `console.*` at line 286 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx:290— `apps/test-server/src/pages/spatial-element-motion/perf-comparison.tsx` reports through `console.*` at line 290 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/test-server/src/pages/spatial-element-motion/transform-translate.tsx:66— `apps/test-server/src/pages/spatial-element-motion/transform-translate.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Mock-dominated test: use2DFrameDetector notifies and wires observers/listeners packages/react/src/coverage-boost.test.ts:395— This test sets up 5 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: destroys element if resolved after unmount packages/react/src/coverage-boost.test.ts:1154— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: binds supported elements by kind without relying on instanceof packages/react/src/spatialized-container/motion/motion.runtime.test.tsx:373— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: routes replaced Core AnimationObject destroy errors to the previous config packages/react/src/spatialized-container/motion/useAnimation.native.test.tsx:602— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: schedules afterHostLayout head sync when the 2D frame callback fires packages/react/src/spatialized-container/hooks/useSync2DFrame.test.tsx:128— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: adds fixed or root portal elements to scene packages/react/src/spatialized-container/context/PortalInstanceContext.coverage.test.ts:169— This test sets up 5 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: adds non-fixed portal elements to parent spatialized 2d element packages/react/src/spatialized-container/context/PortalInstanceContext.coverage.test.ts:185— This test sets up 12 test doubles (for example `vi.fn`) against 4 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: adjusts client coordinates relative to parent dom when available packages/react/src/spatialized-container/context/PortalInstanceContext.coverage.test.ts:247— This test sets up 7 test doubles (for example `vi.spyOn`) against 3 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: passes timeline precedence declarations to Core on create and update packages/react/src/reality/hooks/EntityMotionBinding.test.ts:241— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: keeps post-destroy playback and set local without adding onError packages/react/src/reality/hooks/EntityMotionBinding.test.ts:618— This test sets up 4 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: binds only the committed animation after async Entity creation packages/react/src/reality/hooks/useEntity.race.test.tsx:58— This test sets up 8 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: restores the latest declared transform after animation unbind completes packages/react/src/reality/hooks/useEntity.race.test.tsx:160— This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not restore declared transform after a newer animation binds packages/react/src/reality/hooks/useEntity.race.test.tsx:220— This test sets up 8 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: destroys the resolved entity without publishing or binding it through %s.addEntity when success is %s packages/react/src/reality/hooks/useEntity.race.test.tsx:276— This test sets up 9 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: publishes and binds normally, then unbinds and destroys once on unmount packages/react/src/reality/hooks/useEntity.race.test.tsx:341— This test sets up 22 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 7 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: commits the latest config before a child binds its late target packages/react/src/reality/hooks/useEntityAnimation.redesign.test.ts:442— This test sets up 17 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: creates and updates with entity-like transforms and meter dimensions packages/react/src/reality/components/AttachmentEntity.test.tsx:41— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: passes cornerRadius and backgroundMaterial through creation and in-place updates packages/react/src/reality/components/AttachmentEntity.test.tsx:124— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: entityTransform setter passes float64 array to updateProperties packages/core/src/coverage-boost.test.ts:809— This test sets up 5 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updateProperties calls UpdateSpatializedDynamic3DElementProperties packages/core/src/coverage-boost.test.ts:921— This test sets up 5 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates flags via gesture handler setters and updates transform via JSB packages/core/src/jsbcommand.coverage.test.ts:602— This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Duplicated predicate packages/core/src/motion/compute/normalize.ts:155— `!values || typeof values !== 'object' || Array.isArray(values)` appears character-identically in 2 files — packages/core/src/motion/compute/normalize.ts, packages/core/src/motion/entity/EntityAnimationObject.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/cli/src/lib/utils/sceneUtils.ts:75— `(defaultUnit === 'px' && targetUnit === 'px') || (defaultUnit === 'm' && targetUnit === 'm')` appears character-identically in 2 files — packages/cli/src/lib/utils/sceneUtils.ts, packages/core/src/scene-polyfill.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/cli/src/lib/utils/sceneUtils.ts:83— `defaultUnit === 'm' && targetUnit === 'px'` appears character-identically in 2 files — packages/cli/src/lib/utils/sceneUtils.ts, packages/core/src/scene-polyfill.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/cli/src/lib/utils/sceneUtils.ts:81— `defaultUnit === 'px' && targetUnit === 'm'` appears character-identically in 2 files — packages/cli/src/lib/utils/sceneUtils.ts, packages/core/src/scene-polyfill.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react/src/facades/shared/warnBootForgotten.ts:25— `typeof process !== 'undefined' && process.env.NODE_ENV === 'production'` appears character-identically in 3 files — packages/react/src/facades/shared/warnBootForgotten.ts, packages/react/src/ornament/Ornament.tsx, packages/react/src/runtime/bridge.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/src/motion/compute/validate.ts:147— `typeof value !== 'number' || !Number.isFinite(value)` appears character-identically in 2 files — packages/core/src/motion/compute/validate.ts, packages/core/src/motion/entity/normalizeEntityMotionConfig.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/react/src/inspector/WebSpatialInspector.tsx:70— `typeof value === 'number' && Number.isFinite(value)` appears character-identically in 2 files — packages/react/src/inspector/WebSpatialInspector.tsx, packages/react/src/inspector/sceneGraph.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/src/Ornament.ts:153— `typeof value === 'number' && Number.isFinite(value) && value >= 0` appears character-identically in 2 files — packages/core/src/Ornament.ts, packages/core/src/reality/attachmentSurface.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/src/runtime/capability-manifest.ts:24— `typeof value === 'object' && value !== null && !Array.isArray(value)` appears character-identically in 2 files — packages/core/src/runtime/capability-manifest.ts, packages/react/src/inspector/sceneGraph.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/visionOS/web-spatial/model/element-motion/SpatializedElementAnimationObject.swift:117— `playState == .running || playState == .paused` appears character-identically in 2 files — packages/visionOS/web-spatial/model/element-motion/SpatializedElementAnimationObject.swift, packages/visionOS/web-spatial/model/entity-motion/EntityMotionAnimationObject.swift. 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.
Deprecated: git-raw-commits REDACTED:4921— git-raw-commits 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Use @conventional-changelog/git-client instead.". 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:4946— 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: inflight REDACTED:5169— 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: rimraf REDACTED:6837— rimraf 2.6.3 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:6842— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:7936— whatwg-encoding 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:7941— whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
M2 · Architecture documentation· Architecture diagram out of date · ×5
Architecture diagram out of date openspec/changes/add-entity-transform-animation/design.md:417— `openspec/changes/add-entity-transform-animation/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/react-sdk`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Architecture diagram out of date openspec/changes/add-entity-transform-animation/design.zh.md:413— `openspec/changes/add-entity-transform-animation/design.zh.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/react-sdk`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Architecture diagram out of date openspec/changes/redesign-entity-motion-api/design.md:118— `openspec/changes/redesign-entity-motion-api/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/platform-visionos`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Architecture diagram out of date openspec/changes/redesign-entity-motion-api/design.zh.md:118— `openspec/changes/redesign-entity-motion-api/design.zh.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, `@webspatial/platform-visionos`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Architecture diagram out of date openspec/changes/spatialized-element-motion-api/design.md:76— `openspec/changes/spatialized-element-motion-api/design.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `@webspatial/builder`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
No direct assertions: should pass tests/ci-test/test/e2e.test.ts:11— No conventional assertion call was detected, and 4 of 6 tests in `tests/ci-test` 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: builder run tests/ci-test/test/webspatial-builder.test.ts:2— No conventional assertion call was detected, and 4 of 6 tests in `tests/ci-test` 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: setBackgroundStyle tests/ci-test/src/specs/core-api.spec.tsx:13— No conventional assertion call was detected, and 4 of 6 tests in `tests/ci-test` 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: window.open tests/ci-test/src/specs/core-api.spec.tsx:31— No conventional assertion call was detected, and 4 of 6 tests in `tests/ci-test` 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 36 significant file(s) lose their only recent owner: packages/visionOS/web-spatial/model/entity-motion/EntityMotionAnimationObject.swift, apps/test-server/src/pages/spatial-element-motion/property-takeover.tsx, packages/core/src/motion/entity/EntityAnimationObject.ts, packages/visionOS/web-spatial/model/element-motion/SpatializedElementAnimationObject.swift, packages/visionOS/web-spatial/model/entity-motion/EntityMotionTimelineCompiler.swift, packages/react/src/reality/hooks/EntityMotionBinding.ts, packages/react/src/spatialized-container/motion/AnimationBinding.ts, apps/test-server/src/pages/entity-animation/play-state.tsx (+28 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 24 significant file(s) lose their only recent owner: apps/test-server/src/pages/runtime-capabilities/index.tsx, apps/test-server/src/pages/reality/spatialElementGestureCoordinates.tsx, tools/scripts/iwdp-sim.py, apps/test-server/src/pages/spatial-content-ready-three/index.tsx, apps/test-server/src/pages/runtime-capabilities/ContractChecks.tsx, packages/react/src/spatialized-container/hooks/useDomProxy.ts, apps/test-server/src/pages/spatial-rotate-axis-constraint/index.tsx, apps/test-server/src/pages/reality/entityGestureCoordinates.tsx (+16 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: apps/test-server/src/pages/static-3d-model/index.tsx, packages/visionOS/web-spatial/model/BlobTransfer.swift, packages/visionOS/web-spatial/view/view-modifier/OrbitModifier.swift, packages/visionOS/web-spatial/model/SpatializedStatic3DElement.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: apps/test-server/src/pages/page-properties-corner/index.tsx, apps/test-server/src/pages/ornament-test/index.tsx, packages/react/src/ornament/Ornament.tsx. 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/visionOS/package.json:1— `packages/visionOS` (9732 LoC, 267 module-visible types across 12 directories) overshoots its size bounds. 3 of 11 build unit(s) (SwiftPM, npm) overshoot their size bounds, lowering Project Cohesion to 4.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/core/package.json:1— `packages/core` (8591 LoC, 265 module-visible types across 19 directories) overshoots its size bounds. 3 of 11 build unit(s) (SwiftPM, npm) overshoot their size bounds, lowering Project Cohesion to 4.5/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/react/package.json:1— `packages/react` (11715 LoC, 153 module-visible types across 20 directories) overshoots its size bounds. 3 of 11 build unit(s) (SwiftPM, npm) overshoot their size bounds, lowering Project Cohesion to 4.5/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.
Outdated (npm): inquirer packages/cli/package.json:54— inquirer is pinned at 8.2.7; registry.npmjs.org publishes 14.3.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): motion apps/test-server/package.json:35— motion is pinned at 11.18.2; registry.npmjs.org publishes 14.14.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.
README/code drift CONTRIBUTING.md:10— CONTRIBUTING.md names Xcode 26, but the manifest declares `xcode` ^3.0.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/react/README.md:148— packages/react/README.md links to `../../openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md`, but `openspec/changes/lazy-load-spatial-runtime/specs/spatial-lazy-load/spec.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Silent fallback default in catch apps/test-server/src/pages/jsapi-refresh-validation/index.tsx:55— `readHistory` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/react/src/reality/hooks/useSpatialMaterial.tsx:36— `resolveTextureIdForNative` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
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 (70 single-owned of 224 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; 224 of the 494 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: apps/test-server/src/pages/reality/texturedUnlitBox.tsx, apps/test-server/src/pages/reality/dynamicAssets.tsx, packages/cli/src/lib/pwa/index.ts.
D21 · Naming Consistency· `resolveJsbAdapterPlatform` spells `Jsb` where 25 names in the project spell it `JSB` · ×1
`resolveJsbAdapterPlatform` spells `Jsb` where 25 names in the project spell it `JSB` packages/core/src/runtime/jsbAdapterPlatform.ts:34— 25 of 26 names in project webspatial-sdk spell the token `JSB` (25 of 26; unit: names in project webspatial-sdk containing `JSB`). Peers: packages.core.src.JSBCommand.CreateSpatializedElementAnimationJSBCommand (packages/core/src/JSBCommand.ts:782); packages.core.src.JSBCommand.ControlSpatializedElementAnimationJSBCommand (packages/core/src/JSBCommand.ts:798); packages.core.src.JSBCommand.CreateEntityAnimationJSBCommand (packages/core/src/JSBCommand.ts:898); packages.core.src.JSBCommand.UpdateEntityAnimationJSBCommand (packages/core/src/JSBCommand.ts:914); packages.core.src.JSBCommand.ControlEntityAnimationJSBCommand (packages/core/src/JSBCommand.ts:930). Rename to `resolveJSBAdapterPlatform`. [rule N6]
D21 · Naming Consistency· `deepCloneJSON` spells `JSON` where 14 names in the project spell it `Json` · ×1
`deepCloneJSON` spells `JSON` where 14 names in the project spell it `Json` packages/core/src/utils.ts:70— 14 of 15 names in project webspatial-sdk spell the token `Json` (14 of 15; unit: names in project webspatial-sdk containing `Json`). Peers: ManifestDependencies.loadJsonFromDisk (packages/cli/src/lib/cmds/runPico.ts:24); ManifestDependencies.loadJsonFromNet (packages/cli/src/lib/cmds/runPico.ts:25); config.configId(manifestJson) (packages/cli/src/lib/pwa/config.ts:15); config.configStartUrl(manifestJson) (packages/cli/src/lib/pwa/config.ts:29); config.configScope(manifestJson) (packages/cli/src/lib/pwa/config.ts:101). Rename to `deepCloneJson`. [rule N6]
D21 · Naming Consistency· `jsxDEV` spells `DEV` where 12 names in the project spell it `Dev` · ×1
`jsxDEV` spells `DEV` where 12 names in the project spell it `Dev` packages/react/src/jsx/jsx-shared.ts:174— 12 of 13 names in project webspatial-sdk spell the token `Dev` (12 of 13; unit: names in project webspatial-sdk containing `Dev`). Peers: build.doPwa(isDev) (packages/cli/src/lib/cmds/build.ts:80); build.doXcode(isDev) (packages/cli/src/lib/cmds/build.ts:110); check.checkBuildParams(isDev) (packages/cli/src/lib/cmds/check.ts:2); PWAGenerator.generator(isDev) (packages/cli/src/lib/pwa/index.ts:33); PWAGenerator.validate(isDev) (packages/cli/src/lib/pwa/index.ts:44). Rename to `jsxDev`. [rule N6]
D21 · Naming Consistency· `sceneID` spells `ID` where 76 names in the project spell it `Id` · ×1
`sceneID` spells `ID` where 76 names in the project spell it `Id` packages/visionOS/web-spatial/model/SpatialApp.swift:20— 76 of 78 names in project repository spell the token `Id` (76 of 78; unit: names in project repository containing `Id`). Peers: AddSpatializedElementToSpatialScene.spatializedElementId (packages/visionOS/web-spatial/JSBCommand.swift:18); AddOrnamentToSceneCommand.ornamentId (packages/visionOS/web-spatial/JSBCommand.swift:23); CreateUnlitMaterial.textureId (packages/visionOS/web-spatial/JSBCommand.swift:57); CreatePBRMaterial.textureId (packages/visionOS/web-spatial/JSBCommand.swift:65); CreateSpatialModelEntity.modelAssetId (packages/visionOS/web-spatial/JSBCommand.swift:90). Rename to `sceneId`. [rule N6]
D21 · Naming Consistency· `navigationStateListenerID` spells `ID` where 76 names in the project spell it `Id` · ×1
`navigationStateListenerID` spells `ID` where 76 names in the project spell it `Id` packages/visionOS/web-spatial/view/SpatialNavView.swift:81— 76 of 78 names in project repository spell the token `Id` (76 of 78; unit: names in project repository containing `Id`). Peers: AddSpatializedElementToSpatialScene.spatializedElementId (packages/visionOS/web-spatial/JSBCommand.swift:18); AddOrnamentToSceneCommand.ornamentId (packages/visionOS/web-spatial/JSBCommand.swift:23); CreateUnlitMaterial.textureId (packages/visionOS/web-spatial/JSBCommand.swift:57); CreatePBRMaterial.textureId (packages/visionOS/web-spatial/JSBCommand.swift:65); CreateSpatialModelEntity.modelAssetId (packages/visionOS/web-spatial/JSBCommand.swift:90). Rename to `navigationStateListenerId`. [rule N6]
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 224 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 224 of the 494 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: apps/test-server/src/pages/memoryStats/index.tsx. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file apps/test-server/src/pages/memoryStats/index.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Disabled test tests/ci-test/test/webspatial-builder.test.ts:1— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `openspec/changes/archive/2026-06-30-lazy-load-spatial-runtime/REVIEW.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Logging is not universal — Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/spatial-next-eager-min`, `apps/spatial-next-min`.
No dependency-update automation package.json:72— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code· Unused export 'isValidSpatialSceneType' · ×1
Unused export 'isValidSpatialSceneType' packages/cli/src/lib/utils/sceneUtils.ts:51— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'formatSceneConfig' · ×1
Unused export 'formatSceneConfig' packages/cli/src/lib/utils/sceneUtils.ts:114— Nothing imports this binding — it is safe to review for removal.
Unused export 'ReactJSX' packages/react/src/jsx/jsx-namespace.ts:72— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'useAttachmentContext' · ×1
Unused export 'useAttachmentContext' packages/react/src/reality/context/AttachmentContext.tsx:67— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/react/src/reality/context/index.tsx, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/react/src/reality/context/index.tsx in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused module-local declaration 'SafeSceneState' · ×1
Unused module-local declaration 'SafeSceneState' tests/autoTest/src/webview/ProtocolHandlerManager.ts:12— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
No security response headers detected apps/test-server/vercel.json:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) override strict null checking — ~2.1 `!` null assertions per 1k TypeScript source lines — 59 assertion(s) across the 28173 source line(s) of the 287 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/react/src/utils/windowStyleSync.ts (10), packages/react/src/spatialized-container/context/PortalInstanceContext.ts (6), packages/core/src/motion/entity/EntityAnimationObject.ts (5). 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.
Outdated (npm): @react-router/node — @react-router/node is pinned at 7.18.3; registry.npmjs.org publishes 8.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/serve — @react-router/serve is pinned at 7.18.3; registry.npmjs.org publishes 8.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-spring/web — @react-spring/web is pinned at 9.7.5; registry.npmjs.org publishes 10.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): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 2.12.0; registry.npmjs.org publishes 2.14.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): @tailwindcss/vite — @tailwindcss/vite is pinned at 4.3.3; registry.npmjs.org publishes 4.3.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/three — @types/three is pinned at 0.164.1; registry.npmjs.org publishes 0.187.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): @vitejs/plugin-react — @vitejs/plugin-react is pinned at 6.1.1; registry.npmjs.org publishes 6.3.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): @xterm/addon-fit — @xterm/addon-fit is pinned at 0.10.0; registry.npmjs.org publishes 0.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): @xterm/xterm — @xterm/xterm is pinned at 5.5.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): animejs — animejs is pinned at 3.2.2; registry.npmjs.org publishes 4.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): autoprefixer — autoprefixer is pinned at 10.5.4; registry.npmjs.org publishes 10.6.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): axios — axios is pinned at 1.20.0; registry.npmjs.org publishes 1.21.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): bplist-parser — bplist-parser is pinned at 0.5.0; registry.npmjs.org publishes 0.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): chai — chai is pinned at 5.3.3; registry.npmjs.org publishes 6.3.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): commander — commander is pinned at 13.1.0; registry.npmjs.org publishes 15.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.
Outdated (npm): express — express is pinned at 4.22.2; registry.npmjs.org publishes 5.3.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): fetch-h2 — fetch-h2 is pinned at 2.5.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): gsap — gsap is pinned at 3.15.0; registry.npmjs.org publishes 3.15.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): isbot — isbot is pinned at 5.2.2; registry.npmjs.org publishes 5.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): livereload — livereload is pinned at 0.9.3; registry.npmjs.org publishes 0.10.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): mime-types — mime-types is pinned at 2.1.35; 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): mocha — mocha is pinned at 11.8.0; registry.npmjs.org publishes 12.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): next — next is pinned at 15.5.27; registry.npmjs.org publishes 16.4.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): node-fetch — node-fetch is pinned at 2.7.0; registry.npmjs.org publishes 3.3.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): postcss — postcss is pinned at 8.5.28; registry.npmjs.org publishes 8.5.33 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): Reality parity — real-impl does NOT render the documented <div aria-hidden> placeholder; align via §15.8 follow-up packages/react/src/__tests__/parity.test.tsx:240— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): Entity-class parity (Box/Sphere/Cone/Cylinder/Plane/Model/AttachmentEntity) — real-impl throws on missing Reality context instead of rendering null; align via §15.8 follow-up packages/react/src/__tests__/parity.test.tsx:250— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): Material / Texture / *Asset parity — same as Entity-class; align via §15.8 follow-up packages/react/src/__tests__/parity.test.tsx:254— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): SceneGraph / World parity — Path 2 unpinned in `runtime-capabilities`; needs spec amendment under §15.8 packages/react/src/__tests__/parity.test.tsx:263— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
doc comments repeat the names packages/cli/src/lib/utils/Log.ts:103— 0 of 24 documented parameters and 1 of 18 summaries in `@webspatial/builder` only repeat the member or parameter name (e.g. "Sets the verbose." for `setVerbose`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/core/src/SpatializedStatic3DElement.ts:35— 1 of 63 documented parameters and 6 of 368 summaries in `@webspatial/core-sdk` only repeat the member or parameter name (e.g. "URL of the 3D model" for `modelURL`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/autoTest/src/model/SpatialScene.ts:275— 1 of 21 documented parameters and 30 of 115 summaries in `autotest` only repeat the member or parameter name (e.g. "update transform for spatializedElement" for `handleUpdateSpatializedElementTransform`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 13 file(s) — `apps/spatial-remix-min/app/routes.ts`, `apps/spatial-remix-min/react-router.config.ts`, `packages/core/src/runtime/keys.ts`, `packages/react/src/MaterialPresets.ts`, `packages/react/src/eager.ts`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e4f9-91e1-7130-b8c3-dedbe74f1022 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 58 · Warnings: 408 · Recommendations: 169 · Info: 48 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 15:28 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.