Public report of repalash/threepipe, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 19:21 UTC · Survey ID cd_3bf861f3c047427db6eafcb8b92f036d
repalash/threepipe
Measured 17 November 2026, 19:14 UTC, at code version 79e83e6
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
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: 79,503 lines of product code in 20 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 33.6
Findings by how serious they are
52 critical1125 serious115 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 19:14 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.
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 ▸
73of 73 dimensions measured by tools.
1267of 1292 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
73dimensions across 7 lenses, read from 79,503 lines of product code in 20 projects.
repalash/threepipe falls short of our standard for a preview release because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 42.2 out of 100 and is rated Weak, and 36 of its 52 critical findings are security problems.
Production Readiness, at 33.6, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 3.4 points. Adopting a logging library would lift Production Readiness itself, worth about 3.9 points. Raising Production Readiness to 62 would lift the score to about 49.0.
Twenty-two known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eight controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks. The four passwords or keys in the code's history need replacing, with the old ones switched off. The three loops of files that import each other need breaking.
The product code is 79,503 lines, about €72,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 33.6 to 62, the lowest score rated Strong, the score would rise from 42.2 to about 49.0.
Code composition: what the lines of code are
Product code 95%Tests 5%
Rebuild cost: about €72,000 · Estimate
Cost to rebuild
€24,000 to €120,000, for 399 to 1,265 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 42. 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: 79,503 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 1 Banned license finding(s) in License Compliance — start with LICENSE.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 4.3 points · Medium effort · Text alternatives
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €72,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 33.6 (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 1 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 3.4 points for low effort, because it clears the 1 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 12,184 lines over the last 90 days, which is about 49,413 lines a year. At that pace, the extra work comes to an estimated 7.8 to 46.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: 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.
382 modules, with 853 dependencies between them. 7 loops run through 38 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 342 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.
2 pairs of types, where a type in plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses a type in plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations, while a change to plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses a type in plugins.svg-renderer.src.three-svg-renderer.core.viewmap.Viewmap.
plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses plugins.svg-renderer.src.three-svg-renderer.core.viewmap.Viewmap, so a change to plugins.svg-renderer.src.three-svg-renderer.core.viewmap.Viewmap can break plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations, while a change to plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations can't break plugins.svg-renderer.src.three-svg-renderer.core.viewmap.Viewmap.
Position
Below the diagonal: plugins.svg-renderer.src.three-svg-renderer.core.viewmap.operations uses a module listed above it, which is the healthy direction.
src.assetmanager.AssetManager uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.assetmanager.AssetManager, while a change to src.assetmanager.AssetManager can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.assetmanager.AssetManager uses a module listed above it, which is the healthy direction.
8→22 src.assetmanager.AssetManager uses src.viewer.ThreeViewerpart of a loop✕
Connections
1 pair of types, where a type in src.assetmanager.AssetManager uses a type in src.viewer.ThreeViewer.
src.assetmanager.AssetManager uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.assetmanager.AssetManager, while a change to src.assetmanager.AssetManager can't break src.viewer.ThreeViewer.
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.
8→24 src.assetmanager.AssetManager uses src.assetmanager.IAssetImporterpart of a loop✕
Connections
1 pair of types, where a type in src.assetmanager.AssetManager uses a type in src.assetmanager.IAssetImporter.
src.assetmanager.AssetManager uses src.assetmanager.IAssetImporter, so a change to src.assetmanager.IAssetImporter can break src.assetmanager.AssetManager, while a change to src.assetmanager.AssetManager can't break src.assetmanager.IAssetImporter.
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.
8→33 src.assetmanager.AssetManager uses plugins.3d-tiles-renderer.src.TilesRendererPluginpart of a loop✕
Connections
1 pair of types, where a type in src.assetmanager.AssetManager uses a type in plugins.3d-tiles-renderer.src.TilesRendererPlugin.
src.assetmanager.AssetManager uses plugins.3d-tiles-renderer.src.TilesRendererPlugin, so a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can break src.assetmanager.AssetManager, while a change to src.assetmanager.AssetManager can't break plugins.3d-tiles-renderer.src.TilesRendererPlugin.
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.
9→33 src.assetmanager.IImporter uses plugins.3d-tiles-renderer.src.TilesRendererPluginpart of a loop✕
Connections
1 pair of types, where a type in src.assetmanager.IImporter uses a type in plugins.3d-tiles-renderer.src.TilesRendererPlugin.
src.assetmanager.IImporter uses plugins.3d-tiles-renderer.src.TilesRendererPlugin, so a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can break src.assetmanager.IImporter, while a change to src.assetmanager.IImporter can't break plugins.3d-tiles-renderer.src.TilesRendererPlugin.
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.
src.core.IGeometry uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break src.core.IGeometry, while a change to src.core.IGeometry can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: src.core.IGeometry uses a module listed above it, which is the healthy direction.
src.core.IGeometry uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.core.IGeometry, while a change to src.core.IGeometry can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.core.IGeometry uses a module listed above it, which is the healthy direction.
src.core.IScene uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.core.IScene, while a change to src.core.IScene can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.core.IScene uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in src.core.IScene uses a type in src.core.ICamera.
The types involved
src.core.IScene.IScene → src.core.ICamera.ICamera
Direction
src.core.IScene uses src.core.ICamera, so a change to src.core.ICamera can break src.core.IScene, while a change to src.core.IScene can't break src.core.ICamera.
Position
Below the diagonal: src.core.IScene uses a module listed above it, which is the healthy direction.
12→19 src.rendering.RenderTarget uses src.core.IRendererpart of a loop✕
Connections
2 pairs of types, where a type in src.rendering.RenderTarget uses a type in src.core.IRenderer.
src.rendering.RenderTarget uses src.core.IRenderer, so a change to src.core.IRenderer can break src.rendering.RenderTarget, while a change to src.rendering.RenderTarget can't break src.core.IRenderer.
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.
13→24 src.utils.serialization uses src.assetmanager.IAssetImporterpart of a loop✕
Connections
1 pair of types, where a type in src.utils.serialization uses a type in src.assetmanager.IAssetImporter.
src.utils.serialization uses src.assetmanager.IAssetImporter, so a change to src.assetmanager.IAssetImporter can break src.utils.serialization, while a change to src.utils.serialization can't break src.assetmanager.IAssetImporter.
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.
src.core.ITexture uses src.rendering.RenderTarget, so a change to src.rendering.RenderTarget can break src.core.ITexture, while a change to src.core.ITexture can't break src.rendering.RenderTarget.
Position
Below the diagonal: src.core.ITexture uses a module listed above it, which is the healthy direction.
src.plugins.geometry.AGeometryGenerator uses src.core.IGeometry, so a change to src.core.IGeometry can break src.plugins.geometry.AGeometryGenerator, while a change to src.plugins.geometry.AGeometryGenerator can't break src.core.IGeometry.
Position
Below the diagonal: src.plugins.geometry.AGeometryGenerator uses a module listed above it, which is the healthy direction.
src.postprocessing.Pass uses src.core.ICamera, so a change to src.core.ICamera can break src.postprocessing.Pass, while a change to src.postprocessing.Pass can't break src.core.ICamera.
Position
Below the diagonal: src.postprocessing.Pass uses a module listed above it, which is the healthy direction.
src.postprocessing.Pass uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break src.postprocessing.Pass, while a change to src.postprocessing.Pass can't break src.materials.MaterialExtension.
Position
Below the diagonal: src.postprocessing.Pass uses a module listed above it, which is the healthy direction.
src.postprocessing.Pass uses src.core.IScene, so a change to src.core.IScene can break src.postprocessing.Pass, while a change to src.postprocessing.Pass can't break src.core.IScene.
Position
Below the diagonal: src.postprocessing.Pass uses a module listed above it, which is the healthy direction.
16→19 src.postprocessing.Pass uses src.core.IRendererpart of a loop✕
Connections
1 pair of types, where a type in src.postprocessing.Pass uses a type in src.core.IRenderer.
src.postprocessing.Pass uses src.core.IRenderer, so a change to src.core.IRenderer can break src.postprocessing.Pass, while a change to src.postprocessing.Pass can't break src.core.IRenderer.
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.
src.viewer.AViewerPlugin uses src.utils.serialization, so a change to src.utils.serialization can break src.viewer.AViewerPlugin, while a change to src.viewer.AViewerPlugin can't break src.utils.serialization.
Position
Below the diagonal: src.viewer.AViewerPlugin uses a module listed above it, which is the healthy direction.
17→22 src.viewer.AViewerPlugin uses src.viewer.ThreeViewerpart of a loop✕
Connections
2 pairs of types, where a type in src.viewer.AViewerPlugin uses a type in src.viewer.ThreeViewer.
src.viewer.AViewerPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.viewer.AViewerPlugin, while a change to src.viewer.AViewerPlugin can't break src.viewer.ThreeViewer.
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.
src.core.IMaterial uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.core.IMaterial, while a change to src.core.IMaterial can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.core.IMaterial uses a module listed above it, which is the healthy direction.
src.core.IMaterial uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.core.IMaterial, while a change to src.core.IMaterial can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.core.IMaterial uses a module listed above it, which is the healthy direction.
src.core.IMaterial uses src.utils.serialization, so a change to src.utils.serialization can break src.core.IMaterial, while a change to src.core.IMaterial can't break src.utils.serialization.
Position
Below the diagonal: src.core.IMaterial uses a module listed above it, which is the healthy direction.
src.core.IMaterial uses src.core.ITexture, so a change to src.core.ITexture can break src.core.IMaterial, while a change to src.core.IMaterial can't break src.core.ITexture.
Position
Below the diagonal: src.core.IMaterial uses a module listed above it, which is the healthy direction.
18→23 src.core.IMaterial uses plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPluginpart of a loop✕
Connections
1 pair of types, where a type in src.core.IMaterial uses a type in plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin.
src.core.IMaterial uses plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, so a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can break src.core.IMaterial, while a change to src.core.IMaterial can't break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin.
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.
src.core.IRenderer uses src.core.IScene, so a change to src.core.IScene can break src.core.IRenderer, while a change to src.core.IRenderer can't break src.core.IScene.
Position
Below the diagonal: src.core.IRenderer uses a module listed above it, which is the healthy direction.
src.core.IRenderer uses src.rendering.RenderTarget, so a change to src.rendering.RenderTarget can break src.core.IRenderer, while a change to src.core.IRenderer can't break src.rendering.RenderTarget.
Position
Below the diagonal: src.core.IRenderer uses a module listed above it, which is the healthy direction.
src.core.IRenderer uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break src.core.IRenderer, while a change to src.core.IRenderer can't break src.postprocessing.Pass.
Position
Below the diagonal: src.core.IRenderer uses a module listed above it, which is the healthy direction.
src.plugins.base.PipelinePassPlugin uses src.core.ICamera, so a change to src.core.ICamera can break src.plugins.base.PipelinePassPlugin, while a change to src.plugins.base.PipelinePassPlugin can't break src.core.ICamera.
Position
Below the diagonal: src.plugins.base.PipelinePassPlugin uses a module listed above it, which is the healthy direction.
src.plugins.base.PipelinePassPlugin uses src.core.IScene, so a change to src.core.IScene can break src.plugins.base.PipelinePassPlugin, while a change to src.plugins.base.PipelinePassPlugin can't break src.core.IScene.
Position
Below the diagonal: src.plugins.base.PipelinePassPlugin uses a module listed above it, which is the healthy direction.
src.plugins.base.PipelinePassPlugin uses src.utils.serialization, so a change to src.utils.serialization can break src.plugins.base.PipelinePassPlugin, while a change to src.plugins.base.PipelinePassPlugin can't break src.utils.serialization.
Position
Below the diagonal: src.plugins.base.PipelinePassPlugin uses a module listed above it, which is the healthy direction.
src.plugins.base.PipelinePassPlugin uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break src.plugins.base.PipelinePassPlugin, while a change to src.plugins.base.PipelinePassPlugin can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: src.plugins.base.PipelinePassPlugin uses a module listed above it, which is the healthy direction.
src.plugins.base.PipelinePassPlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break src.plugins.base.PipelinePassPlugin, while a change to src.plugins.base.PipelinePassPlugin can't break src.core.IRenderer.
Position
Below the diagonal: src.plugins.base.PipelinePassPlugin uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.materials.MaterialExtension.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.core.IScene, so a change to src.core.IScene can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.core.IScene.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.rendering.RenderTarget, so a change to src.rendering.RenderTarget can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.rendering.RenderTarget.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.core.ITexture, so a change to src.core.ITexture can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.core.ITexture.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.postprocessing.Pass.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.rendering.RenderManager uses src.core.IRenderer, so a change to src.core.IRenderer can break src.rendering.RenderManager, while a change to src.rendering.RenderManager can't break src.core.IRenderer.
Position
Below the diagonal: src.rendering.RenderManager uses a module listed above it, which is the healthy direction.
src.viewer.ThreeViewer uses src.assetmanager.AssetManager, so a change to src.assetmanager.AssetManager can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.assetmanager.AssetManager.
Position
Below the diagonal: src.viewer.ThreeViewer uses a module listed above it, which is the healthy direction.
src.viewer.ThreeViewer uses src.core.IScene, so a change to src.core.IScene can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.core.IScene.
Position
Below the diagonal: src.viewer.ThreeViewer uses a module listed above it, which is the healthy direction.
src.viewer.ThreeViewer uses src.utils.serialization, so a change to src.utils.serialization can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.utils.serialization.
Position
Below the diagonal: src.viewer.ThreeViewer uses a module listed above it, which is the healthy direction.
src.viewer.ThreeViewer uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: src.viewer.ThreeViewer uses a module listed above it, which is the healthy direction.
src.viewer.ThreeViewer uses src.core.IRenderer, so a change to src.core.IRenderer can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.core.IRenderer.
Position
Below the diagonal: src.viewer.ThreeViewer uses a module listed above it, which is the healthy direction.
22→24 src.viewer.ThreeViewer uses src.assetmanager.IAssetImporterpart of a loop✕
Connections
1 pair of types, where a type in src.viewer.ThreeViewer uses a type in src.assetmanager.IAssetImporter.
src.viewer.ThreeViewer uses src.assetmanager.IAssetImporter, so a change to src.assetmanager.IAssetImporter can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break src.assetmanager.IAssetImporter.
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.
22→33 src.viewer.ThreeViewer uses plugins.3d-tiles-renderer.src.TilesRendererPluginpart of a loop✕
Connections
1 pair of types, where a type in src.viewer.ThreeViewer uses a type in plugins.3d-tiles-renderer.src.TilesRendererPlugin.
src.viewer.ThreeViewer uses plugins.3d-tiles-renderer.src.TilesRendererPlugin, so a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can break src.viewer.ThreeViewer, while a change to src.viewer.ThreeViewer can't break plugins.3d-tiles-renderer.src.TilesRendererPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a type in plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.core.ICamera, so a change to src.core.ICamera can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.core.ICamera.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.core.IScene, so a change to src.core.IScene can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.core.IScene.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.core.IMaterial, so a change to src.core.IMaterial can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.core.IMaterial.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.core.IRenderer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.plugins.base.PipelinePassPlugin, so a change to src.plugins.base.PipelinePassPlugin can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.plugins.base.PipelinePassPlugin.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, while a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin uses a module listed above it, which is the healthy direction.
src.assetmanager.IAssetImporter uses src.assetmanager.IImporter, so a change to src.assetmanager.IImporter can break src.assetmanager.IAssetImporter, while a change to src.assetmanager.IAssetImporter can't break src.assetmanager.IImporter.
Position
Below the diagonal: src.assetmanager.IAssetImporter uses a module listed above it, which is the healthy direction.
src.assetmanager.IAssetImporter uses src.utils.serialization, so a change to src.utils.serialization can break src.assetmanager.IAssetImporter, while a change to src.assetmanager.IAssetImporter can't break src.utils.serialization.
Position
Below the diagonal: src.assetmanager.IAssetImporter uses a module listed above it, which is the healthy direction.
src.assetmanager.IAssetImporter uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.assetmanager.IAssetImporter, while a change to src.assetmanager.IAssetImporter can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.assetmanager.IAssetImporter uses a module listed above it, which is the healthy direction.
src.plugins.animation.TransformAnimationPlugin uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.plugins.animation.TransformAnimationPlugin, while a change to src.plugins.animation.TransformAnimationPlugin can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.plugins.animation.TransformAnimationPlugin uses a module listed above it, which is the healthy direction.
src.plugins.animation.TransformAnimationPlugin uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break src.plugins.animation.TransformAnimationPlugin, while a change to src.plugins.animation.TransformAnimationPlugin can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: src.plugins.animation.TransformAnimationPlugin uses a module listed above it, which is the healthy direction.
src.plugins.animation.TransformAnimationPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.animation.TransformAnimationPlugin, while a change to src.plugins.animation.TransformAnimationPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.animation.TransformAnimationPlugin uses a module listed above it, which is the healthy direction.
src.plugins.base.BaseImporterPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.base.BaseImporterPlugin, while a change to src.plugins.base.BaseImporterPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.base.BaseImporterPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.core.ICamera, so a change to src.core.ICamera can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.core.ICamera.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.core.IScene, so a change to src.core.IScene can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.core.IScene.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.utils.serialization, so a change to src.utils.serialization can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.utils.serialization.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.postprocessing.Pass.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.core.IRenderer.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.plugins.base.PipelinePassPlugin, so a change to src.plugins.base.PipelinePassPlugin can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.plugins.base.PipelinePassPlugin.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.ProgressivePlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.pipeline.ProgressivePlugin, while a change to src.plugins.pipeline.ProgressivePlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.pipeline.ProgressivePlugin uses a module listed above it, which is the healthy direction.
src.plugins.postprocessing.AScreenPassExtensionPlugin uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.plugins.postprocessing.AScreenPassExtensionPlugin, while a change to src.plugins.postprocessing.AScreenPassExtensionPlugin can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.plugins.postprocessing.AScreenPassExtensionPlugin uses a module listed above it, which is the healthy direction.
src.plugins.postprocessing.AScreenPassExtensionPlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break src.plugins.postprocessing.AScreenPassExtensionPlugin, while a change to src.plugins.postprocessing.AScreenPassExtensionPlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: src.plugins.postprocessing.AScreenPassExtensionPlugin uses a module listed above it, which is the healthy direction.
src.plugins.postprocessing.AScreenPassExtensionPlugin uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break src.plugins.postprocessing.AScreenPassExtensionPlugin, while a change to src.plugins.postprocessing.AScreenPassExtensionPlugin can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: src.plugins.postprocessing.AScreenPassExtensionPlugin uses a module listed above it, which is the healthy direction.
src.plugins.postprocessing.AScreenPassExtensionPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.postprocessing.AScreenPassExtensionPlugin, while a change to src.plugins.postprocessing.AScreenPassExtensionPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.postprocessing.AScreenPassExtensionPlugin uses a module listed above it, which is the healthy direction.
src.core.IObject uses src.core.IGeometry, so a change to src.core.IGeometry can break src.core.IObject, while a change to src.core.IObject can't break src.core.IGeometry.
Position
Below the diagonal: src.core.IObject uses a module listed above it, which is the healthy direction.
src.core.IObject uses src.plugins.animation.TransformAnimationPlugin, so a change to src.plugins.animation.TransformAnimationPlugin can break src.core.IObject, while a change to src.core.IObject can't break src.plugins.animation.TransformAnimationPlugin.
Position
Below the diagonal: src.core.IObject uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses src.utils.serialization, so a change to src.utils.serialization can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break src.utils.serialization.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses src.core.IMaterial, so a change to src.core.IMaterial can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break src.core.IMaterial.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.LineMaterial2 uses plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, so a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can break src.core.material.LineMaterial2, while a change to src.core.material.LineMaterial2 can't break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin.
Position
Below the diagonal: src.core.material.LineMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses src.utils.serialization, so a change to src.utils.serialization can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break src.utils.serialization.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses src.core.IMaterial, so a change to src.core.IMaterial can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break src.core.IMaterial.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.PhysicalMaterial uses plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, so a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can break src.core.material.PhysicalMaterial, while a change to src.core.material.PhysicalMaterial can't break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin.
Position
Below the diagonal: src.core.material.PhysicalMaterial uses a module listed above it, which is the healthy direction.
src.core.material.ShaderMaterial2 uses plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh, so a change to plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh can break src.core.material.ShaderMaterial2, while a change to src.core.material.ShaderMaterial2 can't break plugins.svg-renderer.src.three-svg-renderer.core.SVGMesh.
Position
Below the diagonal: src.core.material.ShaderMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.ShaderMaterial2 uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.core.material.ShaderMaterial2, while a change to src.core.material.ShaderMaterial2 can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.core.material.ShaderMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.ShaderMaterial2 uses src.core.IMaterial, so a change to src.core.IMaterial can break src.core.material.ShaderMaterial2, while a change to src.core.material.ShaderMaterial2 can't break src.core.IMaterial.
Position
Below the diagonal: src.core.material.ShaderMaterial2 uses a module listed above it, which is the healthy direction.
src.core.material.ShaderMaterial2 uses plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin, so a change to plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin can break src.core.material.ShaderMaterial2, while a change to src.core.material.ShaderMaterial2 can't break plugins.webgi-plugins.src.plugins.buffer.VelocityBufferPlugin.
Position
Below the diagonal: src.core.material.ShaderMaterial2 uses a module listed above it, which is the healthy direction.
plugins.3d-tiles-renderer.src.TilesRendererPlugin uses src.assetmanager.IImporter, so a change to src.assetmanager.IImporter can break plugins.3d-tiles-renderer.src.TilesRendererPlugin, while a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can't break src.assetmanager.IImporter.
Position
Below the diagonal: plugins.3d-tiles-renderer.src.TilesRendererPlugin uses a module listed above it, which is the healthy direction.
plugins.3d-tiles-renderer.src.TilesRendererPlugin uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break plugins.3d-tiles-renderer.src.TilesRendererPlugin, while a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: plugins.3d-tiles-renderer.src.TilesRendererPlugin uses a module listed above it, which is the healthy direction.
plugins.3d-tiles-renderer.src.TilesRendererPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break plugins.3d-tiles-renderer.src.TilesRendererPlugin, while a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: plugins.3d-tiles-renderer.src.TilesRendererPlugin uses a module listed above it, which is the healthy direction.
plugins.3d-tiles-renderer.src.TilesRendererPlugin uses src.assetmanager.IAssetImporter, so a change to src.assetmanager.IAssetImporter can break plugins.3d-tiles-renderer.src.TilesRendererPlugin, while a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can't break src.assetmanager.IAssetImporter.
Position
Below the diagonal: plugins.3d-tiles-renderer.src.TilesRendererPlugin uses a module listed above it, which is the healthy direction.
plugins.3d-tiles-renderer.src.TilesRendererPlugin uses src.core.IObject, so a change to src.core.IObject can break plugins.3d-tiles-renderer.src.TilesRendererPlugin, while a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can't break src.core.IObject.
Position
Below the diagonal: plugins.3d-tiles-renderer.src.TilesRendererPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.core.IGeometry, so a change to src.core.IGeometry can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.core.IGeometry.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.viewer.AViewerPlugin, so a change to src.viewer.AViewerPlugin can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.viewer.AViewerPlugin.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.plugins.geometry.GeometryGeneratorPlugin uses src.core.IObject, so a change to src.core.IObject can break src.plugins.geometry.GeometryGeneratorPlugin, while a change to src.plugins.geometry.GeometryGeneratorPlugin can't break src.core.IObject.
Position
Below the diagonal: src.plugins.geometry.GeometryGeneratorPlugin uses a module listed above it, which is the healthy direction.
src.postprocessing.ExtendedShaderPass uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break src.postprocessing.ExtendedShaderPass, while a change to src.postprocessing.ExtendedShaderPass can't break src.postprocessing.Pass.
Position
Below the diagonal: src.postprocessing.ExtendedShaderPass uses a module listed above it, which is the healthy direction.
src.postprocessing.ExtendedShaderPass uses src.core.IRenderer, so a change to src.core.IRenderer can break src.postprocessing.ExtendedShaderPass, while a change to src.postprocessing.ExtendedShaderPass can't break src.core.IRenderer.
Position
Below the diagonal: src.postprocessing.ExtendedShaderPass uses a module listed above it, which is the healthy direction.
src.postprocessing.ExtendedShaderPass uses src.core.material.ShaderMaterial2, so a change to src.core.material.ShaderMaterial2 can break src.postprocessing.ExtendedShaderPass, while a change to src.postprocessing.ExtendedShaderPass can't break src.core.material.ShaderMaterial2.
Position
Below the diagonal: src.postprocessing.ExtendedShaderPass uses a module listed above it, which is the healthy direction.
src.utils uses src.assetmanager.export.assetExportHook, so a change to src.assetmanager.export.assetExportHook can break src.utils, while a change to src.utils can't break src.assetmanager.export.assetExportHook.
Position
Below the diagonal: src.utils uses a module listed above it, which is the healthy direction.
src.utils uses src.utils.serialization, so a change to src.utils.serialization can break src.utils, while a change to src.utils can't break src.utils.serialization.
Position
Below the diagonal: src.utils uses a module listed above it, which is the healthy direction.
src.utils uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.utils, while a change to src.utils can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.utils uses a module listed above it, which is the healthy direction.
src.utils uses src.assetmanager.IAssetImporter, so a change to src.assetmanager.IAssetImporter can break src.utils, while a change to src.utils can't break src.assetmanager.IAssetImporter.
Position
Below the diagonal: src.utils uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.core.ICamera, so a change to src.core.ICamera can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.core.ICamera.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.core.material.IMaterialUi.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.core.IScene, so a change to src.core.IScene can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.core.IScene.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.postprocessing.Pass.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.core.IRenderer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.plugins.base.PipelinePassPlugin, so a change to src.plugins.base.PipelinePassPlugin can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.plugins.base.PipelinePassPlugin.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses src.postprocessing.ExtendedShaderPass, so a change to src.postprocessing.ExtendedShaderPass can break plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin can't break src.postprocessing.ExtendedShaderPass.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSGIPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.core.ICamera, so a change to src.core.ICamera can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.core.ICamera.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.core.material.IMaterialUi.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.core.IScene, so a change to src.core.IScene can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.core.IScene.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.postprocessing.Pass.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.core.IRenderer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a type in src.plugins.base.PipelinePassPlugin.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.plugins.base.PipelinePassPlugin, so a change to src.plugins.base.PipelinePassPlugin can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.plugins.base.PipelinePassPlugin.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a type in src.postprocessing.ExtendedShaderPass.
plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses src.postprocessing.ExtendedShaderPass, so a change to src.postprocessing.ExtendedShaderPass can break plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin, while a change to plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin can't break src.postprocessing.ExtendedShaderPass.
Position
Below the diagonal: plugins.webgi-plugins.src.plugins.postprocessing.SSReflectionPlugin uses a module listed above it, which is the healthy direction.
src.assetmanager.import.GLTFLoader2 uses src.assetmanager.IImporter, so a change to src.assetmanager.IImporter can break src.assetmanager.import.GLTFLoader2, while a change to src.assetmanager.import.GLTFLoader2 can't break src.assetmanager.IImporter.
Position
Below the diagonal: src.assetmanager.import.GLTFLoader2 uses a module listed above it, which is the healthy direction.
src.assetmanager.import.GLTFLoader2 uses src.utils.serialization, so a change to src.utils.serialization can break src.assetmanager.import.GLTFLoader2, while a change to src.assetmanager.import.GLTFLoader2 can't break src.utils.serialization.
Position
Below the diagonal: src.assetmanager.import.GLTFLoader2 uses a module listed above it, which is the healthy direction.
src.assetmanager.import.GLTFLoader2 uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.assetmanager.import.GLTFLoader2, while a change to src.assetmanager.import.GLTFLoader2 can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.assetmanager.import.GLTFLoader2 uses a module listed above it, which is the healthy direction.
src.assetmanager.import.GLTFLoader2 uses plugins.3d-tiles-renderer.src.TilesRendererPlugin, so a change to plugins.3d-tiles-renderer.src.TilesRendererPlugin can break src.assetmanager.import.GLTFLoader2, while a change to src.assetmanager.import.GLTFLoader2 can't break plugins.3d-tiles-renderer.src.TilesRendererPlugin.
Position
Below the diagonal: src.assetmanager.import.GLTFLoader2 uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.core.ICamera, so a change to src.core.ICamera can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.core.ICamera.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.core.material.IMaterialUi, so a change to src.core.material.IMaterialUi can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.core.material.IMaterialUi.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.materials.MaterialExtension, so a change to src.materials.MaterialExtension can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.materials.MaterialExtension.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.core.IScene, so a change to src.core.IScene can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.core.IScene.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.postprocessing.Pass, so a change to src.postprocessing.Pass can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.postprocessing.Pass.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.core.IRenderer, so a change to src.core.IRenderer can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.core.IRenderer.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.plugins.base.PipelinePassPlugin, so a change to src.plugins.base.PipelinePassPlugin can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.plugins.base.PipelinePassPlugin.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.viewer.ThreeViewer, so a change to src.viewer.ThreeViewer can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.viewer.ThreeViewer.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
src.plugins.pipeline.SSAOPlugin uses src.postprocessing.ExtendedShaderPass, so a change to src.postprocessing.ExtendedShaderPass can break src.plugins.pipeline.SSAOPlugin, while a change to src.plugins.pipeline.SSAOPlugin can't break src.postprocessing.ExtendedShaderPass.
Position
Below the diagonal: src.plugins.pipeline.SSAOPlugin uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 53.0 · Adequate · gated by D2, R10 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
42
High / Critical
A05:2025 — Injection
21
High / Critical
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
Top priorities: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Adopt pino (or winston) and log at meaningful points in the services you run.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Banned license finding(s) in License Compliance — start with LICENSE.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 52
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 — 1125
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 — 115
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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 73 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 — 73 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, 1267 of 1292 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.
D16 Bus Factor — 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 971 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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. `plugins/3d-tiles-renderer/src/gltf.ts`, `plugins/geometry-generator/src/FontLibrary.ts`, `plugins/geometry-generator/src/index.ts`, `plugins/path-tracing/src/WebGLPathTracer2.ts`, `plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts`, … (+50 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.
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: "> threepipe@0.6.1 dev / > NODE_ENV=development vite build --watch / vite v7.3.1 building client environment for production... / watching for file changes... / build started... / transforming... / ✓ 403 modules transformed. / rendering chunks... / computing gzip size... / dist/index.mjs 3,542.91 kB │ gzip: 716.44 kB │ map: 6,865.64 kB / built in 6502ms." 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: "> threepipe@0.6.1 dev / > NODE_ENV=development vite build --watch / vite v7.3.1 building client environment for production... / watching for file changes... / build started... / transforming... / ✓ 403 modules transformed. / rendering chunks... / computing gzip size... / dist/index.mjs 3,542.91 kB │ gzip: 716.44 kB │ map: 6,865.64 kB / built in 6502ms." No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 168 further occurrence(s) are not listed individually; the score already reflects all 208.
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. 118 further occurrence(s) are not listed individually; the score already reflects all 158.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
S1 Web-Security Posture — 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. 411 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X26 Unsynchronised callback handoff — 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 Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C++ is not read 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.
X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Go source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Go was found, and this repository's C++ is not read 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.
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 make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 26 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
102 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GLTFMaterialExtrasExtension.Export at 128. 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 cache.overrideThreeCache at 22 — 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: src/three/utils/cache.ts (cache.overrideThreeCache at 22), plugins/webgi-plugins/src/utils/Reflector2.ts (Reflector2.constructor at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 94 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with GLTFMaterialExtrasExtension.Export (cyclomatic 128), material.createMaterial (cyclomatic 86), GLTFMaterialExtrasExtension.Import (cyclomatic 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 4.4 to about 5.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 125 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 13 bodies over 60 down to 60 or less in Cognitive Complexity — start with updateMatrixWorld (cognitive 148), GLTFMaterialExtrasExtension.Import (cognitive 137), geometry.createBufferGeometry (cognitive 136). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cognitive Complexity from 3.0 to about 5.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 10 MethodTooLong finding(s) in God Classes — start with REDACTED (3), PivotControls.ts, ExtendedRenderPass.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 FileTooLong finding(s) in God Classes — start with ThreeViewer.ts, REDACTED, serialization.ts. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 TooManyMethods finding(s) in God Classes — start with ThreeViewer.ts, PickingPlugin.ts, Object3DManager.ts. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
20 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 19 of the 20 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 11 Low cohesion finding(s) in Cohesion (LCOM4) — start with SSGIPlugin.ts (2), GLTFWriter2.ts, PopmotionPlugin.ts. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 335 tests.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.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 `npm ci --ignore-scripts` in the repository root (142 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.
9 outdated direct production npm dependency(ies) of 15 graded, 2 pinning defect(s), across 20 package.json (20 of them the product) and 19 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 2 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — 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 51 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 51 package(s) this repository's committed lockfile installs for a consumer — its 28 production, optional and peer dependency(ies), across 20 product package.json manifest(s), and everything those install in turn. Its 67 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. Third-party code that ships WITHOUT a manifest entry was read too: 3 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 1 use a banned licence. 1 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under Apache-2.0 / GPLV3 / SEE LICENSE IN LICENSE, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
625 deducted task-comment markers across 71868 LoC (0.8/KLoC) → score 8.3. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment repeated across 22 filessrc/viewer/ThreeViewer.ts:103
What to do
Resolve the 591 TodoComment finding(s) in Explicit Debt — start with serialization.ts (19), ThreeViewer.ts (18), AssetManager.ts (17). — One of this dimension's main actionable groups (591 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with ViewerRenderManager.ts, PhysicalMaterial.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 TodoComment repeated across 22 files finding(s) in Explicit Debt — start with ThreeViewer.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 21 document(s) read across 20 unit(s).
Documentation: no build, run or usage example · ×18plugins/3d-tiles-renderer/README.md:1
What to do
Resolve the 18 Documentation finding(s) in Documentation Quality — start with README.md (18). — One of this dimension's main actionable groups (18 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 48 declarations measured against a convention their peers follow.
`matToJson` spells `Json` where 90 names in the project spell it `JSON`src/assetmanager/AssetExporter.ts:199
What to do
Resolve the 1 `matToJson` spells `Json` where 90 names in the project spell it `JSON` finding(s) in Naming Consistency — start with AssetExporter.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 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 · ×5plugins/gltf-transform/src/GLTFDracoExportPlugin.ts:91
What to do
Resolve the 25 redundant comment finding(s) in Comment Value — start with tpImageInputGenerator.ts (2), setupComponent.ts (2), CascadedShadowsPlugin.ts (2). — One of this dimension's main actionable groups (25 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
21 finding(s): 0 critical, 10 high, 11 medium, 0 low. 10 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 57 file(s) — `examples/screen-pass-extension-plugin/script.ts` (line 39), `plugins/3d-tiles-renderer/src/gltf.ts` (line 10, line 16, line 19, …), `plugins/geometry-generator/src/FontLibrary.ts` (lines 41–42, line 46), `plugins/geometry-generator/src/index.ts` (line 25), `plugins/path-tracing/src/WebGLPathTracer2.ts` (line 25, line 27, line 29), … (+52 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 10 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 (10 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 11 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 271 of the 428 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — plugins/configurator/src/GridItemList.ts:59, src/plugins/interaction/LoadingScreenPlugin.ts:215
Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — src/assetmanager/import/VideoLoader.ts:38
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — src/three/utils/texture.ts:71, website/.vitepress/theme/components/WebgiShowcase.vue:27
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — plugins/timeline-ui/src/timeline.tsx:102, plugins/timeline-ui/src/timeline.tsx:375
The repo's own CSS styles .timeline-indicator-head with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — plugins/timeline-ui/src/timeline.tsx:238, plugins/timeline-ui/src/timeline.tsx:250
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×4) — src/plugins/ui/GeometryUVPreviewPlugin.ts:76, src/plugins/ui/RenderTargetPreviewPlugin.ts:112, src/utils/CustomContextMenu.ts:58, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
`.treejs .treejs-node-selected > .treejs-label` sets color: #eee on background-color: #067ce9 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — plugins/tweakpane-editor/src/HierarchyUiPlugin.ts:79
`.switch input[type="checkbox"]` 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. — website/.vitepress/theme/components/EffectToggle.vue:82
`.timeline-controls-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — plugins/timeline-ui/src/timeline.css:312
`.css-in-js .treejs .treejs-node-selected > .treejs-label` 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. — plugins/tweakpane-editor/src/HierarchyUiPlugin.ts:82
`.css-in-js *: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. — examples/shadertoy-player/script.ts:416
`.css-in-js .editor-container textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/shadertoy-player/script.ts:444
`.model-tab` moves (`transition: background 0.3s, transform 0.3s, color 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/.vitepress/theme/custom.css:215
`.loadingScreenLogoElement` moves (`animation: rotation1 4s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/.vitepress/theme/custom.css:277
`#assetManagerLoadingScreen` moves (`transition: opacity 0.5s ease-in-out, min-width 0.5s, min-height 0.5s, bottom 0.5s, right 0.5s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/plugins/interaction/LoadingScreenPlugin.css:18
`.loader` moves (`animation: rotation 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/plugins/interaction/loaders/spinner1.css:9
`.button-bar-selected:before` moves (`transition: width 0.25s, left 0.25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — plugins/tweakpane-editor/src/TweakpaneEditorPlugin.css:89
`.timeline-card` moves (`transition: transform 0.2s ease, opacity 0.2s ease, box-shadow 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — plugins/timeline-ui/src/timeline.css:69
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.
`ICamera` declares 26 required operations: `setDirty`, `activateMain`, `deactivateMain`, `refreshTarget`, `refreshAspect`, `setInteractions`, `setControlsCtor`, `removeControlsCtor`, `refreshCameraControls`, `updateProjectionMatrix`, `getView`, `setView`, `fitObject`, `setViewFromCamera`, `setViewToMain`, `setCanvas`, `traverse`, `traverseVisible`, `traverseAncestors`, `getObjectById`, `getObjectByName`, `getObjectByProperty`, `copy`, `clone`, `add`, `remove`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/core/ICamera.ts:57
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — plugins/configurator/src/GridItemList.ts:41
A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition. — plugins/gaussian-splatting/src/three-gaussian-splat/materials/GaussianSplatMaterialExtension.ts:47
`initTimeline` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — plugins/timeline-ui/src/init.ts:7
The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/plugins/extras/components/typeSystem.ts:168
`onParseReady` has an empty body — confirm it's an intentional no-op and not an unfinished method. — plugins/blend-importer/src/js-blend/parser/parser.js:32
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×6) — src/assetmanager/import/MTLLoader2.ts:1, src/assetmanager/import/MTLLoader2.ts:2, src/assetmanager/import/OBJLoader2.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.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
README.md names TypeScript 6, but the manifest declares `typescript` 5.8.3. 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.md:140
What to do
Reconcile the README with reality: README.md names TypeScript 6, but the manifest declares `typescript` 5.8.3.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 405 JavaScript/TypeScript production file(s) this check read across 20 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`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:117
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`existsSync` in `has` 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. — scripts/vite-utils.mjs:84
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.5 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
Do you agree with this assessment?
R10 · Code Duplication3.9 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
26 duplicated blocks under the repository root have copies in at least two of the sibling directories plugins, scripts, src — 20 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 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. — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69
14 duplicated blocks under src/ have copies in at least two of the sibling directories assetmanager, core, plugins, postprocessing, rendering, three (+1 more sibling(s) not listed) — 5 of them are reported below, and 9 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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. — src/plugins/pipeline/GBufferPlugin.ts:214
14 duplicated blocks under src/plugins/ have copies in at least two of the sibling directories animation, base, extras, geometry, import, interaction (+2 more sibling(s) not listed) — 10 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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. — src/plugins/animation/AnimationObjectPlugin.ts:273
12 duplicated blocks under plugins/ have copies in at least two of the sibling directories 3d-tiles-renderer, assimpjs, blend-importer, blueprintjs, configurator, extra-importers (+13 more sibling(s) not listed) — 11 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63
5 duplicated blocks under src/core/ have copies in at least two of the sibling directories geometry, light, material, object — 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/core/light/DirectionalLight2.ts:133
plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:52 · plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:52 — the two spans are one implementation copied and then locally edited — 1152 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. — plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:52
src/plugins/material/ClearcoatTintPlugin.ts:18 · src/plugins/material/NoiseBumpMaterialPlugin.ts:21 — the two spans are one implementation copied and then locally edited — 997 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. — src/plugins/material/ClearcoatTintPlugin.ts:18
src/core/camera/OrthographicCamera2.ts:259 · src/core/camera/PerspectiveCamera2.ts:238 — the two spans are one implementation copied and then locally edited — 1005 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. — src/core/camera/OrthographicCamera2.ts:259
plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69 · src/plugins/material/CustomBumpMapPlugin.ts:44 — the two spans are one implementation copied and then locally edited — 901 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. — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69
src/plugins/material/FragmentClippingExtensionPlugin.ts:22 · src/plugins/material/NoiseBumpMaterialPlugin.ts:21 — the two spans are one implementation copied and then locally edited — 849 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. — src/plugins/material/FragmentClippingExtensionPlugin.ts:22
plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:137 · src/plugins/pipeline/SSAOPlugin.ts:230 — the two spans are one implementation copied and then locally edited — 848 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. — plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:137
src/plugins/ui/GeometryUVPreviewPlugin.ts:18 · src/plugins/ui/RenderTargetPreviewPlugin.ts:28 — the two spans are one implementation copied and then locally edited — 699 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. — src/plugins/ui/GeometryUVPreviewPlugin.ts:18
src/core/camera/OrthographicCamera2.ts:16 · src/core/camera/PerspectiveCamera2.ts:27 — the two spans are one implementation copied and then locally edited — 845 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. — src/core/camera/OrthographicCamera2.ts:16
src/core/material/LegacyPhongMaterial.ts:28 · src/core/material/UnlitMaterial.ts:31 — 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. — src/core/material/LegacyPhongMaterial.ts:28
plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:167 · src/plugins/pipeline/SSAOPlugin.ts:254 — the two spans are one implementation copied and then locally edited — 593 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. — plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:167
plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63 · plugins/tweakpane/src/TweakpaneUiPlugin.ts:83 — the two spans are one implementation copied and then locally edited — 678 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. — plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63
plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · plugins/extra-importers/vite.config.js:11 · plugins/gaussian-splatting/vite.config.js:11 · +2 more site(s) not listed — the 6 copies are spread across 6 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. — plugins/blend-importer/vite.config.js:11
plugins/assimpjs/vite.config.js:11 · plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · plugins/network/vite.config.js:11 — the 4 copies are spread across 4 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. — plugins/assimpjs/vite.config.js:11
plugins/3d-tiles-renderer/src/CMPTLoadPlugin.ts:17 · plugins/3d-tiles-renderer/src/PNTSLoadPlugin.ts:16 — 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. — plugins/3d-tiles-renderer/src/CMPTLoadPlugin.ts:17
src/plugins/interaction/PivotControlsPlugin.ts:115 · src/plugins/interaction/TransformControlsPlugin.ts:106 — 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. — src/plugins/interaction/PivotControlsPlugin.ts:115
src/assetmanager/gltf/GLTFMaterialsBumpMapExtension.ts:15 · src/assetmanager/gltf/GLTFMaterialsDisplacementMapExtension.ts:13 — 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. — src/assetmanager/gltf/GLTFMaterialsBumpMapExtension.ts:15
src/plugins/pipeline/DepthBufferPlugin.ts:95 · src/plugins/pipeline/GBufferPlugin.ts:102 — the two spans are one implementation copied and then locally edited — 392 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. — src/plugins/pipeline/DepthBufferPlugin.ts:95
plugins/configurator/src/MaterialConfiguratorPlugin.ts:49 · plugins/configurator/src/SwitchNodePlugin.ts:51 — the two spans are one implementation copied and then locally edited — 335 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. — plugins/configurator/src/MaterialConfiguratorPlugin.ts:49
src/three/widgets/BoneHelper.ts:40 · src/three/widgets/SkeletonHelper2.ts:43 — the two spans are one implementation copied and then locally edited — 369 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. — src/three/widgets/BoneHelper.ts:40
plugins/blueprintjs/vite.config.js:6 · plugins/timeline-ui/vite.config.js:6 · plugins/tweakpane/vite.config.js:6 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — plugins/blueprintjs/vite.config.js:6
plugins/plugin-template-vite/vite.config.js:6 · plugins/tweakpane-editor/vite.config.js:6 — 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. — plugins/plugin-template-vite/vite.config.js:6
src/core/light/PointLight2.ts:49 · src/core/light/SpotLight2.ts:52 — 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. — src/core/light/PointLight2.ts:49
src/plugins/interaction/PivotControlsPlugin.ts:30 · src/plugins/interaction/TransformControlsPlugin.ts:20 — 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. — src/plugins/interaction/PivotControlsPlugin.ts:30
plugins/3d-tiles-renderer/vite.config.js:11 · plugins/assimpjs/vite.config.js:11 · plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · +2 more site(s) not listed — the 6 copies are spread across 6 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. — plugins/3d-tiles-renderer/vite.config.js:11
plugins/svg-renderer/vite.config.js:9 · plugins/troika-text/vite.config.js:4 — the two spans are one implementation copied and then locally edited — 209 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. — plugins/svg-renderer/vite.config.js:9
plugins/gltf-transform/vite.config.js:8 · plugins/webgi-plugins/vite.config.js:11 — 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. — plugins/gltf-transform/vite.config.js:8
src/assetmanager/gltf/GLTFLightExtrasExtension.ts:5 · src/assetmanager/gltf/GLTFObject3DExtrasExtension.ts:5 — the two spans are one implementation copied and then locally edited — 316 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. — src/assetmanager/gltf/GLTFLightExtrasExtension.ts:5
plugins/3d-tiles-renderer/src/B3DMLoadPlugin.ts:22 · plugins/3d-tiles-renderer/src/I3DMLoadPlugin.ts:23 — 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. — plugins/3d-tiles-renderer/src/B3DMLoadPlugin.ts:22
plugins/3d-tiles-renderer/vite.config.js:17 · plugins/assimpjs/vite.config.js:17 · plugins/blend-importer/vite.config.js:17 · plugins/blueprintjs/vite.config.js:14 · +14 more site(s) not listed — the 18 copies are spread across 18 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. — plugins/3d-tiles-renderer/vite.config.js:17
src/plugins/material/ClearcoatTintPlugin.ts:103 · src/plugins/material/FragmentClippingExtensionPlugin.ts:118 · src/plugins/material/NoiseBumpMaterialPlugin.ts:102 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/plugins/material/ClearcoatTintPlugin.ts:103
src/plugins/material/ClearcoatTintPlugin.ts:147 · src/plugins/material/FragmentClippingExtensionPlugin.ts:172 · src/plugins/material/NoiseBumpMaterialPlugin.ts:228 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/plugins/material/ClearcoatTintPlugin.ts:147
src/utils/camera-anim.ts:13 · src/utils/camera-anim.ts:69 — the two spans are one implementation copied and then locally edited — 239 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. — src/utils/camera-anim.ts:13
vite.config.js:36 · vite.lib.config.js:45 — 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. — vite.config.js:36
plugins/svg-renderer/src/BasicSVGRendererPlugin.ts:35 · plugins/svg-renderer/src/ThreeSVGRendererPlugin.ts:152 — the two spans are one implementation copied and then locally edited — 206 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. — plugins/svg-renderer/src/BasicSVGRendererPlugin.ts:35
src/core/material/ObjectShaderMaterial.ts:28 · src/core/material/UnlitLineMaterial.ts:30 — 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. — src/core/material/ObjectShaderMaterial.ts:28
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:1 imports uiconfig-blueprint/lib/esm, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:1
plugins/configurator/src/GridItemList.ts:3 imports tippy.js/dist/tippy.css?inline, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — plugins/configurator/src/GridItemList.ts:3
plugins/tweakpane-editor/src/TweakpaneEditorPlugin.ts:15 imports tippy.js/dist/tippy.css?inline, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — plugins/tweakpane-editor/src/TweakpaneEditorPlugin.ts:15
plugins/tweakpane/src/TweakpaneUiPlugin.ts:2 imports uiconfig-tweakpane/lib/esm, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — plugins/tweakpane/src/TweakpaneUiPlugin.ts:2
src/three/Threejs.ts:219 imports three/src/constants.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/three/Threejs.ts:219
tests/unit/blend-importer-material.test.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../../plugins/blend-importer/src/loader/material) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/unit/blend-importer-material.test.ts:3
tests/unit/blend-importer-material.test.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../../plugins/blend-importer/src/loader/ctx) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/unit/blend-importer-material.test.ts:4
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
_onKeyDown has cyclomatic complexity 113 and cognitive complexity 172; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/three/controls/PivotControls.ts:205
writeMaterial has cyclomatic complexity 106 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:158
createMaterial has cyclomatic complexity 86 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plugins/blend-importer/src/loader/material.ts:162
selectionCondition has cyclomatic complexity 82 and cognitive complexity 108; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/three/utils/ObjectPicker.ts:59
createBufferGeometry has cyclomatic complexity 75 and cognitive complexity 135; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — plugins/blend-importer/src/loader/geometry.ts:187
(anonymous) has cyclomatic complexity 71 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:25
pointerMove has cyclomatic complexity 62 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:277
updateMatrixWorld has cyclomatic complexity 61 and cognitive complexity 148; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1208
ImportMeta has cyclomatic complexity 59 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/utils/serialization.ts:699
readFile has cyclomatic complexity 48 and cognitive complexity 131; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — plugins/blend-importer/src/js-blend/parser/parser.js:691
(top-level) has cyclomatic complexity 46 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/plugins/base/BaseGroundPlugin.ts:1
createBufferGeometryFromAttributes has cyclomatic complexity 43 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — plugins/blend-importer/src/loader/geometry.ts:96
deserialize has cyclomatic complexity 41 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/utils/serialization.ts:241
proxyGetValue has cyclomatic complexity 36 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — plugins/tweakpane/src/tpImageInputGenerator.ts:49
proxySetValue has cyclomatic complexity 34 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. — plugins/tweakpane/src/tpImageInputGenerator.ts:168
upgradeObject3D has cyclomatic complexity 33 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. — src/core/object/iObjectCommons.ts:696
lerpParams has cyclomatic complexity 32 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/utils/lerp.ts:126
downloadImage has cyclomatic complexity 32 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plugins/tweakpane/src/tpImageInputGenerator.ts:238
_onKeyDown has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/plugins/interaction/PickingPlugin.ts:198
processRawStartHook has cyclomatic complexity 30 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/assetmanager/AssetManager.ts:703
_getFile has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/plugins/export/CanvasSnapshotPlugin.ts:62
lerpTexture has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/utils/lerp.ts:51
GetType has cyclomatic complexity 26 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/plugins/extras/components/typeSystem.ts:70
processTexture has cyclomatic complexity 26 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. — src/assetmanager/export/GLTFWriter2.ts:184
(top-level) has cyclomatic complexity 26 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 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. — src/utils/ViewerTimeline.ts:1
importAsset has cyclomatic complexity 25 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. — src/assetmanager/AssetImporter.ts:233
CanAssign has cyclomatic complexity 24 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/plugins/extras/components/typeSystem.ts:149
(anonymous) has cyclomatic complexity 24 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. — src/plugins/animation/GLTFAnimationPlugin.ts:535
serialize has cyclomatic complexity 23 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/utils/serialization.ts:175
upgradeCamera has cyclomatic complexity 23 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. — src/core/object/iCameraCommons.ts:260
update has cyclomatic complexity 23 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. — src/three/widgets/LineHelper.ts:92
setValue has cyclomatic complexity 23 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. — src/plugins/geometry/helpers/CurveUiHelper.ts:267
serialize has cyclomatic complexity 23 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — src/utils/serialization.ts:88
enableAnisotropy has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69
_loadFile has cyclomatic complexity 22 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. — src/assetmanager/AssetImporter.ts:367
detectBlendCompression has cyclomatic complexity 22 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plugins/blend-importer/src/decompress.ts:11
onBeforeRender has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plugins/webgi-plugins/src/utils/Reflector2.ts:82
updateMatrixWorld has cyclomatic complexity 21 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. — REDACTED:1542
write has cyclomatic complexity 20 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. — tests/deterministic-injection.js:118
setMaterial has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/core/object/iObjectCommons.ts:337
Do you agree with this assessment?
R3 · Large Files6.5 / 10Adequate✓ 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.
src/viewer/ThreeViewer.ts has 1606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/viewer/ThreeViewer.ts:1
REDACTED has 1060 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
src/utils/serialization.ts has 925 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/serialization.ts:1
plugins/blend-importer/src/js-blend/parser/parser.js has 912 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/blend-importer/src/js-blend/parser/parser.js:1
src/plugins/interaction/PickingPlugin.ts has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/interaction/PickingPlugin.ts:1
src/core/object/RootScene.ts has 813 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/object/RootScene.ts:1
src/plugins/rendering/CascadedShadowsPlugin.ts has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/rendering/CascadedShadowsPlugin.ts:1
src/three/controls/PivotControls.ts has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/three/controls/PivotControls.ts:1
src/assetmanager/AssetManager.ts has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/assetmanager/AssetManager.ts:1
src/core/object/iObjectCommons.ts has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/object/iObjectCommons.ts:1
REDACTED has 727 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
src/core/material/IMaterialUi.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/material/IMaterialUi.ts:1
src/assetmanager/AssetImporter.ts has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/assetmanager/AssetImporter.ts:1
src/plugins/animation/GLTFAnimationPlugin.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/animation/GLTFAnimationPlugin.ts:1
src/plugins/animation/CameraViewPlugin.ts has 693 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/animation/CameraViewPlugin.ts:1
plugins/timeline-ui/src/timeline.tsx has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/timeline-ui/src/timeline.tsx:1
src/assetmanager/import/OBJLoader2.ts has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/assetmanager/import/OBJLoader2.ts:1
src/assetmanager/Object3DManager.ts has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/assetmanager/Object3DManager.ts:1
src/plugins/extras/EntityComponentPlugin.ts has 585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/extras/EntityComponentPlugin.ts:1
src/utils/AnimationObject.ts has 576 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/AnimationObject.ts:1
src/core/IObject.ts has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/IObject.ts:1
src/plugins/animation/AnimationObjectPlugin.ts has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/animation/AnimationObjectPlugin.ts:1
plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:1
src/plugins/pipeline/SSAOPlugin.ts has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/pipeline/SSAOPlugin.ts:1
plugins/blend-importer/src/loader/geometry.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/blend-importer/src/loader/geometry.ts:1
src/three/utils/ViewHelper2.ts has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/three/utils/ViewHelper2.ts:1
plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts has 491 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:1
src/plugins/animation/PopmotionPlugin.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/animation/PopmotionPlugin.ts:1
plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:1
plugins/webgi-plugins/src/utils/ShadowMapBaker.ts 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. — plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:1
src/assetmanager/import/GLTFLoader2.ts has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/assetmanager/import/GLTFLoader2.ts:1
src/plugins/configurator/MaterialConfiguratorBasePlugin.ts has 432 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:1
src/core/camera/PerspectiveCamera2.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/camera/PerspectiveCamera2.ts:1
plugins/timeline-ui/src/extensions.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/timeline-ui/src/extensions.ts:1
plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts:1
plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage7.2 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — plugins/blend-importer/src/js-blend/parser/parser.js:1, plugins/timeline-ui/src/timeline.tsx:1, plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Strong✓ 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.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
the root package configures a linter in `.eslintrc.cjs`, but no package script, bundler plugin, task runner or CI step in this repository runs a linter, so the rules it sets are enforced nowhere. Run it where it can fail: a `lint` script that CI runs, a linter plugin in the build, or a CI step. — .eslintrc.cjs:1
What to do
Add eslint as package.json scripts and run them in CI.
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.
Unreachable from the 45 application, 55 tooling and 26 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/blend_three.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — plugins/blend-importer/src/js-blend/threejs/material.js, plugins/blend-importer/src/js-blend/threejs/mesh.js, plugins/blend-importer/src/js-blend/threejs/light.js
no import path from any entry point (45 application, 55 tooling, 26 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 (×5) — plugins/blend-importer/src/js-blend/threejs/blend_three.js, plugins/blend-importer/src/loader/bakeGetters.ts, plugins/timeline-ui/src/init.ts, …
no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/material.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — plugins/blend-importer/src/js-blend/threejs/texture.js
Nothing imports this binding — it is safe to review for removal. — plugins/webgi-plugins/src/plugins/extras/AdvancedGroundPlugin.ts:385
Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:103
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — tests/helpers.ts:208, plugins/r3f/src/TextPlane.tsx:3
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — package.json:130, package.json:137, package.json:139, …
Declared in plugins/assimpjs/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. — plugins/assimpjs/package.json:9
Declared in plugins/svg-renderer/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) — plugins/svg-renderer/package.json:10, plugins/svg-renderer/package.json:13
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×3) — src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:68, plugins/gaussian-splatting/src/three-gaussian-splat/ThreeGaussianSplatPlugin.ts:45, plugins/gaussian-splatting/src/three-gaussian-splat/ThreeGaussianSplatPlugin.ts:50
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 document1.7 / 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.
`copyUserData` is exported and takes `source: any` from its caller, and it calls itself at line 520 (`copyUserData`) with a piece of `source` — and nowhere in `copyUserData` 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 `copyUserData` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utils/serialization.ts:520
`GetType` is exported and takes `v: any` from its caller, and it calls itself at line 80 (`this.GetType`) with a piece of `v` (and at line 111) — and nowhere in `GetType` 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 `GetType` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/plugins/extras/components/typeSystem.ts:80
`TypeToString` is exported and takes `type: TypedType` from its caller, and it calls itself at line 132 (`this.TypeToString`) with a piece of `type` (and at line 135, line 138) — and nowhere in `TypeToString` 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 `TypeToString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/plugins/extras/components/typeSystem.ts:132
`CanAssign` is exported and takes `src: TypedType` from its caller, and it calls itself at line 164 (`this.CanAssign`) with a piece of `src` (and at line 181, line 187, line 195) — and nowhere in `CanAssign` 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 `CanAssign` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/plugins/extras/components/typeSystem.ts:164
`ImportViewerConfig` is exported and takes `scene: any` from its caller, and it calls itself at line 31 (`this.ImportViewerConfig`) with a piece of `scene` — and nowhere in `ImportViewerConfig` 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 `ImportViewerConfig` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/assetmanager/gltf/GLTFViewerConfigExtension.ts:31
`bakeGetters` is exported, takes a document from its caller (line 1) and hands it to `toPlainObject`, which calls itself at line 19 (`toPlainObject`) with a piece of `source` (and at line 41) — and nowhere in `toPlainObject` 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 `toPlainObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — plugins/blend-importer/src/loader/bakeGetters.ts:19
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.
`ViewHelper2` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `renderer` itself (line 111, `new WebGLRenderer`), which makes that instance its own. But `renderer` is named in none of the methods the disposal search covered: `dispose` (line 262) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `WebGLRenderer` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this.renderer.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree. — src/three/utils/ViewHelper2.ts:111
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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.
`initDecoder` 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 })`. — src/assetmanager/import/DRACOLoader2.ts:79
`getLink` 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 })`. — plugins/network/src/TransfrSharePlugin.ts:49
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 unescaped3.6 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`svg.node.outerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — plugins/svg-renderer/src/ThreeSVGRendererPlugin.ts:322
`collapse` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — plugins/tweakpane-editor/src/util-buttons.ts:154
`expand` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — plugins/tweakpane-editor/src/util-buttons.ts:158
``
import { MeshoptSimplifier } from ${JSON.stringify(MeshOptSimplifyModifierPlugin.SIMPLIFIER_URL)};
MeshoptSimplifie…` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/plugins/extras/MeshOptSimplifyModifierPlugin.ts:45
``
import { MeshoptDecoder } from ${JSON.stringify(GLTFMeshOptDecodePlugin.DECODER_URL)};
window.MeshoptDecoder = Mesh…` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/plugins/import/GLTFMeshOptDecodePlugin.ts:42
`this.pointerIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/plugins/interaction/InteractionPromptPlugin.ts:188
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/plugins/interaction/LoadingScreenPlugin.ts:179, src/plugins/interaction/LoadingScreenPlugin.ts:181
`styles` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/utils/CustomContextMenu.ts:55
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`.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. — src/three/utils/cache.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. — plugins/blend-importer/src/loader/bakeGetters.ts:42
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.8 `!` null assertions per 1k TypeScript source lines — 199 assertion(s) across the 71331 source line(s) of the 395 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: src/plugins/interaction/PivotControlsPlugin.ts (10), src/plugins/interaction/TransformControlsPlugin.ts (10), plugins/blend-importer/src/loader/light.ts (9). 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 — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 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.
AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run 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: "> threepipe@0.6.1 dev / > NODE_ENV=development vite build --watch / vite v7.3.1 building client environment for production... / watching for file changes... / build started... / transforming... / ✓ 403 modules transformed. / rendering chunks... / computing gzip size... / dist/index.mjs 3,542.91 kB │ gzip: 716.44 kB │ map: 6,865.64 kB / built in 6502ms." No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D16 Bus Factor — single-contributor repository — bus factor is not applicable
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — 55 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication. The rest — .cpp (87 lines, 0.1% of production source) — is compared by neither card, so duplication there is unmeasured; it is a corner of this repository, not its product.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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.
S1 Web-Security Posture — Not assessed: 411 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
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 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
X27 Collection changed while being enumerated — 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×6
Click handler on a non-interactive <div> plugins/timeline-ui/src/timeline.tsx:102— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> plugins/timeline-ui/src/timeline.tsx:375— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/plugins/ui/GeometryUVPreviewPlugin.ts:76— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> src/plugins/ui/RenderTargetPreviewPlugin.ts:112— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> src/utils/CustomContextMenu.ts:58— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> website/public/scripts/viewer-controls.js:24— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC1 · Text alternatives· <img> without a text alternative · ×2
<img> without a text alternative plugins/configurator/src/GridItemList.ts:59— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative src/plugins/interaction/LoadingScreenPlugin.ts:215— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×2
Clickable element isn't keyboard-operable plugins/timeline-ui/src/timeline.tsx:238— The repo's own CSS styles .timeline-indicator-head with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable plugins/timeline-ui/src/timeline.tsx:250— The repo's own CSS styles .timeline-indicator-head with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Banned license: three-svg-renderer plugins/svg-renderer/src/three-svg-renderer/LICENSE:1— `three-svg-renderer` ships inside this repository without a manifest entry: it is a copy of another project's code in a directory of this repository that carries its own licence, and its licence is stated in its licence file `plugins/svg-renderer/src/three-svg-renderer/LICENSE`. It carries `GPL-3.0`, which this policy bans. Code copied or bundled into a product ships under its upstream licence just as a declared dependency does; no manifest names it, so this line is its site. A licence offering SEVERAL options is a choice and is charged only when every one of them is banned. Replace it, or record an accepted exception.
Unlisted import 'suspend-react' plugins/r3f/src/TextPlane.tsx:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
TodoComment tests/extras.spec.ts:148— // todo timeout or something — 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 tests/helpers.ts:205— // TODO: Remove webpToPng conversion when Playwright adds WEBP support to toMatchSnapshot — 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 tests/helpers.ts:263— // TODO: Remove WEBP→PNG conversion when Playwright adds WEBP visual diff support — 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 src/viewer/AViewerPlugin.ts:92— // todo: move to ThreeViewer — 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 src/viewer/ThreeViewer.ts:81— // todo make proper event map — 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 src/viewer/ThreeViewer.ts:346— // todo add a separate animation loop enabled? — 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 src/viewer/ThreeViewer.ts:401— // todo console.warn('container is deprecated, NOTE: subscribe to events when the canvas is moved to another container') — 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 src/viewer/ThreeViewer.ts:437— // todo: add a way to move the canvas to a new container... and dispatch event... — 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 src/viewer/ThreeViewer.ts:479— // todo listen to canvas container 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.
TodoComment src/viewer/ThreeViewer.ts:521— // todo: move inside RootScene. — 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 src/viewer/ThreeViewer.ts:534— // todo: move inside RootScene. and maybe check the world matrix and target vector 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.
TodoComment src/viewer/ThreeViewer.ts:743— // TODO - return promise? — 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 src/viewer/ThreeViewer.ts:745— // todo: dispose stuff from constructor etc — 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 src/viewer/ThreeViewer.ts:824— // todo: find a better way to resize for XR. — 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 src/viewer/ThreeViewer.ts:1107— // todo make a constructor parameter for renderSize — 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 src/viewer/ThreeViewer.ts:1108— // todo make getRenderSize or get renderSize — 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 src/viewer/ThreeViewer.ts:1141— // todo what about container resize? — 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 src/viewer/ThreeViewer.ts:1498— // todo: handle — 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 src/viewer/ThreeViewer.ts:1506— // // todo: dispose? — 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 src/viewer/ThreeViewer.ts:1620— // todo: find a better fix for context loss and restore? — 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 src/viewer/ThreeViewer.ts:1670— // todo: create/load texture utils? — 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 src/viewer/ThreeViewer.ts:1720— // todo await? — 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 src/viewer/ViewerRenderManager.ts:52— // todo: hack for now, fix blurTransmissionTarget in ExtendedRenderPass — 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 src/viewer/ViewerRenderManager.ts:53— // todo: hack for now, fix blurTransmissionTarget in ExtendedRenderPass — 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 src/utils/AnimationObject.ts:32— // - todo dosent update shadows every frame — 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.
+ 566 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file plugins/blend-importer/src/js-blend/parser/parser.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file plugins/timeline-ui/src/timeline.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 plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.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 plugins/blend-importer/src/loader/geometry.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 plugins/webgi-plugins/src/utils/ShadowMapBaker.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 plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.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 plugins/timeline-ui/src/extensions.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 plugins/gltf-transform/src/GLTFDracoExporterBase.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 plugins/path-tracing/src/ThreeGpuPathTracerPlugin.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 plugins/svg-renderer/src/ThreeSVGRendererPlugin.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 plugins/webgi-plugins/src/plugins/extras/AdvancedGroundPlugin.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 plugins/3d-tiles-renderer/src/TilesRendererPlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/BloomPlugin.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 plugins/troika-text/src/TroikaTextPlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/SSContactShadowsPlugin.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 plugins/tweakpane-editor/src/HierarchyUiPlugin.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 plugins/webgi-plugins/src/utils/Reflector2.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 plugins/webgi-plugins/src/plugins/postprocessing/TemporalAAPlugin.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 plugins/webgi-plugins/src/utils/RandomizedDirectionalLight.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 plugins/network/src/AWSClientPlugin.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file plugins/blend-importer/src/BlendLoadPlugin.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.
+ 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×11
Low cohesion: GLTFWriter2 (LCOM4 5) src/assetmanager/export/GLTFWriter2.ts:8— GLTFWriter2's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PopmotionPlugin (LCOM4 5) src/plugins/animation/PopmotionPlugin.ts:42— PopmotionPlugin's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LineMaterial2 (LCOM4 5) src/core/material/LineMaterial2.ts:33— LineMaterial2's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AScreenPassExtensionPlugin (LCOM4 5) src/plugins/postprocessing/AScreenPassExtensionPlugin.ts:19— AScreenPassExtensionPlugin's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TilesRendererPlugin (LCOM4 4) plugins/3d-tiles-renderer/src/TilesRendererPlugin.ts:47— TilesRendererPlugin's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BloomPlugin (LCOM4 4) plugins/webgi-plugins/src/plugins/postprocessing/BloomPlugin.ts:47— BloomPlugin's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DepthOfFieldPlugin (LCOM4 4) plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts:53— DepthOfFieldPlugin's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SSReflectionPluginPass (LCOM4 4) plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:215— SSReflectionPluginPass's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SSGIPlugin (LCOM4 4) plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:63— SSGIPlugin's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SSGIPluginPass (LCOM4 4) plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:221— SSGIPluginPass's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FrameFadePlugin (LCOM4 4) src/plugins/pipeline/FrameFadePlugin.ts:19— FrameFadePlugin's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
MethodTooLong: TransformControlsGizmo.constructor REDACTED:794— MethodTooLong — constructor runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TransformControlsGizmo.updateMatrixWorld REDACTED:1208— MethodTooLong — updateMatrixWorld runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PivotControls._buildHandles src/three/controls/PivotControls.ts:278— MethodTooLong — _buildHandles runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExtendedRenderPass.render src/postprocessing/ExtendedRenderPass.ts:111— MethodTooLong — render runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ThreeViewer.constructor src/viewer/ThreeViewer.ts:466— MethodTooLong — constructor 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.
MethodTooLong: Reflector2.constructor plugins/webgi-plugins/src/utils/Reflector2.ts:60— MethodTooLong — constructor runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GLTFMaterialExtrasExtension.Export src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:157— MethodTooLong — Export runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TransformControls.pointerMove REDACTED:277— MethodTooLong — pointerMove runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: TubeShapeGeometry.constructor src/core/geometry/TubeShapeGeometry.ts:50— MethodTooLong — constructor runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: ShadowMapBaker.updateShadow plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:207— MethodTooLong — updateShadow runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: viewer/ThreeViewer.ts src/viewer/ThreeViewer.ts— FileTooLong — 938 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: ThreeViewer (316-1807). The bar is 500 significant lines; this is 438 over it, 1.88× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 313 over it, 1.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: utils/serialization.ts src/utils/serialization.ts— FileTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 161 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: interaction/PickingPlugin.ts src/plugins/interaction/PickingPlugin.ts— FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: PickingPlugin (42-988). The bar is 500 significant lines; this is 136 over it, 1.27× 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: controls/PivotControls.ts src/three/controls/PivotControls.ts— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: PivotControls (121-876). The bar is 500 significant lines; this is 95 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: rendering/CascadedShadowsPlugin.ts src/plugins/rendering/CascadedShadowsPlugin.ts— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: CascadedShadowsPlugin (72-875). The bar is 500 significant lines; this is 64 over it, 1.13× 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: src/timeline.tsx plugins/timeline-ui/src/timeline.tsx— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: RenderManager (64-816). The bar is 500 significant lines; this is 22 over it, 1.04× 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: assetmanager/AssetManager.ts src/assetmanager/AssetManager.ts— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: AssetManager (105-701). The bar is 500 significant lines; this is 13 over it, 1.03× 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×9
Untrusted text written into markup unescaped plugins/svg-renderer/src/ThreeSVGRendererPlugin.ts:322— `svg.node.outerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped plugins/tweakpane-editor/src/util-buttons.ts:154— `collapse` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped plugins/tweakpane-editor/src/util-buttons.ts:158— `expand` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/plugins/extras/MeshOptSimplifyModifierPlugin.ts:45— ``
import { MeshoptSimplifier } from ${JSON.stringify(MeshOptSimplifyModifierPlugin.SIMPLIFIER_URL)};
MeshoptSimplifie…` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/plugins/import/GLTFMeshOptDecodePlugin.ts:42— ``
import { MeshoptDecoder } from ${JSON.stringify(GLTFMeshOptDecodePlugin.DECODER_URL)};
window.MeshoptDecoder = Mesh…` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/plugins/interaction/InteractionPromptPlugin.ts:188— `this.pointerIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/plugins/interaction/LoadingScreenPlugin.ts:179— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/plugins/interaction/LoadingScreenPlugin.ts:181— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/utils/CustomContextMenu.ts:55— `styles` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Boundary violation [package:third-party-deep-import] plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:1— plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:1 imports uiconfig-blueprint/lib/esm, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] plugins/configurator/src/GridItemList.ts:3— plugins/configurator/src/GridItemList.ts:3 imports tippy.js/dist/tippy.css?inline, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] plugins/tweakpane-editor/src/TweakpaneEditorPlugin.ts:15— plugins/tweakpane-editor/src/TweakpaneEditorPlugin.ts:15 imports tippy.js/dist/tippy.css?inline, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] plugins/tweakpane/src/TweakpaneUiPlugin.ts:2— plugins/tweakpane/src/TweakpaneUiPlugin.ts:2 imports uiconfig-tweakpane/lib/esm, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/three/Threejs.ts:219— src/three/Threejs.ts:219 imports three/src/constants.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-cross-package-internals] tests/unit/blend-importer-material.test.ts:3— tests/unit/blend-importer-material.test.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../../plugins/blend-importer/src/loader/material) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/unit/blend-importer-material.test.ts:4— tests/unit/blend-importer-material.test.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../../plugins/blend-importer/src/loader/ctx) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×6
Animation without a prefers-reduced-motion guard website/.vitepress/theme/custom.css:215— `.model-tab` moves (`transition: background 0.3s, transform 0.3s, color 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard website/.vitepress/theme/custom.css:277— `.loadingScreenLogoElement` moves (`animation: rotation1 4s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/plugins/interaction/LoadingScreenPlugin.css:18— `#assetManagerLoadingScreen` moves (`transition: opacity 0.5s ease-in-out, min-width 0.5s, min-height 0.5s, bottom 0.5s, right 0.5s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/plugins/interaction/loaders/spinner1.css:9— `.loader` moves (`animation: rotation 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard plugins/tweakpane-editor/src/TweakpaneEditorPlugin.css:89— `.button-bar-selected:before` moves (`transition: width 0.25s, left 0.25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard plugins/timeline-ui/src/timeline.css:69— `.timeline-card` moves (`transition: transform 0.2s ease, opacity 0.2s ease, box-shadow 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
TooManyMethods: ThreeViewer src/viewer/ThreeViewer.ts:315— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.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.
TooManyMethods: PickingPlugin src/plugins/interaction/PickingPlugin.ts:42— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Object3DManager src/assetmanager/Object3DManager.ts:48— 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: AssetImporter src/assetmanager/AssetImporter.ts:71— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RootScene src/core/object/RootScene.ts:38— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: AnimationObjectPlugin src/plugins/animation/AnimationObjectPlugin.ts:29— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×6
Recursive walk over a caller-supplied document has no depth cap src/utils/serialization.ts:520— `copyUserData` is exported and takes `source: any` from its caller, and it calls itself at line 520 (`copyUserData`) with a piece of `source` — and nowhere in `copyUserData` 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 `copyUserData` 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 src/plugins/extras/components/typeSystem.ts:80— `GetType` is exported and takes `v: any` from its caller, and it calls itself at line 80 (`this.GetType`) with a piece of `v` (and at line 111) — and nowhere in `GetType` 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 `GetType` 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 src/plugins/extras/components/typeSystem.ts:132— `TypeToString` is exported and takes `type: TypedType` from its caller, and it calls itself at line 132 (`this.TypeToString`) with a piece of `type` (and at line 135, line 138) — and nowhere in `TypeToString` 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 `TypeToString` 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 src/plugins/extras/components/typeSystem.ts:164— `CanAssign` is exported and takes `src: TypedType` from its caller, and it calls itself at line 164 (`this.CanAssign`) with a piece of `src` (and at line 181, line 187, line 195) — and nowhere in `CanAssign` 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 `CanAssign` 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 src/assetmanager/gltf/GLTFViewerConfigExtension.ts:31— `ImportViewerConfig` is exported and takes `scene: any` from its caller, and it calls itself at line 31 (`this.ImportViewerConfig`) with a piece of `scene` — and nowhere in `ImportViewerConfig` 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 `ImportViewerConfig` 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 plugins/blend-importer/src/loader/bakeGetters.ts:19— `bakeGetters` is exported, takes a document from its caller (line 1) and hands it to `toPlainObject`, which calls itself at line 19 (`toPlainObject`) with a piece of `source` (and at line 41) — and nowhere in `toPlainObject` 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 `toPlainObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×5
Focus outline removed in CSS without a :focus replacement website/.vitepress/theme/components/EffectToggle.vue:82— `.switch input[type="checkbox"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement plugins/timeline-ui/src/timeline.css:312— `.timeline-controls-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement plugins/tweakpane-editor/src/HierarchyUiPlugin.ts:82— `.css-in-js .treejs .treejs-node-selected > .treejs-label` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/shadertoy-player/script.ts:416— `.css-in-js *:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/shadertoy-player/script.ts:444— `.css-in-js .editor-container textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
FunctionTooLong: timeline.Timeline plugins/timeline-ui/src/timeline.tsx:413— FunctionTooLong — Timeline runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: webgi-showcase.init website/public/scripts/webgi-showcase.js:73— FunctionTooLong — init runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: image-ui.makeSamplerUi src/ui/image-ui.ts:21— FunctionTooLong — makeSamplerUi runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: IObjectUi.makeIObject3DUiConfig src/core/object/IObjectUi.ts:110— FunctionTooLong — makeIObject3DUiConfig runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: material.createMaterial plugins/blend-importer/src/loader/material.ts:162— FunctionTooLong — createMaterial runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
ClassTooLong: CascadedShadowsPlugin src/plugins/rendering/CascadedShadowsPlugin.ts:72— ClassTooLong — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 73 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RenderManager REDACTED:62— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RootScene src/core/object/RootScene.ts:38— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AssetImporter src/assetmanager/AssetImporter.ts:71— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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.
`async` callback passed to `forEach` src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:68— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` plugins/gaussian-splatting/src/three-gaussian-splat/ThreeGaussianSplatPlugin.ts:45— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` plugins/gaussian-splatting/src/three-gaussian-splat/ThreeGaussianSplatPlugin.ts:50— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
AC1 · Text alternatives· <canvas> without a text alternative · ×2
<canvas> without a text alternative src/three/utils/texture.ts:71— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative website/.vitepress/theme/components/WebgiShowcase.vue:27— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
Floating npm dependency: ts-browser-helpers — `ts-browser-helpers` is declared as `>=0.20.0` in package.json, which names no releasable version: `>=0.20.0` is an open range with no upper bound on the major. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: uiconfig.js — `uiconfig.js` is declared as `>=0.3.1` in package.json, which names no releasable version: `>=0.3.1` is an open range with no upper bound on the major. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
HackComment src/viewer/ViewerRenderManager.ts:67— // hack. used in WebGLRenderer.js — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment src/core/material/PhysicalMaterial.ts:193— // hack for ui — 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.
Duplicated block (43 lines × 2 locations) src/core/light/PointLight2.ts:49— src/core/light/PointLight2.ts:49 · src/core/light/SpotLight2.ts:52 — 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 (43 lines × 2 locations) src/plugins/interaction/PivotControlsPlugin.ts:30— src/plugins/interaction/PivotControlsPlugin.ts:30 · src/plugins/interaction/TransformControlsPlugin.ts:20 — 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: initDecoder src/assetmanager/import/DRACOLoader2.ts:79— `initDecoder` 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: getLink plugins/network/src/TransfrSharePlugin.ts:49— `getLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Swallowed exception (empty catch) src/three/utils/cache.ts:76— `.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) plugins/blend-importer/src/loader/bakeGetters.ts:42— 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.
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track src/assetmanager/import/VideoLoader.ts:38— Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
Low contrast colour pair in CSS (3.6:1) plugins/tweakpane-editor/src/HierarchyUiPlugin.ts:79— `.treejs .treejs-node-selected > .treejs-label` sets color: #eee on background-color: #067ce9 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
GLTFMaterialExtrasExtension.Export (cyclomatic 128) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:157— GLTFMaterialExtrasExtension.Export has cyclomatic complexity 128 (threshold 15). Of this number, 111 points are the body's own statements and 17 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
material.createMaterial (cyclomatic 86) plugins/blend-importer/src/loader/material.ts:162— material.createMaterial has cyclomatic complexity 86 (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.
GLTFMaterialExtrasExtension.Import (cyclomatic 80) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:17— GLTFMaterialExtrasExtension.Import has cyclomatic complexity 80 (threshold 15). Most of this is not in the body itself: 1 of the 80 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 25, 19, 124). 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.
geometry.createBufferGeometry (cyclomatic 78) plugins/blend-importer/src/loader/geometry.ts:187— geometry.createBufferGeometry has cyclomatic complexity 78 (threshold 15). Of this number, 75 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransformControls.pointerMove (cyclomatic 62) REDACTED:277— TransformControls.pointerMove has cyclomatic complexity 62 (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.
TransformControlsGizmo.updateMatrixWorld (cyclomatic 61) REDACTED:1208— TransformControlsGizmo.updateMatrixWorld has cyclomatic complexity 61 (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.
MetaImporter.ImportMeta (cyclomatic 61) src/utils/serialization.ts:699— MetaImporter.ImportMeta has cyclomatic complexity 61 (threshold 15). Of this number, 59 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ThreeViewer.constructor (cyclomatic 54) src/viewer/ThreeViewer.ts:466— ThreeViewer.constructor has cyclomatic complexity 54 (threshold 15). Of this number, 42 points are the body's own statements and 12 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GLTFAnimationPlugin._postFrame (cyclomatic 53) src/plugins/animation/GLTFAnimationPlugin.ts:434— GLTFAnimationPlugin._postFrame has cyclomatic complexity 53 (threshold 15). Of this number, 31 points are the body's own statements and 22 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GLTFLoader2.transform (cyclomatic 50) src/assetmanager/import/GLTFLoader2.ts:187— GLTFLoader2.transform has cyclomatic complexity 50 (threshold 15). Of this number, 31 points are the body's own statements and 19 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.
geometry.createBufferGeometryFromAttributes (cyclomatic 47) plugins/blend-importer/src/loader/geometry.ts:96— geometry.createBufferGeometryFromAttributes has cyclomatic complexity 47 (threshold 15). Of this number, 43 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
timeline.TimelineCard (cyclomatic 41) plugins/timeline-ui/src/timeline.tsx:29— timeline.TimelineCard has cyclomatic complexity 41 (threshold 15). Of this number, 19 points are the body's own statements and 22 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExtendedRenderPass.render (cyclomatic 41) src/postprocessing/ExtendedRenderPass.ts:111— ExtendedRenderPass.render has cyclomatic complexity 41 (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.
assetExportHook.assetExportHook (cyclomatic 40) src/assetmanager/export/assetExportHook.ts:29— assetExportHook.assetExportHook has cyclomatic complexity 40 (threshold 15). Of this number, 19 points are the body's own statements and 21 belong to 7 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.
tpImageInputGenerator.proxyGetValue (cyclomatic 39) plugins/tweakpane/src/tpImageInputGenerator.ts:49— tpImageInputGenerator.proxyGetValue has cyclomatic complexity 39 (threshold 15). Of this number, 35 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetManager.processRawStartHook (cyclomatic 39) src/assetmanager/AssetManager.ts:703— AssetManager.processRawStartHook has cyclomatic complexity 39 (threshold 15). Of this number, 28 points are the body's own statements and 11 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.
timeline.Timeline (cyclomatic 35) plugins/timeline-ui/src/timeline.tsx:413— timeline.Timeline has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 586, 639, 484, …). 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.
ObjectPicker.setSelected (cyclomatic 35) src/three/utils/ObjectPicker.ts:148— ObjectPicker.setSelected has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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.
iObjectCommons.upgradeObject3D (cyclomatic 34) src/core/object/iObjectCommons.ts:696— iObjectCommons.upgradeObject3D has cyclomatic complexity 34 (threshold 15). Of this number, 33 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.
lerp.lerpParams (cyclomatic 32) src/utils/lerp.ts:126— lerp.lerpParams has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetManager.loadImported (cyclomatic 32) src/assetmanager/AssetManager.ts:155— AssetManager.loadImported has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PickingPlugin._onKeyDown (cyclomatic 32) src/plugins/interaction/PickingPlugin.ts:198— PickingPlugin._onKeyDown has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tpImageInputGenerator.proxySetValue (cyclomatic 31) plugins/tweakpane/src/tpImageInputGenerator.ts:168— tpImageInputGenerator.proxySetValue has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PivotControls._onDragMove (cyclomatic 31) src/three/controls/PivotControls.ts:725— PivotControls._onDragMove has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetImporter._loadFile (cyclomatic 31) src/assetmanager/AssetImporter.ts:367— AssetImporter._loadFile has cyclomatic complexity 31 (threshold 15). Of this number, 26 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.
AssetImporter.processRaw (cyclomatic 31) src/assetmanager/AssetImporter.ts:523— AssetImporter.processRaw has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tpImageInputGenerator.downloadImage (cyclomatic 30) plugins/tweakpane/src/tpImageInputGenerator.ts:238— tpImageInputGenerator.downloadImage has cyclomatic complexity 30 (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.
LineHelper.update (cyclomatic 30) src/three/widgets/LineHelper.ts:92— LineHelper.update has cyclomatic complexity 30 (threshold 15). Of this number, 25 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.
decorators.bindToValue.<returned closure> (cyclomatic 29) src/three/utils/decorators.ts:141— decorators.bindToValue.<returned closure> has cyclomatic complexity 29 (threshold 15). Of this number, 20 points are the body's own statements and 9 belong to one function item 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.
AssetImporter.importAsset (cyclomatic 29) src/assetmanager/AssetImporter.ts:233— AssetImporter.importAsset has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransformControlsPlugin.onAdded (cyclomatic 29) src/plugins/interaction/TransformControlsPlugin.ts:86— TransformControlsPlugin.onAdded has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 108, 155, 92, …). 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.
AnimationObjectPlugin.setupUiConfigButton (cyclomatic 29) src/plugins/animation/AnimationObjectPlugin.ts:332— AnimationObjectPlugin.setupUiConfigButton has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
lerp.lerpTexture (cyclomatic 28) src/utils/lerp.ts:51— lerp.lerpTexture has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
webgi-showcase.init (cyclomatic 28) website/public/scripts/webgi-showcase.js:73— webgi-showcase.init has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 3 of the 28 points are its own statements and the rest belongs to 16 function items inside it that branch (onMouseMove, loadModel, setSplit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TroikaTextPlugin.updateText (cyclomatic 27) plugins/troika-text/src/TroikaTextPlugin.ts:96— TroikaTextPlugin.updateText has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssetManager._loadObjectDependencies (cyclomatic 27) src/assetmanager/AssetManager.ts:415— AssetManager._loadObjectDependencies has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GBufferMaterial.onBeforeRender (cyclomatic 27) src/plugins/pipeline/GBufferMaterial.ts:65— GBufferMaterial.onBeforeRender has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PivotControlsPlugin.onAdded (cyclomatic 27) src/plugins/interaction/PivotControlsPlugin.ts:96— PivotControlsPlugin.onAdded has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 118, 165, 103, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
setupComponent.generateComponentPropertyUi (cyclomatic 27) src/plugins/extras/components/setupComponent.ts:276— setupComponent.generateComponentPropertyUi has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 303, uiC, a function literal at line 325). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GLTFWriter2.processTexture (cyclomatic 26) src/assetmanager/export/GLTFWriter2.ts:184— GLTFWriter2.processTexture has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IObjectUi.makeIObject3DUiConfig (cyclomatic 26) src/core/object/IObjectUi.ts:110— IObjectUi.makeIObject3DUiConfig has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 117, 197, 244, …). 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.
PopmotionPlugin.animate (cyclomatic 26) src/plugins/animation/PopmotionPlugin.ts:193— PopmotionPlugin.animate has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CanvasSnapshotPlugin._getFile (cyclomatic 26) src/plugins/export/CanvasSnapshotPlugin.ts:62— CanvasSnapshotPlugin._getFile 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.
TypeSystem.GetType (cyclomatic 26) src/plugins/extras/components/typeSystem.ts:70— TypeSystem.GetType has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Box3B.expandByObject (cyclomatic 25) src/three/math/Box3B.ts:8— Box3B.expandByObject has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CurveUiHelper.createCurveTypeDropdown.setValue (cyclomatic 25) src/plugins/geometry/helpers/CurveUiHelper.ts:267— CurveUiHelper.createCurveTypeDropdown.setValue has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TypeSystem.CanAssign (cyclomatic 24) src/plugins/extras/components/typeSystem.ts:149— TypeSystem.CanAssign 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.
iCameraCommons.upgradeCamera (cyclomatic 23) src/core/object/iCameraCommons.ts:260— iCameraCommons.upgradeCamera 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.
MaterialConfiguratorBasePlugin._preFrame (cyclomatic 23) src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:215— MaterialConfiguratorBasePlugin._preFrame has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ThreeViewer._animationLoop (cyclomatic 23) src/viewer/ThreeViewer.ts:802— ThreeViewer._animationLoop has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, 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.
decompress.detectBlendCompression (cyclomatic 22) plugins/blend-importer/src/decompress.ts:11— decompress.detectBlendCompression has cyclomatic complexity 22 (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.
ThreeGpuPathTracerPlugin.onAdded (cyclomatic 22) plugins/path-tracing/src/ThreeGpuPathTracerPlugin.ts:121— ThreeGpuPathTracerPlugin.onAdded has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 172, 149, 154, …). 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.
AnimationObject._onAccessChanged (cyclomatic 22) src/utils/AnimationObject.ts:323— AnimationObject._onAccessChanged has cyclomatic complexity 22 (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.
ThreeViewer.fromJSON (cyclomatic 22) src/viewer/ThreeViewer.ts:1431— ThreeViewer.fromJSON has cyclomatic complexity 22 (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.
TransformControlsPlane.updateMatrixWorld (cyclomatic 21) REDACTED:1542— TransformControlsPlane.updateMatrixWorld has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
GLTFViewerConfigExtension.BundleArrayBuffers (cyclomatic 21) src/assetmanager/gltf/GLTFViewerConfigExtension.ts:196— GLTFViewerConfigExtension.BundleArrayBuffers has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Object3DManager.onPostFrame (cyclomatic 21) src/assetmanager/Object3DManager.ts:73— Object3DManager.onPostFrame has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
material.packedTexture (cyclomatic 20) plugins/blend-importer/src/loader/material.ts:69— material.packedTexture has cyclomatic complexity 20 (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.
ShadowMapBaker.updateShadow (cyclomatic 20) plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:207— ShadowMapBaker.updateShadow has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: 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.
Rhino3dmLoader2._useMaterialSource (cyclomatic 20) src/assetmanager/import/Rhino3dmLoader2.ts:84— Rhino3dmLoader2._useMaterialSource has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
EntityComponentPlugin.registerComponent (cyclomatic 20) src/plugins/extras/EntityComponentPlugin.ts:378— EntityComponentPlugin.registerComponent has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
camera.createCamera (cyclomatic 19) plugins/blend-importer/src/loader/camera.ts:4— camera.createCamera 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.
bbox.computeScreenSpaceBoundingBox (cyclomatic 19) src/three/utils/bbox.ts:3— bbox.computeScreenSpaceBoundingBox 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.
ObjectPicker._hitObject (cyclomatic 19) src/three/utils/ObjectPicker.ts:327— ObjectPicker._hitObject 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.
CameraViewPlugin.animateToView (cyclomatic 19) src/plugins/animation/CameraViewPlugin.ts:228— CameraViewPlugin.animateToView has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DynamicImportPlugin.loadPlugin (cyclomatic 19) src/plugins/extras/DynamicImportPlugin.ts:65— DynamicImportPlugin.loadPlugin has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MaterialExtender.RegisterExtensions (cyclomatic 19) src/materials/MaterialExtender.ts:63— MaterialExtender.RegisterExtensions has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
geometry.createBufferGeometryOld (cyclomatic 18) plugins/blend-importer/src/loader/geometry.ts:464— geometry.createBufferGeometryOld has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
texture.texImageToCanvas (cyclomatic 18) src/three/utils/texture.ts:60— texture.texImageToCanvas has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ObjectPicker.checkIntersection (cyclomatic 18) src/three/utils/ObjectPicker.ts:370— ObjectPicker.checkIntersection has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
serialization.copyUserData (cyclomatic 18) src/utils/serialization.ts:508— serialization.copyUserData has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MeshNormalMaterialOverride.onBeforeRender (cyclomatic 18) src/plugins/pipeline/NormalBufferPlugin.ts:165— MeshNormalMaterialOverride.onBeforeRender has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ShapeTubeExtrudePlugin.ConvertGeometryToFlatShape (cyclomatic 18) src/plugins/geometry/ShapeTubeExtrudePlugin.ts:192— ShapeTubeExtrudePlugin.ConvertGeometryToFlatShape has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GenericExtension.read (cyclomatic 17) plugins/gltf-transform/src/GLTFDracoExporterBase.ts:271— GenericExtension.read has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 276, 305, 314, …). 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.
tpImageInputGenerator.tpImageInputGenerator.<returned closure> (cyclomatic 17) plugins/tweakpane/src/tpImageInputGenerator.ts:351— tpImageInputGenerator.tpImageInputGenerator.<returned closure> has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 360, 385, 373). 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.
decorators.matDefine.<returned closure> (cyclomatic 17) src/three/utils/decorators.ts:70— decorators.matDefine.<returned closure> has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function item 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.
Object3DManager.registerObject (cyclomatic 17) src/assetmanager/Object3DManager.ts:123— Object3DManager.registerObject 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.
RenderManager.blit (cyclomatic 17) REDACTED:445— RenderManager.blit has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
PickingPlugin.refreshUiChildren (cyclomatic 17) src/plugins/interaction/PickingPlugin.ts:839— PickingPlugin.refreshUiChildren has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GLTFKHRMaterialVariantsPlugin.applyVariant (cyclomatic 17) src/plugins/extras/GLTFKHRMaterialVariantsPlugin.ts:71— GLTFKHRMaterialVariantsPlugin.applyVariant has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RootScene.loadModelRoot (cyclomatic 17) src/core/object/RootScene.ts:304— RootScene.loadModelRoot has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
extensions.videoTextureExt.update (cyclomatic 16) plugins/timeline-ui/src/extensions.ts:287— extensions.videoTextureExt.update 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.
OutlinePlugin.onAdded (cyclomatic 16) plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts:175— OutlinePlugin.onAdded has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 202, 186). 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.
PivotControls.updateHandleVisibility (cyclomatic 16) src/three/controls/PivotControls.ts:465— PivotControls.updateHandleVisibility 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.
FirstPersonControls2.update (cyclomatic 16) src/three/controls/FirstPersonControls2.ts:260— FirstPersonControls2.update 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.
MaterialManager.convertToIMaterial (cyclomatic 16) src/assetmanager/MaterialManager.ts:170— MaterialManager.convertToIMaterial 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.
GLTFLoader2.parse (cyclomatic 16) src/assetmanager/import/GLTFLoader2.ts:142— GLTFLoader2.parse has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 144, 164, 176). 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.
GLTFLoader2.gltfViewerParser (cyclomatic 16) src/assetmanager/import/GLTFLoader2.ts:316— GLTFLoader2.gltfViewerParser has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 318, 385, 333, …). 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.
Object3DManager._unregisterTexture (cyclomatic 16) src/assetmanager/Object3DManager.ts:484— Object3DManager._unregisterTexture 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.
MetaImporter.LoadRootPathTextures (cyclomatic 16) src/utils/serialization.ts:860— MetaImporter.LoadRootPathTextures has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 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.
sortPasses.sortPasses (cyclomatic 16) src/postprocessing/sortPasses.ts:4— sortPasses.sortPasses has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UndoManagerPlugin.createBindingsProxy (cyclomatic 16) src/plugins/interaction/UndoManagerPlugin.ts:181— UndoManagerPlugin.createBindingsProxy has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PopmotionPlugin._postFrame (cyclomatic 16) src/plugins/animation/PopmotionPlugin.ts:73— PopmotionPlugin._postFrame has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DuplicateTracker.applyOffset (cyclomatic 16) src/plugins/interaction/DuplicateTracker.ts:50— DuplicateTracker.applyOffset 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.
TransformControls2._keyDownListener (cyclomatic 16) src/plugins/interaction/TransformControlsPlugin.ts:223— TransformControls2._keyDownListener has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
HDRiGroundPlugin.setDirty (cyclomatic 16) src/plugins/extras/HDRiGroundPlugin.ts:56— HDRiGroundPlugin.setDirty 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.
Object3DWidgetsPlugin._createWidget (cyclomatic 16) src/plugins/extras/Object3DWidgetsPlugin.ts:110— Object3DWidgetsPlugin._createWidget has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, 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.
EntityComponentPlugin._objectRemove (cyclomatic 16) src/plugins/extras/EntityComponentPlugin.ts:575— EntityComponentPlugin._objectRemove has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 596, 588). 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.
AssetExporter.processBeforeExport (cyclomatic 16) src/assetmanager/AssetExporter.ts:144— AssetExporter.processBeforeExport 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.
Deprecated: eslint package.json:132— eslint 8.57.1, 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.
TodoComment repeated across 22 files src/viewer/ThreeViewer.ts:103— The identical TodoComment appears in 22 files (32 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 32 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// todo". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
updateMatrixWorld (cognitive 148) REDACTED:1208— updateMatrixWorld has cognitive complexity 148 (threshold 15). Drivers by points: if/else 42 (127 pts), boolean chains 17, ternaries 3, loops 1 (nesting depth added 85). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GLTFMaterialExtrasExtension.Import (cognitive 137) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:17— GLTFMaterialExtrasExtension.Import has cognitive complexity 137 (threshold 15). Drivers by points: if/else 62 (123 pts), boolean chains 9, ternaries 2 (4 pts), loops 1 (nesting depth added 63). None of this is in the body itself: all 137 points belong to 3 function literals inside it that branch (lines 25, 19, 124). 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.
geometry.createBufferGeometry (cognitive 136) plugins/blend-importer/src/loader/geometry.ts:187— geometry.createBufferGeometry has cognitive complexity 136 (threshold 15). Drivers by points: if/else 33 (67 pts), boolean chains 27, loops 9 (26 pts), ternaries 7 (16 pts) (nesting depth added 60). Of this number, 132 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFMaterialExtrasExtension.Export (cognitive 134) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:157— GLTFMaterialExtrasExtension.Export has cognitive complexity 134 (threshold 15). Drivers by points: if/else 70 (78 pts), boolean chains 55, ternaries 1 (nesting depth added 8). Of this number, 109 points are the body's own statements and 25 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
pointerMove (cognitive 121) REDACTED:277— pointerMove has cognitive complexity 121 (threshold 15). Drivers by points: if/else 44 (102 pts), boolean chains 15, ternaries 2 (4 pts) (nesting depth added 60). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
material.createMaterial (cognitive 120) plugins/blend-importer/src/loader/material.ts:162— material.createMaterial has cognitive complexity 120 (threshold 15). Drivers by points: if/else 38 (76 pts), boolean chains 25, ternaries 10 (16 pts), loops 1 (3 pts) (nesting depth added 46). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetManager.processRawStartHook (cognitive 108) src/assetmanager/AssetManager.ts:703— AssetManager.processRawStartHook has cognitive complexity 108 (threshold 15). Drivers by points: if/else 22 (48 pts), ternaries 8 (46 pts), boolean chains 7, loops 3 (7 pts) (nesting depth added 68). Of this number, 82 points are the body's own statements and 26 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MetaImporter.ImportMeta (cognitive 86) src/utils/serialization.ts:699— MetaImporter.ImportMeta has cognitive complexity 86 (threshold 15). Drivers by points: if/else 34 (61 pts), boolean chains 15, loops 7 (9 pts), ternaries 1 (nesting depth added 29). Of this number, 84 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFLoader2.transform (cognitive 80) src/assetmanager/import/GLTFLoader2.ts:187— GLTFLoader2.transform has cognitive complexity 80 (threshold 15). Drivers by points: if/else 31 (54 pts), loops 5 (14 pts), boolean chains 8, ternaries 3 (4 pts) (nesting depth added 33). Of this number, 51 points are the body's own statements and 29 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.
assetExportHook.assetExportHook (cognitive 75) src/assetmanager/export/assetExportHook.ts:29— assetExportHook.assetExportHook has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (48 pts), boolean chains 16, ternaries 5 (11 pts) (nesting depth added 34). Of this number, 30 points are the body's own statements and 45 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThreeViewer._animationLoop (cognitive 74) src/viewer/ThreeViewer.ts:802— ThreeViewer._animationLoop has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (61 pts), error handling 1 (6 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 50). Of this number, 68 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tpImageInputGenerator.proxyGetValue (cognitive 66) plugins/tweakpane/src/tpImageInputGenerator.ts:49— tpImageInputGenerator.proxyGetValue has cognitive complexity 66 (threshold 15). Drivers by points: if/else 26 (56 pts), boolean chains 10 (nesting depth added 30). Of this number, 58 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
geometry.createBufferGeometryFromAttributes (cognitive 61) plugins/blend-importer/src/loader/geometry.ts:96— geometry.createBufferGeometryFromAttributes has cognitive complexity 61 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 16, loops 6 (15 pts), ternaries 4 (7 pts) (nesting depth added 25). Of this number, 58 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThreeViewer.constructor (cognitive 60) src/viewer/ThreeViewer.ts:466— ThreeViewer.constructor has cognitive complexity 60 (threshold 15). Drivers by points: if/else 34 (42 pts), boolean chains 15, ternaries 1 (2 pts), loops 1 (nesting depth added 9). Of this number, 46 points are the body's own statements and 14 belong to 5 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PivotControls._onDragMove (cognitive 57) src/three/controls/PivotControls.ts:725— PivotControls._onDragMove has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (49 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeSystem.GetType (cognitive 54) src/plugins/extras/components/typeSystem.ts:70— TypeSystem.GetType has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (45 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GLTFAnimationPlugin._postFrame (cognitive 52) src/plugins/animation/GLTFAnimationPlugin.ts:434— GLTFAnimationPlugin._postFrame has cognitive complexity 52 (threshold 15). Drivers by points: if/else 30 (36 pts), boolean chains 15, ternaries 1 (nesting depth added 6). Of this number, 34 points are the body's own statements and 18 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Box3B.expandByObject (cognitive 51) src/three/math/Box3B.ts:8— Box3B.expandByObject has cognitive complexity 51 (threshold 15). Drivers by points: if/else 20 (40 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtendedRenderPass.render (cognitive 51) src/postprocessing/ExtendedRenderPass.ts:111— ExtendedRenderPass.render has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 16, ternaries 4 (10 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lerp.lerpParams (cognitive 47) src/utils/lerp.ts:126— lerp.lerpParams has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 10, ternaries 1 (2 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GBufferMaterial.onBeforeRender (cognitive 46) src/plugins/pipeline/GBufferMaterial.ts:65— GBufferMaterial.onBeforeRender has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (37 pts), ternaries 4 (8 pts), boolean chains 1 (nesting depth added 19). Of this number, 38 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFWriter2.processTexture (cognitive 45) src/assetmanager/export/GLTFWriter2.ts:184— GLTFWriter2.processTexture has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (38 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialConfiguratorBasePlugin._preFrame (cognitive 45) src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:215— MaterialConfiguratorBasePlugin._preFrame has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 6 (19 pts), if/else 7 (17 pts), boolean chains 8, loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PickingPlugin.refreshUiChildren (cognitive 44) src/plugins/interaction/PickingPlugin.ts:839— PickingPlugin.refreshUiChildren has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (26 pts), ternaries 5 (16 pts), boolean chains 2 (nesting depth added 27). Of this number, 40 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TypeSystem.CanAssign (cognitive 44) src/plugins/extras/components/typeSystem.ts:149— TypeSystem.CanAssign has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
timeline.TimelineCard (cognitive 42) plugins/timeline-ui/src/timeline.tsx:29— timeline.TimelineCard has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 18, if/else 12 (18 pts), ternaries 6 (nesting depth added 6). Most of this is not in the body itself: 14 of the 42 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 63, 38, 43, …). 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.
AnimationObjectPlugin.setupUiConfigButton (cognitive 42) src/plugins/animation/AnimationObjectPlugin.ts:332— AnimationObjectPlugin.setupUiConfigButton has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (30 pts), boolean chains 8, ternaries 2 (3 pts), loops 1 (nesting depth added 12). Most of this is not in the body itself: 13 of the 42 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 344, 399, 358). 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.
setupComponent.generateComponentPropertyUi (cognitive 42) src/plugins/extras/components/setupComponent.ts:276— setupComponent.generateComponentPropertyUi has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 6 (11 pts), boolean chains 7 (nesting depth added 21). Most of this is not in the body itself: 7 of the 42 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 303, uiC, a function literal at line 325). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
timeline.Timeline (cognitive 41) plugins/timeline-ui/src/timeline.tsx:413— timeline.Timeline has cognitive complexity 41 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 12, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 586, 639, 484, …). 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.
AssetManager._loadObjectDependencies (cognitive 40) src/assetmanager/AssetManager.ts:415— AssetManager._loadObjectDependencies has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (29 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 16). Of this number, 37 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bbox.computeScreenSpaceBoundingBox (cognitive 39) src/three/utils/bbox.ts:3— bbox.computeScreenSpaceBoundingBox has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 4 (10 pts), boolean chains 5 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Object3DManager.onPostFrame (cognitive 39) src/assetmanager/Object3DManager.ts:73— Object3DManager.onPostFrame has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 7, loops 1 (nesting depth added 19). Of this number, 31 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.
LineHelper.update (cognitive 39) src/three/widgets/LineHelper.ts:92— LineHelper.update has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 5 (8 pts), boolean chains 6, loops 4 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetManager.loadImported (cognitive 38) src/assetmanager/AssetManager.ts:155— AssetManager.loadImported has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 8, ternaries 3 (4 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iObjectCommons.upgradeObject3D (cognitive 38) src/core/object/iObjectCommons.ts:696— iObjectCommons.upgradeObject3D has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 10, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 4). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
PickingPlugin._onKeyDown (cognitive 37) src/plugins/interaction/PickingPlugin.ts:198— PickingPlugin._onKeyDown has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 12, ternaries 4 (10 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.
AssetImporter.processRaw (cognitive 36) src/assetmanager/AssetImporter.ts:523— AssetImporter.processRaw has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 9, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanvasSnapshotPlugin._getFile (cognitive 36) src/plugins/export/CanvasSnapshotPlugin.ts:62— CanvasSnapshotPlugin._getFile has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 11, loops 2 (6 pts) (nesting depth added 7). 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.
geometry.createBufferGeometryOld (cognitive 35) plugins/blend-importer/src/loader/geometry.ts:464— geometry.createBufferGeometryOld has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (8 pts), boolean chains 4, ternaries 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sortPasses.sortPasses (cognitive 34) src/postprocessing/sortPasses.ts:4— sortPasses.sortPasses has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (20 pts), ternaries 2 (8 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 19). Of this number, 25 points are the body's own statements and 9 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.
tpImageInputGenerator.proxySetValue (cognitive 33) plugins/tweakpane/src/tpImageInputGenerator.ts:168— tpImageInputGenerator.proxySetValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 11, ternaries 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.
ObjectPicker.setSelected (cognitive 33) src/three/utils/ObjectPicker.ts:148— ObjectPicker.setSelected has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 12, ternaries 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObjectPicker.checkIntersection (cognitive 33) src/three/utils/ObjectPicker.ts:370— ObjectPicker.checkIntersection has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 13). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFViewerConfigExtension.BundleArrayBuffers (cognitive 33) src/assetmanager/gltf/GLTFViewerConfigExtension.ts:196— GLTFViewerConfigExtension.BundleArrayBuffers has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 14). Of this number, 17 points are the body's own statements and 16 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.
TransformControlsPlugin.onAdded (cognitive 33) src/plugins/interaction/TransformControlsPlugin.ts:86— TransformControlsPlugin.onAdded has cognitive complexity 33 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 6 (nesting depth added 4). None of this is in the body itself: all 33 points belong to 6 function literals inside it that branch (lines 108, 155, 92, …). 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.
tpImageInputGenerator.downloadImage (cognitive 32) plugins/tweakpane/src/tpImageInputGenerator.ts:238— tpImageInputGenerator.downloadImage has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 12, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetImporter.importAsset (cognitive 32) src/assetmanager/AssetImporter.ts:233— AssetImporter.importAsset has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 8 (nesting depth added 7). Of this number, 28 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
decorators.bindToValue.<returned closure> (cognitive 31) src/three/utils/decorators.ts:141— decorators.bindToValue.<returned closure> has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 9, ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 5). Of this number, 22 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AssetImporter._loadFile (cognitive 31) src/assetmanager/AssetImporter.ts:367— AssetImporter._loadFile has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 8, error handling 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.
PivotControlsPlugin.onAdded (cognitive 31) src/plugins/interaction/PivotControlsPlugin.ts:96— PivotControlsPlugin.onAdded has cognitive complexity 31 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 5 (nesting depth added 4). None of this is in the body itself: all 31 points belong to 6 function literals inside it that branch (lines 118, 165, 103, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CurveUiHelper.createCurveTypeDropdown.setValue (cognitive 30) src/plugins/geometry/helpers/CurveUiHelper.ts:267— CurveUiHelper.createCurveTypeDropdown.setValue has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, ternaries 4 (7 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lerp.lerpTexture (cognitive 29) src/utils/lerp.ts:51— lerp.lerpTexture has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 9, ternaries 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
setupComponent.getComponentStateProperties (cognitive 28) src/plugins/extras/components/setupComponent.ts:176— setupComponent.getComponentStateProperties has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (15 pts), ternaries 2 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialExtender.RegisterExtensions (cognitive 28) src/materials/MaterialExtender.ts:63— MaterialExtender.RegisterExtensions has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extensions.videoTextureExt.update (cognitive 27) plugins/timeline-ui/src/extensions.ts:287— extensions.videoTextureExt.update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TroikaTextPlugin.updateText (cognitive 26) plugins/troika-text/src/TroikaTextPlugin.ts:96— TroikaTextPlugin.updateText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 24, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OutlinePlugin.onAdded (cognitive 26) plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts:175— OutlinePlugin.onAdded has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4 (nesting depth added 8). None of this is in the body itself: all 26 points belong to 2 function literals inside it that branch (lines 202, 186). 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.
ShapeTubeExtrudePlugin.ConvertGeometryToFlatShape (cognitive 26) src/plugins/geometry/ShapeTubeExtrudePlugin.ts:192— ShapeTubeExtrudePlugin.ConvertGeometryToFlatShape has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 3 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.createObjects (cognitive 25) plugins/blend-importer/src/loader/index.ts:15— index.createObjects has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PivotControls._handlePointerMove (cognitive 25) src/three/controls/PivotControls.ts:624— PivotControls._handlePointerMove has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (8 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
assetExportHook.processGLTFAnimations (cognitive 25) src/assetmanager/export/assetExportHook.ts:222— assetExportHook.processGLTFAnimations has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityComponentPlugin.registerComponent (cognitive 25) src/plugins/extras/EntityComponentPlugin.ts:378— EntityComponentPlugin.registerComponent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, error handling 3, ternaries 1 (2 pts) (nesting depth added 6). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThreeViewer.fromJSON (cognitive 25) src/viewer/ThreeViewer.ts:1431— ThreeViewer.fromJSON has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
RootScene.loadModelRoot (cognitive 25) src/core/object/RootScene.ts:304— RootScene.loadModelRoot has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 8). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetExporter.processBeforeExport (cognitive 25) src/assetmanager/AssetExporter.ts:144— AssetExporter.processBeforeExport has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (7 pts), boolean chains 4, loops 1 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
webgi-showcase.init (cognitive 25) website/public/scripts/webgi-showcase.js:73— webgi-showcase.init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5, loops 4 (5 pts), ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 16 function items inside it that branch (onMouseMove, loadModel, setSplit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
camera.createCamera (cognitive 24) plugins/blend-importer/src/loader/camera.ts:4— camera.createCamera has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 10 (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.
Rhino3dmLoader2._useMaterialSource (cognitive 24) src/assetmanager/import/Rhino3dmLoader2.ts:84— Rhino3dmLoader2._useMaterialSource has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 10 (nesting depth added 6). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IObjectUi.makeIObject3DUiConfig (cognitive 24) src/core/object/IObjectUi.ts:110— IObjectUi.makeIObject3DUiConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 117, 197, 244, …). 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.
GLTFKHRMaterialVariantsPlugin.applyVariant (cognitive 24) src/plugins/extras/GLTFKHRMaterialVariantsPlugin.ts:71— GLTFKHRMaterialVariantsPlugin.applyVariant has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (7 pts), boolean chains 3, loops 1 (nesting depth added 8). Of this number, 14 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFViewerConfigExtension._parseExtraResources (cognitive 23) src/assetmanager/gltf/GLTFViewerConfigExtension.ts:77— GLTFViewerConfigExtension._parseExtraResources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 10). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraViewPlugin.animateToView (cognitive 23) src/plugins/animation/CameraViewPlugin.ts:228— CameraViewPlugin.animateToView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 3 (4 pts), loops 1 (2 pts) (nesting depth added 5). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericExtension.read (cognitive 22) plugins/gltf-transform/src/GLTFDracoExporterBase.ts:271— GenericExtension.read has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 9, loops 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 276, 305, 314, …). 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.
texture.texImageToCanvas (cognitive 22) src/three/utils/texture.ts:60— texture.texImageToCanvas has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 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.
AssetImporter.importFiles (cognitive 22) src/assetmanager/AssetImporter.ts:319— AssetImporter.importFiles has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 7 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.
iCameraCommons.upgradeCamera (cognitive 22) src/core/object/iCameraCommons.ts:260— iCameraCommons.upgradeCamera has cognitive complexity 22 (threshold 15). Drivers by points: if/else 22. 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.
DuplicateTracker.applyOffset (cognitive 22) src/plugins/interaction/DuplicateTracker.ts:50— DuplicateTracker.applyOffset has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HDRiGroundPlugin.setDirty (cognitive 22) src/plugins/extras/HDRiGroundPlugin.ts:56— HDRiGroundPlugin.setDirty has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
geometry.readFaceMaterialIndex (cognitive 21) plugins/blend-importer/src/loader/geometry.ts:75— geometry.readFaceMaterialIndex has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 2 (7 pts), if/else 3 (6 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnisotropyPlugin.enableAnisotropy (cognitive 21) plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69— AnisotropyPlugin.enableAnisotropy has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObjectPicker._hitObject (cognitive 21) src/three/utils/ObjectPicker.ts:327— ObjectPicker._hitObject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (6 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Object3DManager.registerObject (cognitive 21) src/assetmanager/Object3DManager.ts:123— Object3DManager.registerObject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PopmotionPlugin._postFrame (cognitive 21) src/plugins/animation/PopmotionPlugin.ts:73— PopmotionPlugin._postFrame has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 3 (nesting depth added 5). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityComponentPlugin.addComponent (cognitive 21) src/plugins/extras/EntityComponentPlugin.ts:219— EntityComponentPlugin.addComponent has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 8 (9 pts), boolean chains 2 (nesting depth added 7). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OutlinePlugin._getSelectedObject (cognitive 20) plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts:278— OutlinePlugin._getSelectedObject has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 4, if/else 3 (4 pts), loops 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.
decorators.matDefine.<returned closure> (cognitive 20) src/three/utils/decorators.ts:70— decorators.matDefine.<returned closure> has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 4). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AssetManager._sceneUpdated (cognitive 20) src/assetmanager/AssetManager.ts:235— AssetManager._sceneUpdated has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (5 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetManager._addImporters (cognitive 20) src/assetmanager/AssetManager.ts:290— AssetManager._addImporters has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetaImporter.LoadRootPathTextures (cognitive 20) src/utils/serialization.ts:860— MetaImporter.LoadRootPathTextures has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 10 points are the body's own statements and 10 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.
GLTFAnimationPlugin.playAnimation (cognitive 20) src/plugins/animation/GLTFAnimationPlugin.ts:299— GLTFAnimationPlugin.playAnimation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CSMFrustum.split (cognitive 20) src/plugins/rendering/CascadedShadowsPlugin.ts:961— CSMFrustum.split has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (14 pts), if/else 4 (6 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ThreeViewer.addSceneObject (cognitive 20) src/viewer/ThreeViewer.ts:1217— ThreeViewer.addSceneObject has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1 (nesting depth added 10). Of this number, 15 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PivotControls.updateGizmoScale (cognitive 19) src/three/controls/PivotControls.ts:513— PivotControls.updateGizmoScale has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RenderManager.blit (cognitive 19) REDACTED:445— RenderManager.blit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4, boolean chains 3 (nesting depth added 2). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
SphereGeometryGenerator._generateData (cognitive 19) src/plugins/geometry/primitives/SphereGeometryGenerator.ts:31— SphereGeometryGenerator._generateData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DynamicImportPlugin.loadPlugin (cognitive 19) src/plugins/extras/DynamicImportPlugin.ts:65— DynamicImportPlugin.loadPlugin has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 3 (4 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.
material.resolveShaders (cognitive 18) plugins/blend-importer/src/loader/material.ts:138— material.resolveShaders has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThreeGpuPathTracerPlugin.onAdded (cognitive 18) plugins/path-tracing/src/ThreeGpuPathTracerPlugin.ts:121— ThreeGpuPathTracerPlugin.onAdded has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 3). None of this is in the body itself: all 18 points belong to 5 function literals inside it that branch (lines 172, 149, 154, …). 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.
ShadowMapBaker._updateMaterial (cognitive 18) plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:375— ShadowMapBaker._updateMaterial has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PivotControls.updateHandleVisibility (cognitive 18) src/three/controls/PivotControls.ts:465— PivotControls.updateHandleVisibility has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mesh.createMesh (cognitive 17) plugins/blend-importer/src/loader/mesh.ts:6— mesh.createMesh has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 2 (4 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFDracoExporterBase.parseAsync (cognitive 17) plugins/gltf-transform/src/GLTFDracoExporterBase.ts:69— GLTFDracoExporterBase.parseAsync has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, error handling 1, ternaries 1 (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, 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.
ShadowMapBaker.updateShadow (cognitive 17) plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:207— ShadowMapBaker.updateShadow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, boolean chains 4, ternaries 1. Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GLTFLightExtrasExtension.Import (cognitive 17) src/assetmanager/gltf/GLTFLightExtrasExtension.ts:12— GLTFLightExtrasExtension.Import has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 17, 14). 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.
assetExportHook.processMeshLines (cognitive 17) src/assetmanager/export/assetExportHook.ts:244— assetExportHook.processMeshLines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (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.
assetExportHook.processObjectMaterials (cognitive 17) src/assetmanager/export/assetExportHook.ts:280— assetExportHook.processObjectMaterials has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 3 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 301, setMaterialRef). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Object3DManager._unregisterTexture (cognitive 17) src/assetmanager/Object3DManager.ts:484— Object3DManager._unregisterTexture has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
serialization.copyUserData (cognitive 17) src/utils/serialization.ts:508— serialization.copyUserData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
serialization.convertArrayBufferToStringsInMeta (cognitive 17) src/utils/serialization.ts:593— serialization.convertArrayBufferToStringsInMeta has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 595, 594). 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.
gpu-instancing.autoGPUInstanceMeshes (cognitive 17) src/three/utils/gpu-instancing.ts:6— gpu-instancing.autoGPUInstanceMeshes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanvasSnapshot.GetClonedCanvas (cognitive 17) src/utils/canvas-snapshot.ts:39— CanvasSnapshot.GetClonedCanvas has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimationObject._onAccessChanged (cognitive 17) src/utils/AnimationObject.ts:323— AnimationObject._onAccessChanged has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (8 pts) (nesting depth added 2). 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.
TubeShapeGeometry.constructor (cognitive 17) src/core/geometry/TubeShapeGeometry.ts:50— TubeShapeGeometry.constructor has cognitive complexity 17 (threshold 15). Drivers by points: loops 9 (11 pts), ternaries 4 (6 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (generateIndices, generateUVs, generateBufferData, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
GLTFKHRMaterialVariantsPlugin._objectAdded (cognitive 17) src/plugins/extras/GLTFKHRMaterialVariantsPlugin.ts:94— GLTFKHRMaterialVariantsPlugin._objectAdded has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 98). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ItemRef.fromJSON (cognitive 17) src/plugins/extras/components/ReferenceManager.ts:34— ItemRef.fromJSON has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EntityComponentPlugin.unregisterComponent (cognitive 17) src/plugins/extras/EntityComponentPlugin.ts:463— EntityComponentPlugin.unregisterComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 2 (4 pts), boolean chains 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.
ThreeViewer.dispose (cognitive 17) src/viewer/ThreeViewer.ts:741— ThreeViewer.dispose has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bakeGetters.bakeGetters::toPlainObject (cognitive 16) plugins/blend-importer/src/loader/bakeGetters.ts:7— bakeGetters.bakeGetters::toPlainObject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericExtension.write (cognitive 16) plugins/gltf-transform/src/GLTFDracoExporterBase.ts:337— GenericExtension.write has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 341, 392, 370, …). 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.
Components.Model (cognitive 16) plugins/r3f/src/Components.tsx:38— Components.Model has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 1, if/else 1 (nesting depth added 7). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 58, 49, 50). 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.
tpImageInputGenerator.tpImageInputGenerator.<returned closure> (cognitive 16) plugins/tweakpane/src/tpImageInputGenerator.ts:351— tpImageInputGenerator.tpImageInputGenerator.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 360, 373, 385). 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.
SSVelocityMaterial.onBeforeRender (cognitive 16) REDACTED:224— SSVelocityMaterial.onBeforeRender has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 1, ternaries 1 (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, 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.
decorators.uniform.<returned closure> (cognitive 16) src/three/utils/decorators.ts:15— decorators.uniform.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 4). Of this number, 9 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialManager.copyMaterialProps (cognitive 16) src/assetmanager/MaterialManager.ts:244— MaterialManager.copyMaterialProps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GLTFLoader2.parse (cognitive 16) src/assetmanager/import/GLTFLoader2.ts:142— GLTFLoader2.parse has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 144, 164, 176). 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.
MeshNormalMaterialOverride.onBeforeRender (cognitive 16) src/plugins/pipeline/NormalBufferPlugin.ts:165— MeshNormalMaterialOverride.onBeforeRender has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 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.
GLTFAnimationPlugin._refreshAnimations (cognitive 16) src/plugins/animation/GLTFAnimationPlugin.ts:643— GLTFAnimationPlugin._refreshAnimations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 665). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CustomBumpMapPlugin.enableCustomBump (cognitive 16) src/plugins/material/CustomBumpMapPlugin.ts:44— CustomBumpMapPlugin.enableCustomBump has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CascadedShadowsPlugin._refreshLightsInner (cognitive 16) src/plugins/rendering/CascadedShadowsPlugin.ts:190— CascadedShadowsPlugin._refreshLightsInner has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (3 pts), boolean chains 2 (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.
ShapeTubeExtrudePlugin.extrudeObject (cognitive 16) src/plugins/geometry/ShapeTubeExtrudePlugin.ts:73— ShapeTubeExtrudePlugin.extrudeObject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (4 pts), error handling 1 (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, 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.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing plugins/configurator/src/GridItemList.ts:41— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Dead branch — condition is always false plugins/gaussian-splatting/src/three-gaussian-splat/materials/GaussianSplatMaterialExtension.ts:47— A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition.
Fake-async — async method never awaits plugins/timeline-ui/src/init.ts:7— `initTimeline` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to src/plugins/extras/components/typeSystem.ts:168— The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
No structured logging — No logging call was found in the 405 JavaScript/TypeScript production file(s) this check read across 20 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Sync-over-async blocking scripts/vite-utils.mjs:84— `existsSync` in `has` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplication concentrated across 3 sibling directories (26 clone groups) plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69— 26 duplicated blocks under the repository root have copies in at least two of the sibling directories plugins, scripts, src — 20 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (14 clone groups) src/plugins/pipeline/GBufferPlugin.ts:214— 14 duplicated blocks under src/ have copies in at least two of the sibling directories assetmanager, core, plugins, postprocessing, rendering, three (+1 more sibling(s) not listed) — 5 of them are reported below, and 9 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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 8 sibling directories (14 clone groups) src/plugins/animation/AnimationObjectPlugin.ts:273— 14 duplicated blocks under src/plugins/ have copies in at least two of the sibling directories animation, base, extras, geometry, import, interaction (+2 more sibling(s) not listed) — 10 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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 19 sibling directories (12 clone groups) plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63— 12 duplicated blocks under plugins/ have copies in at least two of the sibling directories 3d-tiles-renderer, assimpjs, blend-importer, blueprintjs, configurator, extra-importers (+13 more sibling(s) not listed) — 11 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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 4 sibling directories (5 clone groups) src/core/light/DirectionalLight2.ts:133— 5 duplicated blocks under src/core/ have copies in at least two of the sibling directories geometry, light, material, object — 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (163 matched lines × 2 locations) · ×1
Duplicated block with local edits (163 matched lines × 2 locations) plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:52— plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:52 · plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:52 — the two spans are one implementation copied and then locally edited — 1152 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) src/plugins/material/ClearcoatTintPlugin.ts:18— src/plugins/material/ClearcoatTintPlugin.ts:18 · src/plugins/material/NoiseBumpMaterialPlugin.ts:21 — the two spans are one implementation copied and then locally edited — 997 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (133 matched lines × 2 locations) · ×1
Duplicated block with local edits (133 matched lines × 2 locations) src/core/camera/OrthographicCamera2.ts:259— src/core/camera/OrthographicCamera2.ts:259 · src/core/camera/PerspectiveCamera2.ts:238 — the two spans are one implementation copied and then locally edited — 1005 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (130 matched lines × 2 locations) · ×1
Duplicated block with local edits (130 matched lines × 2 locations) plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69— plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69 · src/plugins/material/CustomBumpMapPlugin.ts:44 — the two spans are one implementation copied and then locally edited — 901 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (128 matched lines × 2 locations) · ×1
Duplicated block with local edits (128 matched lines × 2 locations) src/plugins/material/FragmentClippingExtensionPlugin.ts:22— src/plugins/material/FragmentClippingExtensionPlugin.ts:22 · src/plugins/material/NoiseBumpMaterialPlugin.ts:21 — the two spans are one implementation copied and then locally edited — 849 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (115 matched lines × 2 locations) · ×1
Duplicated block with local edits (115 matched lines × 2 locations) plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:137— plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:137 · src/plugins/pipeline/SSAOPlugin.ts:230 — the two spans are one implementation copied and then locally edited — 848 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (101 matched lines × 2 locations) · ×1
Duplicated block with local edits (101 matched lines × 2 locations) src/plugins/ui/GeometryUVPreviewPlugin.ts:18— src/plugins/ui/GeometryUVPreviewPlugin.ts:18 · src/plugins/ui/RenderTargetPreviewPlugin.ts:28 — the two spans are one implementation copied and then locally edited — 699 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (93 matched lines × 2 locations) · ×1
Duplicated block with local edits (93 matched lines × 2 locations) src/core/camera/OrthographicCamera2.ts:16— src/core/camera/OrthographicCamera2.ts:16 · src/core/camera/PerspectiveCamera2.ts:27 — the two spans are one implementation copied and then locally edited — 845 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 (90 lines × 2 locations) src/core/material/LegacyPhongMaterial.ts:28— src/core/material/LegacyPhongMaterial.ts:28 · src/core/material/UnlitMaterial.ts:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:167— plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:167 · src/plugins/pipeline/SSAOPlugin.ts:254 — the two spans are one implementation copied and then locally edited — 593 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (79 matched lines × 2 locations) · ×1
Duplicated block with local edits (79 matched lines × 2 locations) plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63— plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:63 · plugins/tweakpane/src/TweakpaneUiPlugin.ts:83 — the two spans are one implementation copied and then locally edited — 678 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 (66 lines × 6 locations) plugins/blend-importer/vite.config.js:11— plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · plugins/extra-importers/vite.config.js:11 · plugins/gaussian-splatting/vite.config.js:11 · +2 more site(s) not listed — the 6 copies are spread across 6 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 (65 lines × 4 locations) plugins/assimpjs/vite.config.js:11— plugins/assimpjs/vite.config.js:11 · plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · plugins/network/vite.config.js:11 — the 4 copies are spread across 4 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 (63 lines × 2 locations) plugins/3d-tiles-renderer/src/CMPTLoadPlugin.ts:17— plugins/3d-tiles-renderer/src/CMPTLoadPlugin.ts:17 · plugins/3d-tiles-renderer/src/PNTSLoadPlugin.ts:16 — 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 (55 lines × 2 locations) src/plugins/interaction/PivotControlsPlugin.ts:115— src/plugins/interaction/PivotControlsPlugin.ts:115 · src/plugins/interaction/TransformControlsPlugin.ts:106 — 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 (53 lines × 2 locations) src/assetmanager/gltf/GLTFMaterialsBumpMapExtension.ts:15— src/assetmanager/gltf/GLTFMaterialsBumpMapExtension.ts:15 · src/assetmanager/gltf/GLTFMaterialsDisplacementMapExtension.ts:13 — 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.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) src/plugins/pipeline/DepthBufferPlugin.ts:95— src/plugins/pipeline/DepthBufferPlugin.ts:95 · src/plugins/pipeline/GBufferPlugin.ts:102 — the two spans are one implementation copied and then locally edited — 392 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) plugins/configurator/src/MaterialConfiguratorPlugin.ts:49— plugins/configurator/src/MaterialConfiguratorPlugin.ts:49 · plugins/configurator/src/SwitchNodePlugin.ts:51 — the two spans are one implementation copied and then locally edited — 335 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (48 matched lines × 2 locations) · ×1
Duplicated block with local edits (48 matched lines × 2 locations) src/three/widgets/BoneHelper.ts:40— src/three/widgets/BoneHelper.ts:40 · src/three/widgets/SkeletonHelper2.ts:43 — the two spans are one implementation copied and then locally edited — 369 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 (46 lines × 3 locations) plugins/blueprintjs/vite.config.js:6— plugins/blueprintjs/vite.config.js:6 · plugins/timeline-ui/vite.config.js:6 · plugins/tweakpane/vite.config.js:6 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (45 lines × 2 locations) plugins/plugin-template-vite/vite.config.js:6— plugins/plugin-template-vite/vite.config.js:6 · plugins/tweakpane-editor/vite.config.js:6 — 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 (42 lines × 6 locations) plugins/3d-tiles-renderer/vite.config.js:11— plugins/3d-tiles-renderer/vite.config.js:11 · plugins/assimpjs/vite.config.js:11 · plugins/blend-importer/vite.config.js:11 · plugins/configurator/vite.config.js:11 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) plugins/svg-renderer/vite.config.js:9— plugins/svg-renderer/vite.config.js:9 · plugins/troika-text/vite.config.js:4 — the two spans are one implementation copied and then locally edited — 209 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 (40 lines × 2 locations) plugins/gltf-transform/vite.config.js:8— plugins/gltf-transform/vite.config.js:8 · plugins/webgi-plugins/vite.config.js:11 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) src/assetmanager/gltf/GLTFLightExtrasExtension.ts:5— src/assetmanager/gltf/GLTFLightExtrasExtension.ts:5 · src/assetmanager/gltf/GLTFObject3DExtrasExtension.ts:5 — the two spans are one implementation copied and then locally edited — 316 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 (36 lines × 2 locations) plugins/3d-tiles-renderer/src/B3DMLoadPlugin.ts:22— plugins/3d-tiles-renderer/src/B3DMLoadPlugin.ts:22 · plugins/3d-tiles-renderer/src/I3DMLoadPlugin.ts:23 — 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 (35 lines × 18 locations) plugins/3d-tiles-renderer/vite.config.js:17— plugins/3d-tiles-renderer/vite.config.js:17 · plugins/assimpjs/vite.config.js:17 · plugins/blend-importer/vite.config.js:17 · plugins/blueprintjs/vite.config.js:14 · +14 more site(s) not listed — the 18 copies are spread across 18 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 3 locations) src/plugins/material/ClearcoatTintPlugin.ts:103— src/plugins/material/ClearcoatTintPlugin.ts:103 · src/plugins/material/FragmentClippingExtensionPlugin.ts:118 · src/plugins/material/NoiseBumpMaterialPlugin.ts:102 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 3 locations) src/plugins/material/ClearcoatTintPlugin.ts:147— src/plugins/material/ClearcoatTintPlugin.ts:147 · src/plugins/material/FragmentClippingExtensionPlugin.ts:172 · src/plugins/material/NoiseBumpMaterialPlugin.ts:228 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) src/utils/camera-anim.ts:13— src/utils/camera-anim.ts:13 · src/utils/camera-anim.ts:69 — the two spans are one implementation copied and then locally edited — 239 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 (33 lines × 2 locations) vite.config.js:36— vite.config.js:36 · vite.lib.config.js:45 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) plugins/svg-renderer/src/BasicSVGRendererPlugin.ts:35— plugins/svg-renderer/src/BasicSVGRendererPlugin.ts:35 · plugins/svg-renderer/src/ThreeSVGRendererPlugin.ts:152 — the two spans are one implementation copied and then locally edited — 206 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 (32 lines × 2 locations) src/core/material/ObjectShaderMaterial.ts:28— src/core/material/ObjectShaderMaterial.ts:28 · src/core/material/UnlitLineMaterial.ts:30 — 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.
Complex function _onKeyDown (cyclomatic 113, cognitive 172) src/three/controls/PivotControls.ts:205— _onKeyDown has cyclomatic complexity 113 and cognitive complexity 172; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 writeMaterial (cyclomatic 106, cognitive 104) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:158— writeMaterial has cyclomatic complexity 106 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 createMaterial (cyclomatic 86, cognitive 127) plugins/blend-importer/src/loader/material.ts:162— createMaterial has cyclomatic complexity 86 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function selectionCondition (cyclomatic 82, cognitive 108) src/three/utils/ObjectPicker.ts:59— selectionCondition has cyclomatic complexity 82 and cognitive complexity 108; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 createBufferGeometry (cyclomatic 75, cognitive 135) plugins/blend-importer/src/loader/geometry.ts:187— createBufferGeometry has cyclomatic complexity 75 and cognitive complexity 135; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 71, cognitive 67) src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:25— (anonymous) has cyclomatic complexity 71 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 pointerMove (cyclomatic 62, cognitive 121) REDACTED:277— pointerMove has cyclomatic complexity 62 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 updateMatrixWorld (cyclomatic 61, cognitive 148) REDACTED:1208— updateMatrixWorld has cyclomatic complexity 61 and cognitive complexity 148; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 ImportMeta (cyclomatic 59, cognitive 89) src/utils/serialization.ts:699— ImportMeta has cyclomatic complexity 59 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 readFile (cyclomatic 48, cognitive 131) plugins/blend-importer/src/js-blend/parser/parser.js:691— readFile has cyclomatic complexity 48 and cognitive complexity 131; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 (top-level) (cyclomatic 46, cognitive 50) src/plugins/base/BaseGroundPlugin.ts:1— (top-level) has cyclomatic complexity 46 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createBufferGeometryFromAttributes (cyclomatic 43, cognitive 74) plugins/blend-importer/src/loader/geometry.ts:96— createBufferGeometryFromAttributes has cyclomatic complexity 43 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 deserialize (cyclomatic 41, cognitive 55) src/utils/serialization.ts:241— deserialize has cyclomatic complexity 41 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 proxyGetValue (cyclomatic 36, cognitive 65) plugins/tweakpane/src/tpImageInputGenerator.ts:49— proxyGetValue has cyclomatic complexity 36 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 proxySetValue (cyclomatic 34, cognitive 40) plugins/tweakpane/src/tpImageInputGenerator.ts:168— proxySetValue has cyclomatic complexity 34 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 upgradeObject3D (cyclomatic 33, cognitive 37) src/core/object/iObjectCommons.ts:696— upgradeObject3D has cyclomatic complexity 33 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 lerpParams (cyclomatic 32, cognitive 50) src/utils/lerp.ts:126— lerpParams has cyclomatic complexity 32 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function downloadImage (cyclomatic 32, cognitive 36) plugins/tweakpane/src/tpImageInputGenerator.ts:238— downloadImage has cyclomatic complexity 32 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _onKeyDown (cyclomatic 32, cognitive 35) src/plugins/interaction/PickingPlugin.ts:198— _onKeyDown has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function processRawStartHook (cyclomatic 30, cognitive 75) src/assetmanager/AssetManager.ts:703— processRawStartHook has cyclomatic complexity 30 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _getFile (cyclomatic 28, cognitive 38) src/plugins/export/CanvasSnapshotPlugin.ts:62— _getFile has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function lerpTexture (cyclomatic 28, cognitive 31) src/utils/lerp.ts:51— lerpTexture has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function GetType (cyclomatic 26, cognitive 55) src/plugins/extras/components/typeSystem.ts:70— GetType has cyclomatic complexity 26 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 processTexture (cyclomatic 26, cognitive 47) src/assetmanager/export/GLTFWriter2.ts:184— processTexture has cyclomatic complexity 26 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 (top-level) (cyclomatic 26, cognitive 25) src/utils/ViewerTimeline.ts:1— (top-level) has cyclomatic complexity 26 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 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 importAsset (cyclomatic 25, cognitive 30) src/assetmanager/AssetImporter.ts:233— importAsset has cyclomatic complexity 25 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 CanAssign (cyclomatic 24, cognitive 44) src/plugins/extras/components/typeSystem.ts:149— CanAssign has cyclomatic complexity 24 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 18) src/plugins/animation/GLTFAnimationPlugin.ts:535— (anonymous) has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function serialize (cyclomatic 23, cognitive 44) src/utils/serialization.ts:175— serialize has cyclomatic complexity 23 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 upgradeCamera (cyclomatic 23, cognitive 37) src/core/object/iCameraCommons.ts:260— upgradeCamera has cyclomatic complexity 23 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 update (cyclomatic 23, cognitive 37) src/three/widgets/LineHelper.ts:92— update has cyclomatic complexity 23 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 setValue (cyclomatic 23, cognitive 30) src/plugins/geometry/helpers/CurveUiHelper.ts:267— setValue has cyclomatic complexity 23 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 serialize (cyclomatic 23, cognitive 26) src/utils/serialization.ts:88— serialize has cyclomatic complexity 23 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 enableAnisotropy (cyclomatic 23, cognitive 22) plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:69— enableAnisotropy has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _loadFile (cyclomatic 22, cognitive 30) src/assetmanager/AssetImporter.ts:367— _loadFile has cyclomatic complexity 22 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 detectBlendCompression (cyclomatic 22, cognitive 11) plugins/blend-importer/src/decompress.ts:11— detectBlendCompression has cyclomatic complexity 22 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onBeforeRender (cyclomatic 21, cognitive 20) plugins/webgi-plugins/src/utils/Reflector2.ts:82— onBeforeRender has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateMatrixWorld (cyclomatic 21, cognitive 13) REDACTED:1542— updateMatrixWorld has cyclomatic complexity 21 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 write (cyclomatic 20, cognitive 31) tests/deterministic-injection.js:118— write has cyclomatic complexity 20 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 setMaterial (cyclomatic 20, cognitive 24) src/core/object/iObjectCommons.ts:337— setMaterial has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
src/viewer/ThreeViewer.ts: 1606 lines of code src/viewer/ThreeViewer.ts:1— src/viewer/ThreeViewer.ts has 1606 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: 1060 lines of code REDACTED:1— REDACTED has 1060 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/utils/serialization.ts: 925 lines of code src/utils/serialization.ts:1— src/utils/serialization.ts has 925 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· plugins/blend-importer/src/js-blend/parser/parser.js · ×1
plugins/blend-importer/src/js-blend/parser/parser.js: 912 lines of code plugins/blend-importer/src/js-blend/parser/parser.js:1— plugins/blend-importer/src/js-blend/parser/parser.js has 912 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· src/plugins/interaction/PickingPlugin.ts · ×1
src/plugins/interaction/PickingPlugin.ts: 870 lines of code src/plugins/interaction/PickingPlugin.ts:1— src/plugins/interaction/PickingPlugin.ts has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/core/object/RootScene.ts · ×1
src/core/object/RootScene.ts: 813 lines of code src/core/object/RootScene.ts:1— src/core/object/RootScene.ts has 813 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· src/plugins/rendering/CascadedShadowsPlugin.ts · ×1
src/plugins/rendering/CascadedShadowsPlugin.ts: 810 lines of code src/plugins/rendering/CascadedShadowsPlugin.ts:1— src/plugins/rendering/CascadedShadowsPlugin.ts has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/three/controls/PivotControls.ts · ×1
src/three/controls/PivotControls.ts: 752 lines of code src/three/controls/PivotControls.ts:1— src/three/controls/PivotControls.ts has 752 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· src/assetmanager/AssetManager.ts · ×1
src/assetmanager/AssetManager.ts: 733 lines of code src/assetmanager/AssetManager.ts:1— src/assetmanager/AssetManager.ts has 733 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· src/core/object/iObjectCommons.ts · ×1
src/core/object/iObjectCommons.ts: 733 lines of code src/core/object/iObjectCommons.ts:1— src/core/object/iObjectCommons.ts has 733 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: 727 lines of code REDACTED:1— REDACTED has 727 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· src/core/material/IMaterialUi.ts · ×1
src/core/material/IMaterialUi.ts: 724 lines of code src/core/material/IMaterialUi.ts:1— src/core/material/IMaterialUi.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/assetmanager/AssetImporter.ts · ×1
src/assetmanager/AssetImporter.ts: 701 lines of code src/assetmanager/AssetImporter.ts:1— src/assetmanager/AssetImporter.ts has 701 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· src/plugins/animation/GLTFAnimationPlugin.ts · ×1
src/plugins/animation/GLTFAnimationPlugin.ts: 699 lines of code src/plugins/animation/GLTFAnimationPlugin.ts:1— src/plugins/animation/GLTFAnimationPlugin.ts has 699 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· src/plugins/animation/CameraViewPlugin.ts · ×1
src/plugins/animation/CameraViewPlugin.ts: 693 lines of code src/plugins/animation/CameraViewPlugin.ts:1— src/plugins/animation/CameraViewPlugin.ts has 693 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· plugins/timeline-ui/src/timeline.tsx · ×1
plugins/timeline-ui/src/timeline.tsx: 660 lines of code plugins/timeline-ui/src/timeline.tsx:1— plugins/timeline-ui/src/timeline.tsx has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/assetmanager/import/OBJLoader2.ts · ×1
src/assetmanager/import/OBJLoader2.ts: 595 lines of code src/assetmanager/import/OBJLoader2.ts:1— src/assetmanager/import/OBJLoader2.ts has 595 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· src/assetmanager/Object3DManager.ts · ×1
src/assetmanager/Object3DManager.ts: 593 lines of code src/assetmanager/Object3DManager.ts:1— src/assetmanager/Object3DManager.ts has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/plugins/extras/EntityComponentPlugin.ts · ×1
src/plugins/extras/EntityComponentPlugin.ts: 585 lines of code src/plugins/extras/EntityComponentPlugin.ts:1— src/plugins/extras/EntityComponentPlugin.ts has 585 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· src/utils/AnimationObject.ts · ×1
src/utils/AnimationObject.ts: 576 lines of code src/utils/AnimationObject.ts:1— src/utils/AnimationObject.ts has 576 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/core/IObject.ts: 568 lines of code src/core/IObject.ts:1— src/core/IObject.ts has 568 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· src/plugins/animation/AnimationObjectPlugin.ts · ×1
src/plugins/animation/AnimationObjectPlugin.ts: 517 lines of code src/plugins/animation/AnimationObjectPlugin.ts:1— src/plugins/animation/AnimationObjectPlugin.ts has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts · ×1
plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts: 512 lines of code plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:1— plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts has 512 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· src/plugins/pipeline/SSAOPlugin.ts · ×1
src/plugins/pipeline/SSAOPlugin.ts: 501 lines of code src/plugins/pipeline/SSAOPlugin.ts:1— src/plugins/pipeline/SSAOPlugin.ts has 501 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· plugins/blend-importer/src/loader/geometry.ts · ×1
plugins/blend-importer/src/loader/geometry.ts: 497 lines of code plugins/blend-importer/src/loader/geometry.ts:1— plugins/blend-importer/src/loader/geometry.ts has 497 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· src/three/utils/ViewHelper2.ts · ×1
src/three/utils/ViewHelper2.ts: 492 lines of code src/three/utils/ViewHelper2.ts:1— src/three/utils/ViewHelper2.ts has 492 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· plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts · ×1
plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts: 491 lines of code plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts:1— plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts has 491 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· src/plugins/animation/PopmotionPlugin.ts · ×1
src/plugins/animation/PopmotionPlugin.ts: 467 lines of code src/plugins/animation/PopmotionPlugin.ts:1— src/plugins/animation/PopmotionPlugin.ts has 467 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· plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts · ×1
plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts: 458 lines of code plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:1— plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts has 458 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· plugins/webgi-plugins/src/utils/ShadowMapBaker.ts · ×1
plugins/webgi-plugins/src/utils/ShadowMapBaker.ts: 448 lines of code plugins/webgi-plugins/src/utils/ShadowMapBaker.ts:1— plugins/webgi-plugins/src/utils/ShadowMapBaker.ts 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· src/assetmanager/import/GLTFLoader2.ts · ×1
src/assetmanager/import/GLTFLoader2.ts: 439 lines of code src/assetmanager/import/GLTFLoader2.ts:1— src/assetmanager/import/GLTFLoader2.ts has 439 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· src/plugins/configurator/MaterialConfiguratorBasePlugin.ts · ×1
src/plugins/configurator/MaterialConfiguratorBasePlugin.ts: 432 lines of code src/plugins/configurator/MaterialConfiguratorBasePlugin.ts:1— src/plugins/configurator/MaterialConfiguratorBasePlugin.ts has 432 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· src/core/camera/PerspectiveCamera2.ts · ×1
src/core/camera/PerspectiveCamera2.ts: 429 lines of code src/core/camera/PerspectiveCamera2.ts:1— src/core/camera/PerspectiveCamera2.ts has 429 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· plugins/timeline-ui/src/extensions.ts · ×1
plugins/timeline-ui/src/extensions.ts: 410 lines of code plugins/timeline-ui/src/extensions.ts:1— plugins/timeline-ui/src/extensions.ts has 410 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· plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts · ×1
plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts: 410 lines of code plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts:1— plugins/webgi-plugins/src/plugins/postprocessing/DepthOfFieldPlugin.ts has 410 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· plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts · ×1
plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts: 405 lines of code plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts:1— plugins/webgi-plugins/src/plugins/postprocessing/OutlinePlugin.ts has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R6 · Tooling· A linter is configured here, but no build or CI step runs it · ×1
A linter is configured here, but no build or CI step runs it .eslintrc.cjs:1— the root package configures a linter in `.eslintrc.cjs`, but no package script, bundler plugin, task runner or CI step in this repository runs a linter, so the rules it sets are enforced nowhere. Run it where it can fail: a `lint` script that CI runs, a linter plugin in the build, or a CI step.
Dead file (~174 LoC) plugins/blend-importer/src/js-blend/threejs/material.js— no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/blend_three.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~100 LoC) plugins/blend-importer/src/js-blend/threejs/mesh.js— no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/blend_three.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~91 LoC) plugins/blend-importer/src/js-blend/threejs/blend_three.js— no import path from any entry point (45 application, 55 tooling, 26 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 (~63 LoC) plugins/blend-importer/src/loader/bakeGetters.ts— no import path from any entry point (45 application, 55 tooling, 26 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 (~60 LoC) plugins/blend-importer/src/js-blend/threejs/texture.js— no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/material.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~47 LoC) plugins/blend-importer/src/js-blend/threejs/light.js— no import path from any entry point (45 application, 55 tooling, 26 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (plugins/blend-importer/src/js-blend/threejs/blend_three.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~24 LoC) plugins/timeline-ui/src/init.ts— no import path from any entry point (45 application, 55 tooling, 26 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 (~5 LoC) scripts/build-plugins.mjs— no import path from any entry point (45 application, 55 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~0 LoC) plugins/gaussian-splatting/src/gaussian-splats-3d/GaussianSplatsPlugin.ts— no import path from any entry point (45 application, 55 tooling, 26 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 'copyfiles' package.json:130— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'hexer' package.json:137— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'proper-lockfile' package.json:139— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tslib' package.json:144— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vitepress-plugin-nprogress' package.json:151— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'wrangler' package.json:153— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'assimpjs' plugins/assimpjs/package.json:9— Declared in plugins/assimpjs/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 'flatbush' plugins/svg-renderer/package.json:10— Declared in plugins/svg-renderer/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 'xml-formatter' plugins/svg-renderer/package.json:13— Declared in plugins/svg-renderer/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.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked plugins/plugin-template-vite/package.json:7— plugins/plugin-template-vite/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×1
Owned disposable field is never released src/three/utils/ViewHelper2.ts:111— `ViewHelper2` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `renderer` itself (line 111, `new WebGLRenderer`), which makes that instance its own. But `renderer` is named in none of the methods the disposal search covered: `dispose` (line 262) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `WebGLRenderer` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this.renderer.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree.
redundant comment plugins/blend-importer/src/js-blend/parser/parser.js:1000— "Get a SDNA constructor by name;" repeats the code it sits on: 4 of its 4 words (get, sdna, constructor, name) are already in `const constructor = current_SDNA_template.getSDNAStructureConstructor(current_SDNA_template.SDNA_NAMES[sdna_index]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment plugins/tweakpane/src/tpImageInputGenerator.ts:249— "HTML image/video/bitmap" repeats the code it sits on: 4 of its 4 words (html, image, video, bitmap) are already in `if (vcv && (vcv instanceof ImageBitmap || vcv instanceof HTMLImageElement || vcv instanceof HTMLVideoElement) && !src)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment plugins/tweakpane/src/tpImageInputGenerator.ts:255— "Render target texture" repeats the code it sits on: 3 of its 3 words (render, target, texture) are already in `if (!src && tex.isRenderTargetTexture)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:38— "type VelocityBufferPluginTarget = WebGLRenderTarget" repeats the code it sits on: 7 of its 8 words (velocity, buffer, plugin, target, web, gl, render) are already in `export type VelocityBufferPluginTarget = WebGLRenderTarget`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/fix-inline-imports.mjs:40— "Replace assetsDir with distDir and append .js" repeats the code it sits on: 5 of its 6 words (replace, assets, dir, dist, js) are already in `const jsFile = assetFile.replace(assetsDir, distDir) + '.js';`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/assetmanager/IExporter.ts:8— "parse(obj: any, options: AnyOptions): any;" repeats the code it sits on: 3 of its 3 words (parse, obj, options) are already in `parseAsync(obj: any, options: AnyOptions): Promise<Blob>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/assetmanager/gltf/GLTFMaterialExtrasExtension.ts:241— "if (material.visible !== undefined && material.visible !== threeMaterialPropList.visible) dat.visible = material.visible" repeats the code it sits on: 6 of its 7 words (material, undefined, three, prop, list, dat) are already in `if (material.toneMapped !== undefined && material.toneMapped !== threeMaterialPropList.toneMapped) dat.toneMapped = mate …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/assetmanager/import/GLTFLoader2.ts:475— "if (meta) { meta._dRoot = res.userData }" repeats the code it sits on: 4 of its 5 words (meta, res, user, data) are already in `res.userData = ThreeSerialization.Deserialize(res.userData, {}, meta)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/animation/AnimationObjectPlugin.ts:568— "if (!obj.userData.animationObjects) obj.userData.animationObjects = []" repeats the code it sits on: 5 of its 5 words (obj, user, data, animation, objects) are already in `return obj?.userData.animationObjects?.find(o => o.access === key)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/animation/TransformAnimationPlugin.ts:48— "if (!o.userData[TransformAnimationPlugin.PluginType].transforms) { o.userData[TransformAnimationPlugin.PluginType].transforms = [] }" repeats the code it sits on: 7 of its 7 words (user, data, transform, animation, plugin, type, transforms) are already in `o.userData[TransformAnimationPlugin.PluginType]?.transforms?.forEach((t, i)=>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/extras/MeshOptSimplifyModifierPlugin.ts:101— "(geometry.index!.array as Uint32Array).set(dstIndexArray)" repeats the code it sits on: 7 of its 7 words (geometry, index, array, uint, 32, set, dst) are already in `geometry.setIndex(new BufferAttribute(new Uint32Array(dstIndexArray), 1))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/extras/components/setupComponent.ts:191— "same class property duplicate" repeats the code it sits on: 3 of its 3 words (class, property, duplicate) are already in `console.error('Object3DComponent: duplicate state property in class', {key, base})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/extras/components/setupComponent.ts:194— "derived class property overrides base class property" repeats the code it sits on: 4 of its 5 words (derived, class, property, base) are already in `console.warn('Object3DComponent: state property overridden in derived class', {key, base, constructor: cons})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/extras/helpers/BasicObjectConstraints.ts:252— "Check if target has geometry" repeats the code it sits on: 3 of its 3 words (check, target, geometry) are already in `if (!target.geometry)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/interaction/LoadingScreenPlugin.ts:163— "this._mainDiv.style.opacity = this.opacity.toString()" repeats the code it sits on: 4 of its 5 words (main, div, style, opacity) are already in `this._mainDiv.style.opacity = '1'`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/pipeline/DepthBufferPlugin.ts:32— "type DepthBufferPluginTarget = WebGLRenderTarget" repeats the code it sits on: 7 of its 8 words (depth, buffer, plugin, target, web, gl, render) are already in `export type DepthBufferPluginTarget = WebGLRenderTarget`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/pipeline/NormalBufferPlugin.ts:27— "type NormalBufferPluginTarget = WebGLRenderTarget" repeats the code it sits on: 7 of its 8 words (normal, buffer, plugin, target, web, gl, render) are already in `export type NormalBufferPluginTarget = WebGLRenderTarget`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/rendering/CascadedShadowsPlugin.ts:715— "ShaderChunk.lights_fragment_begin = CSMShader.lights_fragment_begin" repeats the code it sits on: 6 of its 6 words (shader, chunk, lights, fragment, begin, csm) are already in `ShaderChunk.lights_fragment_begin = shaderReplaceString(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/plugins/rendering/CascadedShadowsPlugin.ts:852— "ShaderChunk.lights_pars_begin = CSMShader.lights_pars_begin" repeats the code it sits on: 6 of its 6 words (shader, chunk, lights, pars, begin, csm) are already in `ShaderChunk.lights_pars_begin = ``. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/postprocessing/ExtendedShaderPass.ts:29— "writes to writeBuffer" repeats the code it sits on: 3 of its 3 words (writes, write, buffer) are already in `render(renderer: IWebGLRenderer, writeBuffer?: WebGLRenderTarget|null, readBuffer?: WebGLRenderTarget, deltaTime?: numbe …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/three/utils/ObjectPicker.ts:136— "set selectedObject(object) { this.setSelected(object) }" repeats the code it sits on: 3 of its 3 words (set, selected, object) are already in `protected _onSelectedRemoved = (e: {target: IObject3D|IMaterial}) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/three/utils/ObjectPicker.ts:210— "set hoverObject(object: SelectionObject | SelectionObject[] | null) {" repeats the code it sits on: 4 of its 5 words (set, hover, object, selection) are already in `setHoverObject(object: SelectionObject, _record = true, intersects?: HitIntersects)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/utils/AnimationObject.ts:256— "targetObject?: Record<string, any>" repeats the code it sits on: 4 of its 4 words (target, object, record, string) are already in `get targetObject(): Record<string, any>|undefined`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/interactive.spec.ts:406— "3x3 Tiles PNG ZIP" repeats the code it sits on: 3 of its 3 words (tiles, png, zip) are already in `await downloadFileMatch(page, 'snapshot.zip', async() => btnClick(page, 'Download 3x3 Tiles (png zip)'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/interactive.spec.ts:2458— "Download the EXR file via the button" repeats the code it sits on: 4 of its 4 words (download, exr, file, button) are already in `await downloadFileMatch(page, 'file.exr',`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate src/core/geometry/iGeometryCommons.ts:19— `!force && this.userData.disposeOnIdle === false` appears character-identically in 2 files — src/core/geometry/iGeometryCommons.ts, src/core/material/iMaterialCommons.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 src/assetmanager/gltf/GLTFMaterialsAlphaMapExtension.ts:49— `!materialDef.extensions || !materialDef.extensions[ this.name ]` appears character-identically in 4 files — src/assetmanager/gltf/GLTFMaterialsAlphaMapExtension.ts, src/assetmanager/gltf/GLTFMaterialsBumpMapExtension.ts, src/assetmanager/gltf/GLTFMaterialsDisplacementMapExtension.ts, src/assetmanager/gltf/GLTFMaterialsLightMapExtension.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 plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:429— `!materialDef.extensions || !materialDef.extensions[this.name]` appears character-identically in 5 files — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts, src/plugins/material/ClearcoatTintPlugin.ts, src/plugins/material/CustomBumpMapPlugin.ts, src/plugins/material/FragmentClippingExtensionPlugin.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 plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:140— `!this._viewer.renderManager.gbufferTarget || !this._viewer.renderManager.gbufferUnpackExtension` appears character-identically in 4 files — plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts, plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.ts, plugins/webgi-plugins/src/plugins/postprocessing/TemporalAAPlugin.ts, src/plugins/pipeline/SSAOPlugin.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 src/plugins/interaction/PickingPlugin.ts:200— `(event.target as any)?.tagName === 'TEXTAREA' || (event.target as any)?.tagName === 'INPUT'` appears character-identically in 4 files — src/plugins/interaction/PickingPlugin.ts, src/plugins/interaction/PivotEditPlugin.ts, src/plugins/interaction/TransformControlsPlugin.ts, src/three/controls/gizmoKeyboardHandler.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 src/three/widgets/BoneHelper.ts:88— `bone.parent && (bone.parent as any).isBone` appears character-identically in 2 files — src/three/widgets/BoneHelper.ts, src/three/widgets/SkeletonHelper2.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 plugins/webgi-plugins/src/plugins/extras/AdvancedGroundPlugin.ts:173— `event?.object?.assetType === 'widget' || event?.object?.userData?.isWidgetRoot` appears character-identically in 2 files — plugins/webgi-plugins/src/plugins/extras/AdvancedGroundPlugin.ts, src/plugins/base/BaseGroundPlugin.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 plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:76— `geometry && (!geometry.attributes.position || !geometry.attributes.normal || !geometry.attributes.uv)` appears character-identically in 2 files — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts, src/plugins/material/CustomBumpMapPlugin.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 src/plugins/geometry/primitives/ShapeGeometryGenerator.ts:73— `label === 'circleRadius' || label === 'circleSegments'` appears character-identically in 2 files — src/plugins/geometry/primitives/ShapeGeometryGenerator.ts, src/plugins/geometry/primitives/TubeShapeGeometryGenerator.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 src/plugins/geometry/primitives/ShapeGeometryGenerator.ts:75— `label === 'sides' || label === 'polygonRadius'` appears character-identically in 2 files — src/plugins/geometry/primitives/ShapeGeometryGenerator.ts, src/plugins/geometry/primitives/TubeShapeGeometryGenerator.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 plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:297— `material.setDirty && material.setDirty()` appears character-identically in 2 files — plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts, src/plugins/material/CustomBumpMapPlugin.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 plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:95— `p.uiConfig && p.uiConfig.hidden === undefined` appears character-identically in 2 files — plugins/blueprintjs/src/BlueprintJsUiPlugin.ts, plugins/tweakpane/src/TweakpaneUiPlugin.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 src/plugins/pipeline/DepthBufferPlugin.ts:223— `renderer.resetCurrentMaterial && renderer.resetCurrentMaterial()` appears character-identically in 3 files — src/plugins/pipeline/DepthBufferPlugin.ts, src/plugins/pipeline/GBufferMaterial.ts, src/plugins/pipeline/NormalBufferPlugin.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 src/plugins/material/ClearcoatTintPlugin.ts:78— `shader.defines && (shader.defines.USE_UV = '')` appears character-identically in 3 files — src/plugins/material/ClearcoatTintPlugin.ts, src/plugins/material/CustomBumpMapPlugin.ts, src/plugins/material/NoiseBumpMaterialPlugin.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 src/core/camera/OrthographicCamera2.ts:306— `this._controls.dispose && this._controls.dispose()` appears character-identically in 2 files — src/core/camera/OrthographicCamera2.ts, src/core/camera/PerspectiveCamera2.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 src/core/camera/OrthographicCamera2.ts:305— `this._controls.removeEventListener && this._controls.removeEventListener('change', this._controlsChanged)` appears character-identically in 2 files — src/core/camera/OrthographicCamera2.ts, src/core/camera/PerspectiveCamera2.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 src/core/camera/OrthographicCamera2.ts:296— `this._controls?.addEventListener && this._controls.addEventListener('change', this._controlsChanged)` appears character-identically in 2 files — src/core/camera/OrthographicCamera2.ts, src/core/camera/PerspectiveCamera2.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 src/core/camera/OrthographicCamera2.ts:315— `this._currentControlsMode !== this.controlsMode || this !== this._controls.object || this._controls.domElement && this._canvas !== this._con…` appears character-identically in 2 files — src/core/camera/OrthographicCamera2.ts, src/core/camera/PerspectiveCamera2.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 src/core/camera/OrthographicCamera2.ts:219— `this._interactionsDisabledBy.size === 0 && this.isMainCamera && this.controlsMode !== ''` appears character-identically in 2 files — src/core/camera/OrthographicCamera2.ts, src/core/camera/PerspectiveCamera2.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 src/plugins/interaction/PivotControlsPlugin.ts:167— `this._multi.hasMultiSelect && this._multi.hasStartStates` appears character-identically in 2 files — src/plugins/interaction/PivotControlsPlugin.ts, src/plugins/interaction/TransformControlsPlugin.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 src/plugins/interaction/PivotControlsPlugin.ts:173— `this._transformState.obj !== object || !this.undoManager` appears character-identically in 2 files — src/plugins/interaction/PivotControlsPlugin.ts, src/plugins/interaction/TransformControlsPlugin.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 src/plugins/pipeline/DepthBufferPlugin.ts:122— `this._viewer.renderManager.zPrepass && this.isPrimaryGBuffer && rm.msaa` appears character-identically in 2 files — src/plugins/pipeline/DepthBufferPlugin.ts, src/plugins/pipeline/GBufferPlugin.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 src/plugins/interaction/PivotControlsPlugin.ts:106— `typeof (controls as any)?.stopDamping === 'function' && controls?.enabled` appears character-identically in 3 files — src/plugins/interaction/PivotControlsPlugin.ts, src/plugins/interaction/PivotEditPlugin.ts, src/plugins/interaction/TransformControlsPlugin.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 src/plugins/extras/components/componentTypes.ts:58— `typeof t === 'number' || typeof t === 'boolean'` appears character-identically in 2 files — src/plugins/extras/components/componentTypes.ts, src/plugins/extras/components/setupComponent.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 plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts:149— `viewer.getPlugin('Ground') || viewer.getPlugin('BaseGroundPlugin')` appears character-identically in 2 files — plugins/webgi-plugins/src/plugins/postprocessing/SSGIPlugin.ts, plugins/webgi-plugins/src/plugins/postprocessing/SSReflectionPlugin.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.
Documentation: no build, run or usage example plugins/3d-tiles-renderer/README.md:1— `3d-tiles-renderer` is a published package (`package.json` without `"private": true`) and neither `plugins/3d-tiles-renderer/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/assimpjs/README.md:1— `assimpjs` is a published package (`package.json` without `"private": true`) and neither `plugins/assimpjs/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/blueprintjs/README.md:1— `blueprintjs` is a published package (`package.json` without `"private": true`) and neither `plugins/blueprintjs/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/configurator/README.md:1— `configurator` is a published package (`package.json` without `"private": true`) and neither `plugins/configurator/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/extra-importers/README.md:1— `extra-importers` is a published package (`package.json` without `"private": true`) and neither `plugins/extra-importers/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/gaussian-splatting/README.md:1— `gaussian-splatting` is a published package (`package.json` without `"private": true`) and neither `plugins/gaussian-splatting/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/geometry-generator/README.md:1— `geometry-generator` is a published package (`package.json` without `"private": true`) and neither `plugins/geometry-generator/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/gltf-transform/README.md:1— `gltf-transform` is a published package (`package.json` without `"private": true`) and neither `plugins/gltf-transform/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/network/README.md:1— `network` is a published package (`package.json` without `"private": true`) and neither `plugins/network/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/path-tracing/README.md:1— `path-tracing` is a published package (`package.json` without `"private": true`) and neither `plugins/path-tracing/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/plugin-template-vite/README.md:1— `plugin-template-vite` is a published package (`package.json` without `"private": true`) and neither `plugins/plugin-template-vite/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/r3f/README.md:1— `r3f` is a published package (`package.json` without `"private": true`) and neither `plugins/r3f/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/svg-renderer/README.md:1— `svg-renderer` is a published package (`package.json` without `"private": true`) and neither `plugins/svg-renderer/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/timeline-ui/README.md:1— `timeline-ui` is a published package (`package.json` without `"private": true`) and neither `plugins/timeline-ui/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/troika-text/README.md:1— `troika-text` is a published package (`package.json` without `"private": true`) and neither `plugins/troika-text/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/tweakpane/README.md:1— `tweakpane` is a published package (`package.json` without `"private": true`) and neither `plugins/tweakpane/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/tweakpane-editor/README.md:1— `tweakpane-editor` is a published package (`package.json` without `"private": true`) and neither `plugins/tweakpane-editor/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example plugins/webgi-plugins/README.md:1— `webgi-plugins` is a published package (`package.json` without `"private": true`) and neither `plugins/webgi-plugins/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Deprecated: @humanwhocodes/config-array REDACTED:1414— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:1444— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". 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:7104— 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: glob REDACTED:7387— 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:7881— 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: glob REDACTED:10976— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Blanket warning suppression src/assetmanager/import/MTLLoader2.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/assetmanager/import/MTLLoader2.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/assetmanager/import/OBJLoader2.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/assetmanager/import/OBJLoader2.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/three/controls/PivotControls.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression REDACTED:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Fat interface: ICamera (26 required operations) src/core/ICamera.ts:57— `ICamera` declares 26 required operations: `setDirty`, `activateMain`, `deactivateMain`, `refreshTarget`, `refreshAspect`, `setInteractions`, `setControlsCtor`, `removeControlsCtor`, `refreshCameraControls`, `updateProjectionMatrix`, `getView`, `setView`, `fitObject`, `setViewFromCamera`, `setViewToMain`, `setCanvas`, `traverse`, `traverseVisible`, `traverseAncestors`, `getObjectById`, `getObjectByName`, `getObjectByProperty`, `copy`, `clone`, `add`, `remove`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D21 · Naming Consistency· `matToJson` spells `Json` where 90 names in the project spell it `JSON` · ×1
`matToJson` spells `Json` where 90 names in the project spell it `JSON` src/assetmanager/AssetExporter.ts:199— 90 of 91 names in project threepipe spell the token `JSON` (90 of 91; unit: names in project threepipe containing `JSON`). Peers: GridItemListPlugin.toJSON (plugins/configurator/src/GridItemListPlugin.ts:9); ThreeGaussianSplatPlugin.toJSON (plugins/gaussian-splatting/src/three-gaussian-splat/ThreeGaussianSplatPlugin.ts:22); GeometryGeneratorExtrasPlugin.toJSON (plugins/geometry-generator/src/GeometryGeneratorExtrasPlugin.ts:21); plugins.gltf-transform.src.GLTFDracoExporterBase.ViewerJSONExtensionProperty (plugins/gltf-transform/src/GLTFDracoExporterBase.ts:153); GLTFSpecGlossinessConverterPluginBase.toJSON (plugins/gltf-transform/src/GLTFSpecGlossinessConverterPluginBase.ts:20). Rename to `matToJSON`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion package.json:1— `(repository root)` (62006 LoC, 752 module-visible types across 244 directories) overshoots its size bounds. 1 of 20 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 9.0/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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body plugins/blend-importer/src/js-blend/parser/parser.js:32— `onParseReady` has an empty body — confirm it's an intentional no-op and not an unfinished method.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
README/code drift README.md:140— README.md names TypeScript 6, but the manifest declares `typescript` 5.8.3. 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.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation package.json:117— `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`.
Unused export 'GroundPlugin' plugins/webgi-plugins/src/plugins/extras/AdvancedGroundPlugin.ts:385— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused private method '_setupPluginSerializationContext' · ×1
Unused private method '_setupPluginSerializationContext' plugins/blueprintjs/src/BlueprintJsUiPlugin.ts:103— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
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.8 `!` null assertions per 1k TypeScript source lines — 199 assertion(s) across the 71331 source line(s) of the 395 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: src/plugins/interaction/PivotControlsPlugin.ts (10), src/plugins/interaction/TransformControlsPlugin.ts (10), plugins/blend-importer/src/loader/light.ts (9). 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-three/fiber — @react-three/fiber is pinned at 9.3.0; registry.npmjs.org publishes 9.8.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): @types/emscripten — @types/emscripten is pinned at 1.39.10; registry.npmjs.org publishes 1.41.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): @types/three — @types/three is pinned at 0.168.10003; 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): @types/wicg-file-system-access — @types/wicg-file-system-access is pinned at 2020.9.8; registry.npmjs.org publishes 2023.10.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): aws4fetch — aws4fetch is pinned at 1.0.18; registry.npmjs.org publishes 1.0.20 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): comlink — comlink is pinned at 4.4.1; registry.npmjs.org publishes 4.4.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): react — react is pinned at 19.1.1; registry.npmjs.org publishes 19.3.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): ts-browser-helpers — ts-browser-helpers is pinned at 0.20.0; registry.npmjs.org publishes 0.23.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): uiconfig.js — uiconfig.js is pinned at 0.4.0; registry.npmjs.org publishes 0.4.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.
doc comments repeat the names plugins/gltf-transform/src/GLTFDracoExportPlugin.ts:91— 0 of 1 documented parameters and 0 of 10 summaries in `@threepipe/plugin-gltf-transform` only repeat the member or parameter name (e.g. "" for `name`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names plugins/network/src/TransfrSharePlugin.ts:47— 0 of 3 documented parameters and 0 of 5 summaries in `@threepipe/plugin-network` only repeat the member or parameter name (e.g. "" for `model`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names plugins/svg-renderer/src/BasicSVGRendererPlugin.ts:26— 0 of 4 documented parameters and 0 of 12 summaries in `@threepipe/plugin-svg-renderer` only repeat the member or parameter name (e.g. "" for `enabled`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts:385— 0 of 9 documented parameters and 3 of 31 summaries in `@threepipe/webgi-plugins` only repeat the member or parameter name (e.g. "Anisotropy factor" for `_anisotropyFactor`). 7 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/assetmanager/MaterialManager.ts:239— 4 of 575 documented parameters and 13 of 809 summaries in `threepipe` only repeat the member or parameter name (e.g. "copyProps from material to c" for `copyMaterialProps`). 308 documentation tag(s) are empty. 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 55 file(s) — `plugins/3d-tiles-renderer/src/gltf.ts`, `plugins/geometry-generator/src/FontLibrary.ts`, `plugins/geometry-generator/src/index.ts`, `plugins/path-tracing/src/WebGLPathTracer2.ts`, `plugins/webgi-plugins/src/plugins/extras/AnisotropyPlugin.ts`, … (+50 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1eaee-cc95-7525-9c0e-5b94a82bb1d3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 52 · Warnings: 1125 · Recommendations: 101 · Info: 14 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 19:14 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.