Executive summary
pmndrs/drei is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 47 out of 100, which the At risk rating leaves unchanged.
Code Health, at 28, is the weakest lens and counts most in the score. The best first steps are removing the copied code and simplifying the most tangled functions, each worth about 5 points. Raising Code Health to 70 would lift the score to about 63.
Forty-three 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 one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, pinning each tool to an exact version and setting a waiting period for automatic updates would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code.
The product code is 69,864 lines, about €63,000 to rebuild.
If Code Health rose from 28 to 70, the lowest score rated Strong, the score would rise from 47 to about 63.
New since the last survey: 31 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling clique: DeviceOrientationControls.tsx, FlyControls.tsx, MapControls.tsx, OrbitControls.tsx, PointerLockControls.tsx, TrackballControls.tsx src/core/DeviceOrientationControls.tsx
- Cyclomatic Complexity · Complex function hb (cyclomatic 77, cognitive 539) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Db (cyclomatic 74, cognitive 364) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Ib (cyclomatic 74, cognitive 239) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function lb (cyclomatic 70, cognitive 383) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function ib (cyclomatic 68, cognitive 435) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function wb (cyclomatic 68, cognitive 312) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Cb (cyclomatic 66, cognitive 244) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function tb (cyclomatic 64, cognitive 269) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function dc (cyclomatic 61, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function zb (cyclomatic 58, cognitive 243) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function DracoDecoderModule (cyclomatic 56, cognitive 77) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Eb (cyclomatic 55, cognitive 242) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function kb (cyclomatic 55, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function $b (cyclomatic 54, cognitive 185) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function cc (cyclomatic 54, cognitive 185) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Fb (cyclomatic 53, cognitive 220) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Jb (cyclomatic 49, cognitive 188) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Kb (cyclomatic 49, cognitive 188) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Lb (cyclomatic 48, cognitive 260) .storybook/public/draco-gltf/draco_decoder.js
- Cyclomatic Complexity · Complex function Rb (cyclomatic 48, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js
Fixed since the last survey: 910 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Change Coupling · Change-coupling hub: DeviceOrientationControls.tsx → FlyControls.tsx, MapControls.tsx, PointerLockControls.tsx, TrackballControls.tsx src/core/DeviceOrientationControls.tsx
- Change Coupling · Change-coupling hub: OrbitControls.tsx → CameraShake.tsx, DeviceOrientationControls.tsx, FlyControls.tsx, MapControls.tsx, PointerLockControls.tsx, TrackballControls.tsx src/core/OrbitControls.tsx
- Change Coupling · Change-coupling hub: FlyControls.tsx → MapControls.tsx, PointerLockControls.tsx, TrackballControls.tsx src/core/FlyControls.tsx
- Change Coupling · Change coupling: MapControls.tsx ↔ TrackballControls.tsx src/core/MapControls.tsx
- Change Coupling · Change coupling: MapControls.tsx ↔ PointerLockControls.tsx src/core/MapControls.tsx
- Change Coupling · Change coupling: PointerLockControls.tsx ↔ TrackballControls.tsx src/core/PointerLockControls.tsx
- Code Duplication · Duplicated block (37 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (37 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (37 lines × 5 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (36 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (36 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (35 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (35 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (35 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (34 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (34 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (34 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (33 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (33 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (32 lines × 13 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (32 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (32 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (31 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (31 lines × 6 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (31 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (30 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (30 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (30 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (30 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (29 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (29 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (29 lines × 10 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (29 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (28 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (28 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (28 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (28 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (27 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (27 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (27 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (27 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (26 lines × 10 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (26 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (26 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (25 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (25 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (25 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (25 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (24 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (23 lines × 2 locations) .storybook/public/draco-gltf/draco_wasm_wrapper.js
- Code Duplication · Duplicated block (22 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (22 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (22 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (22 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (22 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (22 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block with local edits (22 matched lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (21 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (21 lines × 6 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (21 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (21 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (21 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (20 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (20 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (20 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (20 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (20 lines × 6 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 3 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js
- Code Duplication · Duplicated block (19 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js
Rebuild cost: about €63,000 · Estimate
| Cost to rebuild | €21,000 to €110,000, for 351 to 1,112 hours of work, about 0.4 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 47. 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: 69,864 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 sandboxes.bug-report-template-starter | 2 src.core.AccumulativeShadows | 3 src.core.Bounds | 4 src.core.Bvh | 5 src.core.CameraControls | 6 src.core.CameraShake | 7 src.core.Caustics | 8 src.core.Cloud | 9 src.core.CurveModifier | 10 src.core.Effects | 11 src.core.Environment | 12 src.core.Gltf | 13 src.core.GradientTexture | 14 src.core.Grid | 15 src.core.Image | 16 src.core.Instances | 17 src.core.MeshDiscardMaterial | 18 src.core.MeshDistortMaterial | 19 src.core.MeshPortalMaterial | 20 src.core.MeshReflectorMaterial | 21 src.core.MeshRefractionMaterial | 22 src.core.MeshTransmissionMaterial | 23 src.core.PointMaterial | 24 src.core.ShadowAlpha | 25 src.core.SpotLight | 26 src.core.Texture | 27 src.core.useBoxProjectedEnv | 28 src.core.useFont | 29 src.helpers.useEffectfulState | 30 src.materials.ConvolutionMaterial | 31 src.materials.WireframeMaterial | 32 src.web.Html | 33 src.web.Loader | 34 src.web.ScrollControls | 35 src.core | 36 src.core.MeshWobbleMaterial | 37 src.helpers | 38 src.materials | 39 src.materials.BlurPass | 40 src.web |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 sandboxes.bug-report-template-starter | ||||||||||||||||||||||||||||||||||||||||
| 2 src.core.AccumulativeShadows | ||||||||||||||||||||||||||||||||||||||||
| 3 src.core.Bounds | ||||||||||||||||||||||||||||||||||||||||
| 4 src.core.Bvh | ||||||||||||||||||||||||||||||||||||||||
| 5 src.core.CameraControls | ||||||||||||||||||||||||||||||||||||||||
| 6 src.core.CameraShake | ||||||||||||||||||||||||||||||||||||||||
| 7 src.core.Caustics | ||||||||||||||||||||||||||||||||||||||||
| 8 src.core.Cloud | ||||||||||||||||||||||||||||||||||||||||
| 9 src.core.CurveModifier | ||||||||||||||||||||||||||||||||||||||||
| 10 src.core.Effects | ||||||||||||||||||||||||||||||||||||||||
| 11 src.core.Environment | ||||||||||||||||||||||||||||||||||||||||
| 12 src.core.Gltf | ||||||||||||||||||||||||||||||||||||||||
| 13 src.core.GradientTexture | ||||||||||||||||||||||||||||||||||||||||
| 14 src.core.Grid | ||||||||||||||||||||||||||||||||||||||||
| 15 src.core.Image | ||||||||||||||||||||||||||||||||||||||||
| 16 src.core.Instances | ||||||||||||||||||||||||||||||||||||||||
| 17 src.core.MeshDiscardMaterial | ||||||||||||||||||||||||||||||||||||||||
| 18 src.core.MeshDistortMaterial | ||||||||||||||||||||||||||||||||||||||||
| 19 src.core.MeshPortalMaterial | ||||||||||||||||||||||||||||||||||||||||
| 20 src.core.MeshReflectorMaterial | ||||||||||||||||||||||||||||||||||||||||
| 21 src.core.MeshRefractionMaterial | ||||||||||||||||||||||||||||||||||||||||
| 22 src.core.MeshTransmissionMaterial | ||||||||||||||||||||||||||||||||||||||||
| 23 src.core.PointMaterial | ||||||||||||||||||||||||||||||||||||||||
| 24 src.core.ShadowAlpha | ||||||||||||||||||||||||||||||||||||||||
| 25 src.core.SpotLight | ||||||||||||||||||||||||||||||||||||||||
| 26 src.core.Texture | ||||||||||||||||||||||||||||||||||||||||
| 27 src.core.useBoxProjectedEnv | ||||||||||||||||||||||||||||||||||||||||
| 28 src.core.useFont | ||||||||||||||||||||||||||||||||||||||||
| 29 src.helpers.useEffectfulState | ||||||||||||||||||||||||||||||||||||||||
| 30 src.materials.ConvolutionMaterial | ||||||||||||||||||||||||||||||||||||||||
| 31 src.materials.WireframeMaterial | ||||||||||||||||||||||||||||||||||||||||
| 32 src.web.Html | ||||||||||||||||||||||||||||||||||||||||
| 33 src.web.Loader | ||||||||||||||||||||||||||||||||||||||||
| 34 src.web.ScrollControls | ||||||||||||||||||||||||||||||||||||||||
| 35 src.core | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 36 src.core.MeshWobbleMaterial | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 src.helpers | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 src.materials | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 src.materials.BlurPass | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 src.web | 1 | 1 | 1 |
35→4 src.core uses src.core.Bvh✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.Bvh.
- The types involved
src.core.Bvh→src.core.Bvh.BVHOptions
- Direction
- src.core uses src.core.Bvh, so a change to src.core.Bvh can break src.core, while a change to src.core can't break src.core.Bvh.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→9 src.core uses src.core.CurveModifier✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.CurveModifier.
- The types involved
src.core.CurveModifier→src.core.CurveModifier.CurveModifierProps
- Direction
- src.core uses src.core.CurveModifier, so a change to src.core.CurveModifier can break src.core, while a change to src.core can't break src.core.CurveModifier.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→12 src.core uses src.core.Gltf✕
- Connections
- 2 pairs of types, where a type in src.core uses a type in src.core.Gltf.
- The types involved
src.core.Gltf→src.core.Gltf.Pathsrc.core.Gltf→src.core.Gltf.UseDraco
- Direction
- src.core uses src.core.Gltf, so a change to src.core.Gltf can break src.core, while a change to src.core can't break src.core.Gltf.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→24 src.core uses src.core.ShadowAlpha✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.ShadowAlpha.
- The types involved
src.core.ShadowAlpha→src.core.ShadowAlpha.ShadowAlphaProps
- Direction
- src.core uses src.core.ShadowAlpha, so a change to src.core.ShadowAlpha can break src.core, while a change to src.core can't break src.core.ShadowAlpha.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→25 src.core uses src.core.SpotLight✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.SpotLight.
- The types involved
src.core.SpotLight→src.core.SpotLight.ShadowMeshProps
- Direction
- src.core uses src.core.SpotLight, so a change to src.core.SpotLight can break src.core, while a change to src.core can't break src.core.SpotLight.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→26 src.core uses src.core.Texture✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.Texture.
- The types involved
src.core.Texture→src.core.Texture.MappedTextureType
- Direction
- src.core uses src.core.Texture, so a change to src.core.Texture can break src.core, while a change to src.core can't break src.core.Texture.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→27 src.core uses src.core.useBoxProjectedEnv✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.useBoxProjectedEnv.
- The types involved
src.core.useBoxProjectedEnv→src.core.useBoxProjectedEnv.MaterialShader
- Direction
- src.core uses src.core.useBoxProjectedEnv, so a change to src.core.useBoxProjectedEnv can break src.core, while a change to src.core can't break src.core.useBoxProjectedEnv.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
35→28 src.core uses src.core.useFont✕
- Connections
- 1 pair of types, where a type in src.core uses a type in src.core.useFont.
- The types involved
src.core.useFont→src.core.useFont.FontInput
- Direction
- src.core uses src.core.useFont, so a change to src.core.useFont can break src.core, while a change to src.core can't break src.core.useFont.
- Position
- Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
36→18 src.core.MeshWobbleMaterial uses src.core.MeshDistortMaterial✕
- Connections
- 1 pair of types, where a type in src.core.MeshWobbleMaterial uses a type in src.core.MeshDistortMaterial.
- The types involved
src.core.MeshWobbleMaterial.WobbleMaterialImpl→src.core.MeshDistortMaterial.Uniform
- Direction
- src.core.MeshWobbleMaterial uses src.core.MeshDistortMaterial, so a change to src.core.MeshDistortMaterial can break src.core.MeshWobbleMaterial, while a change to src.core.MeshWobbleMaterial can't break src.core.MeshDistortMaterial.
- Position
- Below the diagonal: src.core.MeshWobbleMaterial uses a module listed above it, which is the healthy direction.
37→29 src.helpers uses src.helpers.useEffectfulState✕
- Connections
- 1 pair of types, where a type in src.helpers uses a type in src.helpers.useEffectfulState.
- The types involved
src.helpers.useEffectfulState→src.helpers.useEffectfulState.RefType
- Direction
- src.helpers uses src.helpers.useEffectfulState, so a change to src.helpers.useEffectfulState can break src.helpers, while a change to src.helpers can't break src.helpers.useEffectfulState.
- Position
- Below the diagonal: src.helpers uses a module listed above it, which is the healthy direction.
38→31 src.materials uses src.materials.WireframeMaterial✕
- Connections
- 1 pair of types, where a type in src.materials uses a type in src.materials.WireframeMaterial.
- The types involved
src.materials.WireframeMaterial→src.materials.WireframeMaterial.WireframeMaterialProps
- Direction
- src.materials uses src.materials.WireframeMaterial, so a change to src.materials.WireframeMaterial can break src.materials, while a change to src.materials can't break src.materials.WireframeMaterial.
- Position
- Below the diagonal: src.materials uses a module listed above it, which is the healthy direction.
39→30 src.materials.BlurPass uses src.materials.ConvolutionMaterial✕
- Connections
- 1 pair of types, where a type in src.materials.BlurPass uses a type in src.materials.ConvolutionMaterial.
- The types involved
src.materials.BlurPass.BlurPass→src.materials.ConvolutionMaterial.ConvolutionMaterial
- Direction
- src.materials.BlurPass uses src.materials.ConvolutionMaterial, so a change to src.materials.ConvolutionMaterial can break src.materials.BlurPass, while a change to src.materials.BlurPass can't break src.materials.ConvolutionMaterial.
- Position
- Below the diagonal: src.materials.BlurPass uses a module listed above it, which is the healthy direction.
40→32 src.web uses src.web.Html✕
- Connections
- 1 pair of types, where a type in src.web uses a type in src.web.Html.
- The types involved
src.web.Html→src.web.Html.HtmlProps
- Direction
- src.web uses src.web.Html, so a change to src.web.Html can break src.web, while a change to src.web can't break src.web.Html.
- Position
- Below the diagonal: src.web uses a module listed above it, which is the healthy direction.
40→33 src.web uses src.web.Loader✕
- Connections
- 1 pair of types, where a type in src.web uses a type in src.web.Loader.
- The types involved
src.web.Loader→src.web.Loader.LoaderOptions
- Direction
- src.web uses src.web.Loader, so a change to src.web.Loader can break src.web, while a change to src.web can't break src.web.Loader.
- Position
- Below the diagonal: src.web uses a module listed above it, which is the healthy direction.
40→34 src.web uses src.web.ScrollControls✕
- Connections
- 1 pair of types, where a type in src.web uses a type in src.web.ScrollControls.
- The types involved
src.web.ScrollControls→src.web.ScrollControls.ScrollProps
- Direction
- src.web uses src.web.ScrollControls, so a change to src.web.ScrollControls can break src.web, while a change to src.web can't break src.web.ScrollControls.
- Position
- Below the diagonal: src.web uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 73 | High / Critical |
| A05:2025 — Injection | 12 | High / Critical |
Roadmap
Top priorities: 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; Resolve the 40 finding(s) in Cyclomatic Complexity; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.0 pts | Medium | Code Duplication |
| Resolve the 40 finding(s) in Cyclomatic Complexity. | +5.0 pts | Medium | Cyclomatic Complexity |
| Resolve the 5 redundant comment finding(s) in Comment Value — start with Facemesh.tsx (2), AccumulativeShadows.tsx, SpriteAnimator.tsx. | +2.2 pts | Low | Comment Value |
| 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. | +3.2 pts | Medium | Architecture documentation |
| Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for. | +3.2 pts | Medium | Incompleteness & stubs |
| Resolve the 86 Orphaned file finding(s) in Knowledge Freshness — start with MeshReflectorMaterial.tsx (2), MeshRefractionMaterial.tsx (2), Caustics.tsx. | +3.0 pts | Medium | Knowledge Freshness |
| Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up. | +1.8 pts | Medium | Cancellation propagation |
| Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with package.json (6). | +0.9 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| package.json | 6.6 | Mixed | Dependency Hygiene: Deprecated: @babel/plugin-proposal-class-properties |
| src/core/Instances.tsx | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/core/GizmoHelper.tsx | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/core/MeshDistortMaterial.tsx | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/core/MeshWobbleMaterial.tsx | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/core/shaderMaterial.tsx | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/core/useBoxProjectedEnv.tsx | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/core/DeviceOrientationControls.tsx | 8.5 | Near-clean | Change Coupling: Change coupling clique: DeviceOrientationControls.tsx, FlyControls.tsx, MapControls.tsx, OrbitControls.tsx, PointerLockControls.tsx, TrackballControls.tsx |
| src/web/Facemesh.tsx | 9.3 | Near-clean | Comment Value: redundant comment |
| src/core/AccumulativeShadows.tsx | 9.5 | Near-clean | Comment Value: redundant comment |
| src/core/SpriteAnimator.tsx | 9.5 | Near-clean | Comment Value: redundant comment |
| src/core/useSpriteLoader.tsx | 9.5 | Near-clean | Comment Value: redundant comment |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 57 dimensions across the health lenses
- 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, 347 of 375 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.js, .ts) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.js, .ts) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D8 Code Coverage — 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. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.ts, .tsx) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but every JavaScript/TypeScript test package this repository declares runs its suite in a real browser, which the re-runner has no way to launch. the root package declares `@playwright/test` and its `scripts.test` is `yarn eslint:ci && yarn typecheck && yarn prettier && (cd test/e2e; ./e2e.sh 0.180)`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's browser-driven test support, not a missing .ts/.tsx runner and not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (src/native/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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. `.storybook/stories/AccumulativeShadows.stories.tsx`, `.storybook/stories/Adaptive.stories.tsx`, `.storybook/stories/ArcballControls.stories.tsx`, `.storybook/stories/BBAnchor.stories.tsx`, `.storybook/stories/Billboard.stories.tsx`, … (+106 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 112 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- IC1 Incompleteness & stubs — 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. 256 further occurrence(s) are not listed individually; the score already reflects all 296.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 640 further occurrence(s) are not listed individually; the score already reflects all 680.
- 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. 190 further occurrence(s) are not listed individually; the score already reflects all 230.
- 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. 169 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- 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.
Dimensions
D5 · Coupling
2 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 1 of the 2 (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).
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.
D12 · Dependency Hygiene
13 outdated direct production npm dependency(ies) of 21 graded, 4 pinning defect(s), across 2 package.json (2 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 6 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.
What to do
- Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with package.json (6). — One of this dimension's main actionable groups (6 warning-level).
- 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 4 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 58 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 58 package(s) this repository's committed lockfile installs for a consumer — its 22 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 56 `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. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/core/softShadows.tsx. Counted over 123 of the 285 production source files in this repository: 160 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
D17 · Explicit Debt
6 deducted task-comment markers across 18357 LoC (0.0/KLoC) → score 9.9. 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.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with GizmoHelper.tsx, Instances.tsx, shaderMaterial.tsx. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with MeshDistortMaterial.tsx, MeshWobbleMaterial.tsx, useBoxProjectedEnv.tsx. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 136 document(s) read across 2 unit(s).
D24 · Comment Value
5 of 280 judged comments only repeat the code they sit on (1.8 %). 17 comment(s) in another language or script were not judged.
What to do
- Resolve the 5 redundant comment finding(s) in Comment Value — start with Facemesh.tsx (2), AccumulativeShadows.tsx, SpriteAnimator.tsx. — One of this dimension's main actionable groups (5 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. 9 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 115 file(s) — `.storybook/public/draco-gltf/draco_wasm_wrapper.js`, `.storybook/stories/AccumulativeShadows.stories.tsx` (lines 11–77), `.storybook/stories/Adaptive.stories.tsx` (lines 11–30, lines 77–86), `.storybook/stories/ArcballControls.stories.tsx` (lines 10–89), `.storybook/stories/BBAnchor.stories.tsx` (lines 21–23, line 25, lines 25–29, …), … (+110 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
66 finding(s): 4 critical, 39 high, 16 medium, 7 low.
What to do
- Resolve the 38 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (38). — One of this dimension's main actionable groups (38 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
89 of 125 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is .storybook/public/draco-gltf/draco_decoder.js. Counted over 125 of the 285 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 86 Orphaned file finding(s) in Knowledge Freshness — start with MeshReflectorMaterial.tsx (2), MeshRefractionMaterial.tsx (2), Caustics.tsx. — One of this dimension's main actionable groups (86 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with draco_decoder.js, draco_wasm_wrapper.js, Splat.tsx. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: DeviceOrientationControls.tsx↔PointerLockControls.tsx 77%; MapControls.tsx↔OrbitControls.tsx 69%; Instances.tsx↔Points.tsx 67%
What to do
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with DeviceOrientationControls.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Instances.tsx. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 21 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.
Frontend & cross-cutting dimensions
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — sandboxes/bug-report-template-starter/public/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A branch guarded by a literal `false` can never execute — left-over disabled code. Remove it or restore the real condition. (×40) — .storybook/public/draco-gltf/draco_decoder.js:1763, .storybook/public/draco-gltf/draco_decoder.js:1783, .storybook/public/draco-gltf/draco_decoder.js:1797, …
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)
M2 · Architecture documentation
- 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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- 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 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:10
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
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.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 5 duplicated blocks under src/ have copies in at least two of the sibling directories core, web — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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/Caustics.tsx:324
- .storybook/public/draco-gltf/draco_decoder.js:4570 · .storybook/public/draco-gltf/draco_decoder.js:4767 · .storybook/public/draco-gltf/draco_decoder.js:4964 · .storybook/public/draco-gltf/draco_decoder.js:5161 · +3 more site(s) not listed — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — .storybook/public/draco-gltf/draco_decoder.js:4570
- .storybook/public/draco-gltf/draco_decoder.js:23968 · .storybook/public/draco-gltf/draco_decoder.js:24899 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:23968
- .storybook/public/draco-gltf/draco_decoder.js:15024 · .storybook/public/draco-gltf/draco_decoder.js:16775 — the two spans are one implementation copied and then locally edited — 772 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. — .storybook/public/draco-gltf/draco_decoder.js:15024
- src/web/pivotControls/AxisArrow.tsx:8 · src/web/pivotControls/ScalingSphere.tsx:9 — the two spans are one implementation copied and then locally edited — 831 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/web/pivotControls/AxisArrow.tsx:8
- .storybook/public/draco-gltf/draco_decoder.js:27704 · .storybook/public/draco-gltf/draco_decoder.js:28276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:27704
- .storybook/public/draco-gltf/draco_decoder.js:1975 · .storybook/public/draco-gltf/draco_decoder.js:2245 · .storybook/public/draco-gltf/draco_decoder.js:2747 · .storybook/public/draco-gltf/draco_decoder.js:2984 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:1975
- .storybook/public/draco-gltf/draco_decoder.js:23480 · .storybook/public/draco-gltf/draco_decoder.js:24559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:23480
- .storybook/public/draco-gltf/draco_decoder.js:30496 · .storybook/public/draco-gltf/draco_decoder.js:30870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:30496
- .storybook/public/draco-gltf/draco_decoder.js:34825 · .storybook/public/draco-gltf/draco_decoder.js:35590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:34825
- src/web/pivotControls/AxisRotator.tsx:57 · src/web/pivotControls/PlaneSlider.tsx:31 — the two spans are one implementation copied and then locally edited — 729 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/web/pivotControls/AxisRotator.tsx:57
- .storybook/public/draco-gltf/draco_decoder.js:12188 · .storybook/public/draco-gltf/draco_decoder.js:12327 · .storybook/public/draco-gltf/draco_decoder.js:12466 · .storybook/public/draco-gltf/draco_decoder.js:12605 · +3 more site(s) not listed — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — .storybook/public/draco-gltf/draco_decoder.js:12188
- .storybook/public/draco-gltf/draco_decoder.js:30704 · .storybook/public/draco-gltf/draco_decoder.js:31033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:30704
- .storybook/public/draco-gltf/draco_decoder.js:36051 · .storybook/public/draco-gltf/draco_decoder.js:37171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:36051
- .storybook/public/draco-gltf/draco_decoder.js:27532 · .storybook/public/draco-gltf/draco_decoder.js:28123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:27532
- src/web/pivotControls/AxisArrow.tsx:60 · src/web/pivotControls/PlaneSlider.tsx:56 — the two spans are one implementation copied and then locally edited — 533 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/web/pivotControls/AxisArrow.tsx:60
- .storybook/public/draco-gltf/draco_decoder.js:23679 · .storybook/public/draco-gltf/draco_decoder.js:24370 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — .storybook/public/draco-gltf/draco_decoder.js:23679
- src/web/pivotControls/AxisRotator.tsx:84 · src/web/pivotControls/ScalingSphere.tsx:66 — the two spans are one implementation copied and then locally edited — 449 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/web/pivotControls/AxisRotator.tsx:84
- .storybook/public/draco-gltf/draco_decoder.js:3788 · .storybook/public/draco-gltf/draco_decoder.js:7635 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:3788
- .storybook/public/draco-gltf/draco_decoder.js:5758 · .storybook/public/draco-gltf/draco_decoder.js:6374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:5758
- .storybook/public/draco-gltf/draco_decoder.js:29324 · .storybook/public/draco-gltf/draco_decoder.js:29639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:29324
- .storybook/public/draco-gltf/draco_decoder.js:1917 · .storybook/public/draco-gltf/draco_decoder.js:2187 · .storybook/public/draco-gltf/draco_decoder.js:2692 · .storybook/public/draco-gltf/draco_decoder.js:2929 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — .storybook/public/draco-gltf/draco_decoder.js:1917
- .storybook/public/draco-gltf/draco_decoder.js:37794 · .storybook/public/draco-gltf/draco_decoder.js:37844 · .storybook/public/draco-gltf/draco_decoder.js:37894 · .storybook/public/draco-gltf/draco_decoder.js:37944 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:37794
- .storybook/public/draco-gltf/draco_decoder.js:35308 · .storybook/public/draco-gltf/draco_decoder.js:36459 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:35308
- .storybook/public/draco-gltf/draco_decoder.js:35807 · .storybook/public/draco-gltf/draco_decoder.js:36946 — the two spans are one implementation copied and then locally edited — 467 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. — .storybook/public/draco-gltf/draco_decoder.js:35807
- .storybook/public/draco-gltf/draco_decoder.js:10399 · .storybook/public/draco-gltf/draco_decoder.js:10681 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:10399
- .storybook/public/draco-gltf/draco_decoder.js:35259 · .storybook/public/draco-gltf/draco_decoder.js:36412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:35259
- .storybook/public/draco-gltf/draco_decoder.js:36666 · .storybook/public/draco-gltf/draco_decoder.js:36727 — the two spans are one implementation copied and then locally edited — 334 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. — .storybook/public/draco-gltf/draco_decoder.js:36666
- .storybook/public/draco-gltf/draco_decoder.js:8024 · .storybook/public/draco-gltf/draco_decoder.js:8885 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:8024
- src/core/OrthographicCamera.tsx:8 · src/core/PerspectiveCamera.tsx:8 — the two spans are one implementation copied and then locally edited — 374 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/OrthographicCamera.tsx:8
- .storybook/public/draco-gltf/draco_decoder.js:9095 · .storybook/public/draco-gltf/draco_decoder.js:38953 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:9095
- .storybook/public/draco-gltf/draco_decoder.js:27397 · .storybook/public/draco-gltf/draco_decoder.js:27988 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:27397
- .storybook/public/draco-gltf/draco_decoder.js:36003 · .storybook/public/draco-gltf/draco_decoder.js:37123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:36003
- src/core/MeshDistortMaterial.tsx:14 · src/core/MeshWobbleMaterial.tsx:11 — the two spans are one implementation copied and then locally edited — 252 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/MeshDistortMaterial.tsx:14
- .storybook/public/draco-gltf/draco_decoder.js:27815 · .storybook/public/draco-gltf/draco_decoder.js:28387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:27815
- .storybook/public/draco-gltf/draco_decoder.js:34984 · .storybook/public/draco-gltf/draco_decoder.js:36146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:34984
- .storybook/public/draco-gltf/draco_decoder.js:6750 · .storybook/public/draco-gltf/draco_decoder.js:6888 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .storybook/public/draco-gltf/draco_decoder.js:6750
- .storybook/public/draco-gltf/draco_decoder.js:2819 · .storybook/public/draco-gltf/draco_decoder.js:3056 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:2819
- .storybook/public/draco-gltf/draco_decoder.js:10202 · .storybook/public/draco-gltf/draco_decoder.js:10489 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:10202
- .storybook/public/draco-gltf/draco_decoder.js:43337 · .storybook/public/draco-gltf/draco_decoder.js:43435 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — .storybook/public/draco-gltf/draco_decoder.js:43337
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.
R11 · Import Boundaries
- src/core/PointerLockControls.tsx:2 imports @react-three/fiber/dist/declarations/src/core/events, 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/core/PointerLockControls.tsx:2
- src/web/ScrollControls.tsx:5 imports @react-three/fiber/dist/declarations/src/core/events, 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/web/ScrollControls.tsx:5
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- Ya has cyclomatic complexity 214 and cognitive complexity 1308; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:21872
- Za has cyclomatic complexity 179 and cognitive complexity 1330; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:23176
- _a has cyclomatic complexity 178 and cognitive complexity 1326; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:24130
- ab has cyclomatic complexity 162 and cognitive complexity 1212; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:25845
- eb has cyclomatic complexity 135 and cognitive complexity 607; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:28525
- gb has cyclomatic complexity 131 and cognitive complexity 377; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:29723
- cb has cyclomatic complexity 123 and cognitive complexity 648; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:27362
- db has cyclomatic complexity 121 and cognitive complexity 640; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:27953
- $a has cyclomatic complexity 119 and cognitive complexity 2065; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:25061
- bb has cyclomatic complexity 113 and cognitive complexity 500; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:26839
- fb has cyclomatic complexity 90 and cognitive complexity 647; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:29171
- jb has cyclomatic complexity 85 and cognitive complexity 322; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:31158
- mb has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:32379
- nb has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:32748
- ob has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:33117
- pb has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:33486
- qb has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:33855
- rb has cyclomatic complexity 81 and cognitive complexity 302; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:34224
- xb has cyclomatic complexity 80 and cognitive complexity 388; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:36505
- Ab has cyclomatic complexity 79 and cognitive complexity 319; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:37666
- hb has cyclomatic complexity 77 and cognitive complexity 539; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:30452
- Db has cyclomatic complexity 74 and cognitive complexity 364; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:38684
- Ib has cyclomatic complexity 74 and cognitive complexity 239; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:1580
- lb has cyclomatic complexity 70 and cognitive complexity 383; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:31973
- ib has cyclomatic complexity 68 and cognitive complexity 435; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:30830
- wb has cyclomatic complexity 68 and cognitive complexity 312; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:36112
- Cb has cyclomatic complexity 66 and cognitive complexity 244; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:38294
- tb has cyclomatic complexity 64 and cognitive complexity 269; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:34947
- dc has cyclomatic complexity 61 and cognitive complexity 221; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:6528
- zb has cyclomatic complexity 58 and cognitive complexity 243; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:37232
- DracoDecoderModule has cyclomatic complexity 56 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:1
- Eb has cyclomatic complexity 55 and cognitive complexity 242; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:38994
- kb has cyclomatic complexity 55 and cognitive complexity 221; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:31572
- $b has cyclomatic complexity 54 and cognitive complexity 185; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:5690
- cc has cyclomatic complexity 54 and cognitive complexity 185; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:6306
- Fb has cyclomatic complexity 53 and cognitive complexity 220; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:39260
- Jb has cyclomatic complexity 49 and cognitive complexity 188; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:1864
- Kb has cyclomatic complexity 49 and cognitive complexity 188; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:2134
- Lb has cyclomatic complexity 48 and cognitive complexity 260; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:2404
- Rb has cyclomatic complexity 48 and cognitive complexity 221; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — .storybook/public/draco-gltf/draco_decoder.js:3769
R3 · Large Files
- src/core/Splat.tsx has 607 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/Splat.tsx:1
- src/core/MeshPortalMaterial.tsx 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. — src/core/MeshPortalMaterial.tsx:1
- src/core/SpriteAnimator.tsx has 489 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/SpriteAnimator.tsx:1
- src/core/MeshTransmissionMaterial.tsx has 471 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/MeshTransmissionMaterial.tsx:1
- src/web/Facemesh.tsx has 469 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/web/Facemesh.tsx:1
- src/core/Caustics.tsx has 466 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/Caustics.tsx:1
- src/core/useSpriteLoader.tsx has 427 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/useSpriteLoader.tsx:1
- src/core/AccumulativeShadows.tsx has 417 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/AccumulativeShadows.tsx:1
- src/web/Html.tsx has 417 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/web/Html.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 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. — sandboxes/bug-report-template-starter/src/index.jsx:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/web/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/web/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — src/web/CycleRaycast.tsx:13, src/web/FaceControls.tsx:307, src/web/Select.tsx:177, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
- The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — src/core/VideoTexture.tsx:58
What to do
- `async` Promise executor
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- 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.
- `load` 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/core/Splat.tsx:294
- `loadFontData` 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/core/useFont.tsx:26
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X5 · Nullable reference types
- ~8.4 `!` null assertions per 1k TypeScript source lines — 174 assertion(s) across the 20674 source line(s) of the 166 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/core/Splat.tsx (8), src/web/Html.tsx (7), src/core/Svg.tsx (6). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 28% | Weak — gated by R10, R2, IC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 70% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 7 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
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .ts exposed no member bodies
- D11 Test Reliability — Test reliability not included — no browser-driven test runner (@playwright/test)
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .js, .ts exposed no member bodies
- 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.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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
- D3 God Classes — Most of this repository's production source (.js, .ts) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 111 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 (.js, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (3 module(s), 160 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 169 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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)
Critical — 55 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 175 finding(s)
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:1763
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:1783
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:1797
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2020
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2065
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2290
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2335
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2530
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2584
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2612
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2792
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:2837
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3029
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3074
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3191
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3217
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3291
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3331
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3466
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3512
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3537
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:3953
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:4151
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:4167
- Dead branch — condition is always false .storybook/public/draco-gltf/draco_decoder.js:4526
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: @babel/plugin-proposal-class-properties package.json:74
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator package.json:75
- Deprecated: babel-eslint package.json:100
- Deprecated: eslint package.json:104
- Deprecated: rollup-plugin-multi-input package.json:118
- Deprecated: rollup-plugin-terser package.json:119
- Floating npm dependency: @react-three/fiber
- Floating npm dependency: react
- Floating npm dependency: react-dom
- Floating npm dependency: three
- TodoComment src/core/GizmoHelper.tsx:43
- TodoComment src/core/Instances.tsx:228
- TodoComment src/core/shaderMaterial.tsx:15
- FixmeComment src/core/MeshDistortMaterial.tsx:25
- FixmeComment src/core/MeshWobbleMaterial.tsx:21
- FixmeComment src/core/useBoxProjectedEnv.tsx:52
- Duplicated block (42 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:9095
- Duplicated block (42 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:27397
- Duplicated block (42 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:36003
- Duplicated block (38 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:2819
- Duplicated block (38 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:10202
- Duplicated block (38 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:43337
- REDACTED
- REDACTED
- Duplicated block (50 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js:1917
- Duplicated block (50 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js:37794
- Duplicated block (40 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:27815
- Duplicated block (40 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:34984
- Boundary violation [package:third-party-deep-import] src/core/PointerLockControls.tsx:2
- Boundary violation [package:third-party-deep-import] src/web/ScrollControls.tsx:5
- Async function without AbortSignal: load src/core/Splat.tsx:294
- Async function without AbortSignal: loadFontData src/core/useFont.tsx:26
- Page without a main landmark sandboxes/bug-report-template-starter/public/index.html:2
- Change coupling clique: DeviceOrientationControls.tsx, FlyControls.tsx, MapControls.tsx, OrbitControls.tsx, PointerLockControls.tsx, TrackballControls.tsx src/core/DeviceOrientationControls.tsx
- Change coupling: Instances.tsx ↔ Points.tsx src/core/Instances.tsx:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplication concentrated across 2 sibling directories (5 clone groups) src/core/Caustics.tsx:324
- Duplicated block (172 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js:4570
- Duplicated block (137 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:23968
- Duplicated block with local edits (116 matched lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:15024
- Duplicated block with local edits (112 matched lines × 2 locations) src/web/pivotControls/AxisArrow.tsx:8
- Duplicated block (96 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:27704
- Duplicated block (92 lines × 4 locations) .storybook/public/draco-gltf/draco_decoder.js:1975
- Duplicated block (90 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:23480
- Duplicated block (89 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:30496
- Duplicated block (88 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:34825
- Duplicated block with local edits (86 matched lines × 2 locations) src/web/pivotControls/AxisRotator.tsx:57
- Duplicated block (78 lines × 7 locations) .storybook/public/draco-gltf/draco_decoder.js:12188
- Duplicated block (71 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:30704
- Duplicated block (70 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:36051
- Duplicated block (65 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:27532
- Duplicated block with local edits (64 matched lines × 2 locations) src/web/pivotControls/AxisArrow.tsx:60
- Duplicated block (62 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:23679
- Duplicated block with local edits (58 matched lines × 2 locations) src/web/pivotControls/AxisRotator.tsx:84
- Duplicated block (56 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:3788
- Duplicated block (54 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:5758
- Duplicated block (52 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:29324
- Duplicated block (47 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:35308
- Duplicated block with local edits (46 matched lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:35807
- Duplicated block (45 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:10399
- Duplicated block (44 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:35259
- Duplicated block with local edits (44 matched lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:36666
- Duplicated block (43 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:8024
- Duplicated block with local edits (43 matched lines × 2 locations) src/core/OrthographicCamera.tsx:8
- Duplicated block with local edits (42 matched lines × 2 locations) src/core/MeshDistortMaterial.tsx:14
- Duplicated block (39 lines × 2 locations) .storybook/public/draco-gltf/draco_decoder.js:6750
- Complex function Ya (cyclomatic 214, cognitive 1308) .storybook/public/draco-gltf/draco_decoder.js:21872
- Complex function Za (cyclomatic 179, cognitive 1330) .storybook/public/draco-gltf/draco_decoder.js:23176
- Complex function _a (cyclomatic 178, cognitive 1326) .storybook/public/draco-gltf/draco_decoder.js:24130
- Complex function ab (cyclomatic 162, cognitive 1212) .storybook/public/draco-gltf/draco_decoder.js:25845
- Complex function eb (cyclomatic 135, cognitive 607) .storybook/public/draco-gltf/draco_decoder.js:28525
- Complex function gb (cyclomatic 131, cognitive 377) .storybook/public/draco-gltf/draco_decoder.js:29723
- Complex function cb (cyclomatic 123, cognitive 648) .storybook/public/draco-gltf/draco_decoder.js:27362
- Complex function db (cyclomatic 121, cognitive 640) .storybook/public/draco-gltf/draco_decoder.js:27953
- Complex function $a (cyclomatic 119, cognitive 2065) .storybook/public/draco-gltf/draco_decoder.js:25061
- Complex function bb (cyclomatic 113, cognitive 500) .storybook/public/draco-gltf/draco_decoder.js:26839
- Complex function fb (cyclomatic 90, cognitive 647) .storybook/public/draco-gltf/draco_decoder.js:29171
- Complex function jb (cyclomatic 85, cognitive 322) .storybook/public/draco-gltf/draco_decoder.js:31158
- Complex function mb (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:32379
- Complex function nb (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:32748
- Complex function ob (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:33117
- Complex function pb (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:33486
- Complex function qb (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:33855
- Complex function rb (cyclomatic 81, cognitive 302) .storybook/public/draco-gltf/draco_decoder.js:34224
- Complex function xb (cyclomatic 80, cognitive 388) .storybook/public/draco-gltf/draco_decoder.js:36505
- Complex function Ab (cyclomatic 79, cognitive 319) .storybook/public/draco-gltf/draco_decoder.js:37666
- Complex function hb (cyclomatic 77, cognitive 539) .storybook/public/draco-gltf/draco_decoder.js:30452
- Complex function Db (cyclomatic 74, cognitive 364) .storybook/public/draco-gltf/draco_decoder.js:38684
- Complex function Ib (cyclomatic 74, cognitive 239) .storybook/public/draco-gltf/draco_decoder.js:1580
- Complex function lb (cyclomatic 70, cognitive 383) .storybook/public/draco-gltf/draco_decoder.js:31973
- Complex function ib (cyclomatic 68, cognitive 435) .storybook/public/draco-gltf/draco_decoder.js:30830
- Complex function wb (cyclomatic 68, cognitive 312) .storybook/public/draco-gltf/draco_decoder.js:36112
- Complex function Cb (cyclomatic 66, cognitive 244) .storybook/public/draco-gltf/draco_decoder.js:38294
- Complex function tb (cyclomatic 64, cognitive 269) .storybook/public/draco-gltf/draco_decoder.js:34947
- Complex function dc (cyclomatic 61, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js:6528
- Complex function zb (cyclomatic 58, cognitive 243) .storybook/public/draco-gltf/draco_decoder.js:37232
- Complex function DracoDecoderModule (cyclomatic 56, cognitive 77) .storybook/public/draco-gltf/draco_decoder.js:1
- Complex function Eb (cyclomatic 55, cognitive 242) .storybook/public/draco-gltf/draco_decoder.js:38994
- Complex function kb (cyclomatic 55, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js:31572
- Complex function $b (cyclomatic 54, cognitive 185) .storybook/public/draco-gltf/draco_decoder.js:5690
- Complex function cc (cyclomatic 54, cognitive 185) .storybook/public/draco-gltf/draco_decoder.js:6306
- Complex function Fb (cyclomatic 53, cognitive 220) .storybook/public/draco-gltf/draco_decoder.js:39260
- Complex function Jb (cyclomatic 49, cognitive 188) .storybook/public/draco-gltf/draco_decoder.js:1864
- Complex function Kb (cyclomatic 49, cognitive 188) .storybook/public/draco-gltf/draco_decoder.js:2134
- Complex function Lb (cyclomatic 48, cognitive 260) .storybook/public/draco-gltf/draco_decoder.js:2404
- Complex function Rb (cyclomatic 48, cognitive 221) .storybook/public/draco-gltf/draco_decoder.js:3769
- src/core/Splat.tsx: 607 lines of code src/core/Splat.tsx:1
- src/core/MeshPortalMaterial.tsx: 491 lines of code src/core/MeshPortalMaterial.tsx:1
- src/core/SpriteAnimator.tsx: 489 lines of code src/core/SpriteAnimator.tsx:1
- src/core/MeshTransmissionMaterial.tsx: 471 lines of code src/core/MeshTransmissionMaterial.tsx:1
- src/web/Facemesh.tsx: 469 lines of code src/web/Facemesh.tsx:1
- src/core/Caustics.tsx: 466 lines of code src/core/Caustics.tsx:1
- src/core/useSpriteLoader.tsx: 427 lines of code src/core/useSpriteLoader.tsx:1
- src/core/AccumulativeShadows.tsx: 417 lines of code src/core/AccumulativeShadows.tsx:1
- src/web/Html.tsx: 417 lines of code src/web/Html.tsx:1
- No test reaches this file sandboxes/bug-report-template-starter/src/index.jsx:1
- JavaScript dependencies are not locked sandboxes/bug-report-template-starter/package.json:10
- `async` Promise executor src/core/VideoTexture.tsx:58
Minor — 132 finding(s)
- Orphaned file src/core/Caustics.tsx:1
- Orphaned file src/core/SpriteAnimator.tsx:1
- Orphaned file src/core/MeshPortalMaterial.tsx:1
- Orphaned file src/web/Html.tsx:1
- Orphaned file src/core/useSpriteLoader.tsx:1
- Orphaned file src/core/Instances.tsx:1
- Orphaned file src/core/Cloud.tsx:1
- Orphaned file src/core/Bounds.tsx:1
- Orphaned file src/web/pivotControls/index.tsx:1
- Orphaned file src/web/ScrollControls.tsx:1
- Orphaned file src/web/View.tsx:1
- Orphaned file src/core/MeshReflectorMaterial.tsx:1
- Orphaned file src/core/SpotLight.tsx:1
- Orphaned file src/core/Points.tsx:1
- Orphaned file src/web/pivotControls/PlaneSlider.tsx:1
- Orphaned file src/web/pivotControls/AxisRotator.tsx:1
- Orphaned file src/materials/WireframeMaterial.tsx:1
- Orphaned file src/materials/MeshReflectorMaterial.tsx:1
- Orphaned file src/web/pivotControls/ScalingSphere.tsx:1
- Orphaned file src/web/pivotControls/AxisArrow.tsx:1
- Orphaned file src/core/Environment.tsx:1
- Orphaned file src/materials/MeshRefractionMaterial.tsx:1
- Orphaned file src/core/MotionPathControls.tsx:1
- Orphaned file src/core/Sparkles.tsx:1
- Orphaned file src/web/Select.tsx:1
- Duplicated predicate src/core/Stats.tsx:17
- Duplicated predicate src/web/pivotControls/AxisArrow.tsx:83
- Duplicated predicate src/web/pivotControls/AxisArrow.tsx:125
- Duplicated predicate src/core/Bounds.tsx:69
- Duplicated predicate src/core/ArcballControls.tsx:37
- Duplicated predicate src/core/OrthographicCamera.tsx:60
- Duplicated predicate src/core/MeshDistortMaterial.tsx:91
- Deprecated: glob REDACTED:7391
- Deprecated: glob REDACTED:7422
- Deprecated: glob REDACTED:7438
- Deprecated: inflight REDACTED:8057
- Deprecated: sourcemap-codec REDACTED:12102
- Deprecated: tar REDACTED:12595
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- redundant comment src/core/AccumulativeShadows.tsx:372
- redundant comment src/core/SpriteAnimator.tsx:251
- redundant comment src/core/useSpriteLoader.tsx:186
- redundant comment src/web/Facemesh.tsx:145
- redundant comment src/web/Facemesh.tsx:163
- Most significant orphaned file .storybook/public/draco-gltf/draco_decoder.js:1
- Most significant orphaned file .storybook/public/draco-gltf/draco_wasm_wrapper.js:1
- Most significant orphaned file src/core/Splat.tsx:1
- Outdated (npm): cross-env package.json:55
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:10
- Dependabot does not watch github-actions REDACTED:7
- Unused export 'CycleRaycast' src/web/CycleRaycast.tsx:13
- Unused export 'useFaceControls' src/web/FaceControls.tsx:307
- Unused export 'useSelect' src/web/Select.tsx:177
- Unused export 'View' src/web/View.tsx:274
- Not all async functions that make a request accept an AbortSignal
- Null assertions (`!`) override strict null checking
Minor — 13 finding(s)
- Outdated (npm): @babel/runtime
- Outdated (npm): @mediapipe/tasks-vision
- Outdated (npm): @monogrid/gainmap-js
- Outdated (npm): camera-controls
- Outdated (npm): detect-gpu
- Outdated (npm): hls.js
- Outdated (npm): stats-gl
- Outdated (npm): three-mesh-bvh
- Outdated (npm): three-stdlib
- Outdated (npm): troika-three-text
- Outdated (npm): use-sync-external-store
- Outdated (npm): zustand
- doc comments repeat the names src/core/AsciiRenderer.tsx:6
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-94391ea5d0134ae5b300cf950110d16b/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-94391ea5d0134ae5b300cf950110d16b/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 66 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | 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 111 file(s) — `.storybook/stories/AccumulativeShadows.stories.tsx`, `.storybook/stories/Adaptive.stories.tsx`, `.storybook/stories/ArcballControls.stories.tsx`, `.storybook/stories/BBAnchor.stories.tsx`, `.storybook/stories/Billboard.stories.tsx`, … (+106 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | 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. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | 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. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | 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. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | 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. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |