Public report of motiondivision/motion, published 7 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 7 November 2026, 17:57 UTC · Survey ID cd_feb4079249144854bb6a131203db3b98

motiondivision/motion

Measured 7 November 2026, 17:55 UTC, at code version 78f3ff5

Dependency hygiene is not measured: Npm pinning read, dependency currency not (registry.npmjs.org unreachable).

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 42out of 100 At risk Down 3 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 65,115 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Accessibility, 35

Findings by how serious they are

78 critical 528 serious 168 minor

10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
7 November 2026, 17:55 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

76of 76 dimensions measured by tools.
756of 774 findings point to an exact file and line, so you can open each one in the code. The other 18 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 65,115 lines of product code in 10 projects.
Chapters

Executive summary

motiondivision/motion is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has controls that only work with a mouse and pages that don't say their language. It scores 42 out of 100, which the At risk rating leaves unchanged.

Accessibility, at 35, is the weakest lens and counts most in the score. The best first step for the work it takes is making the two tests that check nothing check their results, worth about 3 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 4 points. Raising Accessibility to 70 would lift the score to about 48.

Twenty-five known security holes in the packages the code depends on can be used by attackers. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and seven controls can't be used without a mouse. Making the controls work with a keyboard, updating the vulnerable packages and pinning each tool to an exact version would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and the two passwords or keys in the code's history need replacing, with the old ones switched off. The 14 pages that don't say their language need their language set.

The product code is 65,115 lines, about €130,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 35 · counts for 46%Production Readiness 36 · counts for 25%Architecture 55 · counts for 14%Maturity 60 · counts for 8%Performance 60 · counts for 4%Code Health 64 · counts for 2%Security and Compliance 75 · counts for 1%

If Accessibility rose from 35 to 70, the lowest score rated Strong, the score would rise from 42 to about 48.

Code composition: what the lines of code are
Product code 42%Tests 58%
New since the last survey: 114 findings

These 114 critical or serious findings weren't in the previous survey, on 21 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · Group.ReorderGroupComponent (cyclomatic 47) packages/framer-motion/src/components/Reorder/Group.tsx
  • Cyclomatic Complexity · remix.motionMixin (cyclomatic 40) packages/framer-motion/src/remix.ts
  • Cyclomatic Complexity · remix.motionMixin.<returned closure> (cyclomatic 36) packages/framer-motion/src/remix.ts
  • Cyclomatic Complexity · remix-reorder.createReorder.Group (cyclomatic 36) packages/framer-motion/src/remix-reorder.ts
  • Cyclomatic Complexity · create.createAnimationsFromSequence::resolveSequence::resolveValueSequence (cyclomatic 32) packages/framer-motion/src/animation/sequence/create.ts
  • Cyclomatic Complexity · motion-value.animateMotionValue.<returned closure> (cyclomatic 24) packages/motion-dom/src/animation/interfaces/motion-value.ts
  • Cyclomatic Complexity · spring.springGenerator (cyclomatic 22) packages/motion-dom/src/animation/generators/spring.ts
  • Cyclomatic Complexity · Timeline.build (cyclomatic 20) packages/framer-motion/src/animation/timeline/index.ts
  • Cyclomatic Complexity · Item.ReorderItemComponent (cyclomatic 20) packages/framer-motion/src/components/Reorder/Item.tsx
  • Cyclomatic Complexity · remix.makeLatestValues (cyclomatic 20) packages/framer-motion/src/remix.ts
  • Cyclomatic Complexity · index.press::startPress (cyclomatic 18) packages/motion-dom/src/gestures/press/index.ts
  • Cyclomatic Complexity · size-scenarios.check (cyclomatic 17) dev/inc/size-scenarios.mjs
  • Cyclomatic Complexity · VisualElement.mount (cyclomatic 16) packages/motion-dom/src/render/VisualElement.ts
  • Cyclomatic Complexity · VisualElementDragControls.resolveConstraints (cyclomatic 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • Cyclomatic Complexity · VisualElementDragControls.startAnimation (cyclomatic 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • Cognitive Complexity · Group.ReorderGroupComponent (cognitive 49) packages/framer-motion/src/components/Reorder/Group.tsx
  • Cognitive Complexity · create.createAnimationsFromSequence::resolveSequence::resolveValueSequence (cognitive 47) packages/framer-motion/src/animation/sequence/create.ts
  • Cognitive Complexity · remix.motionMixin.<returned closure> (cognitive 43) packages/framer-motion/src/remix.ts
  • Cognitive Complexity · remix.motionMixin (cognitive 37) packages/framer-motion/src/remix.ts
  • Cognitive Complexity · remix-reorder.createReorder.Group (cognitive 37) packages/framer-motion/src/remix-reorder.ts
  • Cognitive Complexity · keyframes.keyframes (cognitive 27) packages/motion-dom/src/animation/generators/keyframes.ts
  • Cognitive Complexity · remix.makeLatestValues (cognitive 25) packages/framer-motion/src/remix.ts
  • Cognitive Complexity · create.createAnimationsFromSequence::resolveSequence (cognitive 23) packages/framer-motion/src/animation/sequence/create.ts
  • Cognitive Complexity · Item.ReorderItemComponent (cognitive 23) packages/framer-motion/src/components/Reorder/Item.tsx
  • Cognitive Complexity · spring.springGenerator (cognitive 23) packages/motion-dom/src/animation/generators/spring.ts
  • Cognitive Complexity · Timeline.build (cognitive 21) packages/framer-motion/src/animation/timeline/index.ts
  • Cognitive Complexity · motion-value.animateMotionValue.<returned closure> (cognitive 21) packages/motion-dom/src/animation/interfaces/motion-value.ts
  • Cognitive Complexity · stagger.stagger.<returned closure> (cognitive 21) packages/motion-dom/src/utils/stagger.ts
  • Cognitive Complexity · TransformAnimation.tween (cognitive 19) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Cognitive Complexity · Board.createBoard.drag (cognitive 17) packages/framer-motion/src/components/Reorder/Board.tsx
  • Cognitive Complexity · TransformAnimation.createGroup::getEasing (cognitive 17) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Cognitive Complexity · index.createScopedAnimate.scopedAnimate (cognitive 16) packages/framer-motion/src/animation/animate/index.ts
  • Cognitive Complexity · PopChild.PopChild (cognitive 16) packages/framer-motion/src/components/AnimatePresence/PopChild.tsx
  • Cognitive Complexity · index.press::startPress (cognitive 16) packages/motion-dom/src/gestures/press/index.ts
  • Cognitive Complexity · VisualElementDragControls.resolveConstraints (cognitive 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • God Classes · FunctionTooLong: remix-reorder.createReorder packages/framer-motion/src/remix-reorder.ts
  • God Classes · FunctionTooLong: Board.createBoard packages/framer-motion/src/components/Reorder/Board.tsx
  • God Classes · FunctionTooLong: remix-reorder.createReorder.Group packages/framer-motion/src/remix-reorder.ts
  • God Classes · FileTooLong: src/remix.ts packages/framer-motion/src/remix.ts
  • God Classes · FunctionTooLong: spring.springGenerator packages/motion-dom/src/animation/generators/spring.ts
  • God Classes · FunctionTooLong: index.createScopedAnimate packages/framer-motion/src/animation/animate/index.ts
  • God Classes · TooManyMethods: Timeline packages/framer-motion/src/animation/timeline/index.ts
  • Cohesion (LCOM4) · Low cohesion: TransformAnimation (LCOM4 6) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Test Quality · No assertions: Enter follows a nested link tests/react/reorder-nested-controls.spec.ts
  • Test Quality · No assertions: re-runs a callback scheduled with `true` after it already ran in the same step packages/motion-dom/src/frameloop/__tests__/index.test.ts
  • Test Quality · No assertions: runs a callback scheduled with `true` once, at the end of the step, if it hasn't run yet packages/motion-dom/src/frameloop/__tests__/index.test.ts
  • Test Quality · No assertions: doesn't re-run a callback that schedules itself with `true` while running packages/motion-dom/src/frameloop/__tests__/index.test.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/components/Reorder/Group.tsx packages/framer-motion/src/components/Reorder/Group.tsx
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/gestures/press/index.ts packages/motion-dom/src/gestures/press/index.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/animation/timeline/index.ts packages/framer-motion/src/animation/timeline/index.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/components/Reorder/Item.tsx packages/framer-motion/src/components/Reorder/Item.tsx
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/remix.ts packages/framer-motion/src/remix.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/animation/sequence/create.ts packages/framer-motion/src/animation/sequence/create.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/render/VisualElement.ts packages/motion-dom/src/render/VisualElement.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/remix-reorder.ts packages/framer-motion/src/remix-reorder.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/components/Reorder/Board.tsx packages/framer-motion/src/components/Reorder/Board.tsx
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/value/use-transform.ts packages/framer-motion/src/value/use-transform.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/projection/styles/transform.ts packages/motion-dom/src/projection/styles/transform.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/projection/geometry/delta-apply.ts packages/motion-dom/src/projection/geometry/delta-apply.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/projection/animation/mix-values.ts packages/motion-dom/src/projection/animation/mix-values.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/framer-motion/src/motion/features/animation/exit.ts packages/framer-motion/src/motion/features/animation/exit.ts
  • Static Analysis (SAST) · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Code Duplication · Duplicated block (32 lines × 2 locations) packages/framer-motion/rollup.config.mjs
  • Code Duplication · Duplicated block with local edits (29 matched lines × 2 locations) packages/framer-motion/src/components/Reorder/Group.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) dev/html/src/three-animate.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/motion-dom/src/projection/geometry/delta-apply.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) dev/html/src/three-animate.js
  • Import Boundaries · Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 53, cognitive 56) packages/motion-dom/src/render/utils/animation-state.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 35, cognitive 49) packages/framer-motion/src/remix.ts
  • Cyclomatic Complexity · Complex function retime (cyclomatic 34, cognitive 46) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Cyclomatic Complexity · Complex function onKeyDown (cyclomatic 28, cognitive 30) packages/framer-motion/src/components/Reorder/Group.tsx
  • Cyclomatic Complexity · Complex function animate (cyclomatic 20, cognitive 36) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Cyclomatic Complexity · Complex function makeLatestValues (cyclomatic 20, cognitive 29) packages/framer-motion/src/remix.ts
  • Large Files · packages/motion-dom/src/projection/node/create-projection-node.ts: 2260 lines of code packages/motion-dom/src/projection/node/create-projection-node.ts
  • Large Files · packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts: 1375 lines of code packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts
  • Large Files · packages/framer-motion/src/remix.ts: 1226 lines of code packages/framer-motion/src/remix.ts
  • Large Files · packages/motion-dom/src/node/types.ts: 1050 lines of code packages/motion-dom/src/node/types.ts
  • Large Files · packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts: 832 lines of code packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • Large Files · packages/motion-dom/src/render/VisualElement.ts: 819 lines of code packages/motion-dom/src/render/VisualElement.ts
  • Large Files · packages/motion-dom/src/animation/types.ts: 724 lines of code packages/motion-dom/src/animation/types.ts
  • Large Files · packages/framer-motion/src/animation/timeline/index.ts: 683 lines of code packages/framer-motion/src/animation/timeline/index.ts
  • Large Files · packages/motion-dom/src/value/index.ts: 497 lines of code packages/motion-dom/src/value/index.ts
  • Large Files · dev/inc/size-scenarios.mjs: 480 lines of code dev/inc/size-scenarios.mjs
  • Large Files · packages/framer-motion/src/animation/sequence/create.ts: 479 lines of code packages/framer-motion/src/animation/sequence/create.ts
  • Large Files · packages/motion-dom/src/animation/generators/spring.ts: 470 lines of code packages/motion-dom/src/animation/generators/spring.ts
  • Large Files · packages/framer-motion/src/remix-reorder.ts: 467 lines of code packages/framer-motion/src/remix-reorder.ts
  • Large Files · packages/framer-motion/src/components/Reorder/Board.tsx: 435 lines of code packages/framer-motion/src/components/Reorder/Board.tsx
  • Large Files · packages/motion-dom/src/render/utils/animation-state.ts: 403 lines of code packages/motion-dom/src/render/utils/animation-state.ts
  • Test Coverage · No test reaches this file packages/framer-motion/src/remix.ts
  • Test Coverage · No test reaches this file packages/framer-motion/src/remix-reorder.ts
  • Test Coverage · No test reaches this file dev/html/src/three-xr.js
  • Test Coverage · No test reaches this file dev/remix/src/hydrate.tsx
  • Test Coverage · No test reaches this file dev/remix/src/load-test.ts

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 821 findings

These 821 critical or serious findings were in the previous survey, on 21 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · create.createAnimationsFromSequence::resolveValueSequence (cyclomatic 30) packages/framer-motion/src/animation/sequence/create.ts
  • Cyclomatic Complexity · motion-value.animateMotionValue (cyclomatic 24) packages/motion-dom/src/animation/interfaces/motion-value.ts
  • Cyclomatic Complexity · spring.spring (cyclomatic 21) packages/motion-dom/src/animation/generators/spring.ts
  • Cyclomatic Complexity · arc.createArcPath (cyclomatic 17) packages/motion-dom/src/animation/utils/arc.ts
  • Cyclomatic Complexity · VisualElementDragControls.addListeners (cyclomatic 17) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • Cyclomatic Complexity · ProjectionNode.willUpdate (cyclomatic 16) packages/motion-dom/src/projection/node/create-projection-node.ts
  • Cognitive Complexity · create.createAnimationsFromSequence::resolveValueSequence (cognitive 46) packages/framer-motion/src/animation/sequence/create.ts
  • Cognitive Complexity · spring.spring (cognitive 22) packages/motion-dom/src/animation/generators/spring.ts
  • Cognitive Complexity · motion-value.animateMotionValue (cognitive 21) packages/motion-dom/src/animation/interfaces/motion-value.ts
  • Cognitive Complexity · stagger.stagger (cognitive 21) packages/motion-dom/src/utils/stagger.ts
  • Cognitive Complexity · animate-elements.animateElements (cognitive 20) packages/framer-motion/src/animation/animators/waapi/animate-elements.ts
  • Cognitive Complexity · arc.createArcPath (cognitive 19) packages/motion-dom/src/animation/utils/arc.ts
  • Cognitive Complexity · build-transform.buildTransform (cognitive 19) packages/motion-dom/src/render/html/utils/build-transform.ts
  • Cognitive Complexity · track.scrollInfo (cognitive 18) packages/framer-motion/src/render/dom/scroll/track.ts
  • Cognitive Complexity · create.createAnimationsFromSequence (cognitive 17) packages/framer-motion/src/animation/sequence/create.ts
  • Cognitive Complexity · VisualElementDragControls.addListeners (cognitive 17) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts
  • God Classes · FunctionTooLong: spring.spring packages/motion-dom/src/animation/generators/spring.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/animate-view.ts packages/framer-motion/src/animate-view.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/client.ts packages/framer-motion/src/client.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/debug.ts packages/framer-motion/src/debug.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/dom-mini.ts packages/framer-motion/src/dom-mini.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/m.ts packages/framer-motion/src/m.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/mini.ts packages/framer-motion/src/mini.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/animation/animators/waapi/animate-sequence.ts packages/framer-motion/src/animation/animators/waapi/animate-sequence.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/animation/hooks/use-animate-style.ts packages/framer-motion/src/animation/hooks/use-animate-style.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/animation/optimized-appear/handoff.ts packages/framer-motion/src/animation/optimized-appear/handoff.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/animation/optimized-appear/start.ts packages/framer-motion/src/animation/optimized-appear/start.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/components/AnimateView/index.tsx packages/framer-motion/src/components/AnimateView/index.tsx
  • Code Coverage · Low coverage: packages/framer-motion/src/components/AnimateView/shared-props.ts packages/framer-motion/src/components/AnimateView/shared-props.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/components/AnimateView/hooks/use-reset-view-transitions.ts packages/framer-motion/src/components/AnimateView/hooks/use-reset-view-transitions.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/motion/features/viewport/index.ts packages/framer-motion/src/motion/features/viewport/index.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/motion/features/viewport/observers.ts packages/framer-motion/src/motion/features/viewport/observers.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/projection/use-reset-projection.ts packages/framer-motion/src/projection/use-reset-projection.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/m/create.ts packages/framer-motion/src/render/components/m/create.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/m/elements.ts packages/framer-motion/src/render/components/m/elements.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/m/index.ts packages/framer-motion/src/render/components/m/index.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/m/namespace.ts packages/framer-motion/src/render/components/m/namespace.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/m/size.ts packages/framer-motion/src/render/components/m/size.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/components/motion/size.ts packages/framer-motion/src/render/components/motion/size.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/dom/use-motion-value-child.ts packages/framer-motion/src/render/dom/use-motion-value-child.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/dom/scroll/offsets/inset.ts packages/framer-motion/src/render/dom/scroll/offsets/inset.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/svg/supported-elements.ts packages/framer-motion/src/render/svg/supported-elements.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/render/utils/is-draggable.ts packages/framer-motion/src/render/utils/is-draggable.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/utils/transform-rotated-parent.ts packages/framer-motion/src/utils/transform-rotated-parent.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/utils/transform-viewbox-point.ts packages/framer-motion/src/utils/transform-viewbox-point.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/utils/use-page-in-view.ts packages/framer-motion/src/utils/use-page-in-view.ts
  • Code Coverage · Low coverage: packages/framer-motion/src/value/use-inverted-scale.ts packages/framer-motion/src/value/use-inverted-scale.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/interfaces/visual-element-variant.ts packages/motion-dom/src/animation/interfaces/visual-element-variant.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/interfaces/visual-element.ts packages/motion-dom/src/animation/interfaces/visual-element.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/keyframes/utils/apply-px-defaults.ts packages/motion-dom/src/animation/keyframes/utils/apply-px-defaults.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/optimized-appear/types.ts packages/motion-dom/src/animation/optimized-appear/types.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/utils/active-animations.ts packages/motion-dom/src/animation/utils/active-animations.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/utils/css-variables-conversion.ts packages/motion-dom/src/animation/utils/css-variables-conversion.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/animation/waapi/supports/partial-keyframes.ts packages/motion-dom/src/animation/waapi/supports/partial-keyframes.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/gestures/hover.ts packages/motion-dom/src/gestures/hover.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/projection/node/create-projection-node.ts packages/motion-dom/src/projection/node/create-projection-node.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/projection/node/group.ts packages/motion-dom/src/projection/node/group.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/Feature.ts packages/motion-dom/src/render/Feature.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/object/ObjectVisualElement.ts packages/motion-dom/src/render/object/ObjectVisualElement.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/svg/utils/build-attrs.ts packages/motion-dom/src/render/svg/utils/build-attrs.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/svg/utils/path.ts packages/motion-dom/src/render/svg/utils/path.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/utils/animation-state.ts packages/motion-dom/src/render/utils/animation-state.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/utils/get-variant-context.ts packages/motion-dom/src/render/utils/get-variant-context.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/utils/motion-values.ts packages/motion-dom/src/render/utils/motion-values.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/utils/resolve-variants.ts packages/motion-dom/src/render/utils/resolve-variants.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/render/utils/setters.ts packages/motion-dom/src/render/utils/setters.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/resize/handle-window.ts packages/motion-dom/src/resize/handle-window.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/scope/media.ts packages/motion-dom/src/scope/media.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/view/start.ts packages/motion-dom/src/view/start.ts
  • Code Coverage · Low coverage: packages/motion-dom/src/view/utils/choose-layer-type.ts packages/motion-dom/src/view/utils/choose-layer-type.ts
  • Code Coverage · Low coverage: REDACTED REDACTED
  • Code Coverage · Low coverage: packages/motion-dom/src/view/utils/get-view-animations.ts packages/motion-dom/src/view/utils/get-view-animations.ts
  • Churn × Complexity Hotspots · Hotspot: packages/motion-dom/src/animation/interfaces/motion-value.ts packages/motion-dom/src/animation/interfaces/motion-value.ts
  • Churn × Complexity Hotspots · Hotspot: dev/react/src/tests/start-transition-helpers.ts dev/react/src/tests/start-transition-helpers.ts
  • Churn × Complexity Hotspots · Hotspot: packages/framer-motion/src/render/dom/scroll/track.ts packages/framer-motion/src/render/dom/scroll/track.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/motion-dom/src/render/svg/utils/build-attrs.ts packages/motion-dom/src/render/svg/utils/build-attrs.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/motion-dom/src/gestures/press/index.ts packages/motion-dom/src/gestures/press/index.ts
  • Churn × Complexity Hotspots · Repeated repair: dev/react/src/tests/waapi-svg-zero-duration.tsx dev/react/src/tests/waapi-svg-zero-duration.tsx
  • Churn × Complexity Hotspots · Repeated repair: packages/framer-motion/cypress/integration/waapi-svg-zero-duration.ts packages/framer-motion/cypress/integration/waapi-svg-zero-duration.ts
  • Boundary Type-Coupling · Cross-context type Transition (motion-dom → framer-motion) packages/framer-motion/src/components/AnimateView/types.ts
  • Boundary Type-Coupling · Cross-context type Transition (motion-dom → framer-motion) packages/framer-motion/src/animation/sequence/types.ts
  • Boundary Type-Coupling · Cross-context type AnyResolvedKeyframe (motion-dom → framer-motion) packages/framer-motion/src/animation/sequence/types.ts
  • Boundary Type-Coupling · Cross-context type Easing (motion-utils → framer-motion) packages/framer-motion/src/animation/sequence/types.ts
  • Boundary Type-Coupling · Cross-context type UnresolvedValueKeyframe (motion-dom → framer-motion) packages/framer-motion/src/animation/sequence/utils/edit.ts
  • Boundary Type-Coupling · Cross-context type Easing (motion-utils → framer-motion) packages/framer-motion/src/animation/sequence/utils/edit.ts
  • Boundary Type-Coupling · Cross-context type ElementOrSelector (motion-dom → framer-motion) packages/framer-motion/src/animation/animate/subject.ts
  • Boundary Type-Coupling · Cross-context type UnresolvedValueKeyframe (motion-dom → framer-motion) packages/framer-motion/src/animation/animate/subject.ts
  • Boundary Type-Coupling · Cross-context type ElementOrSelector (motion-dom → framer-motion) packages/framer-motion/src/animation/animators/waapi/animate-elements.ts
  • Boundary Type-Coupling · Cross-context type Transition (motion-dom → framer-motion) packages/framer-motion/src/context/MotionConfigContext.tsx
  • Boundary Type-Coupling · Cross-context type AnyResolvedKeyframe (motion-dom → framer-motion) packages/framer-motion/src/render/html/use-props.ts
  • Boundary Type-Coupling · Cross-context type AnyResolvedKeyframe (motion-dom → framer-motion) packages/framer-motion/src/value/use-transform.ts
  • Boundary Type-Coupling · Cross-context type ElementOrSelector (motion-dom → framer-motion) packages/framer-motion/src/render/dom/viewport/index.ts
  • Boundary Type-Coupling · Cross-context type AnyResolvedKeyframe (motion-dom → framer-motion) packages/framer-motion/src/value/use-follow-value.ts
  • Boundary Type-Coupling · Cross-context type AnyResolvedKeyframe (motion-dom → framer-motion) packages/framer-motion/src/value/use-follow-value.ts
  • Boundary Type-Coupling · Cross-context type Easing (motion-utils → motion-dom) packages/motion-dom/src/animation/waapi/easing/is-supported.ts
  • Boundary Type-Coupling · Cross-context type Easing (motion-utils → motion-dom) packages/motion-dom/src/animation/waapi/easing/map-easing.ts
  • Boundary Type-Coupling · Cross-context type Easing (motion-utils → motion-dom) packages/motion-dom/src/animation/types.ts
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €130,000 · Estimate
Cost to rebuild€45,000 to €220,000, for 744 to 2,359 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 65,115 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with GroupAnimation.test.ts, JSAnimation.test.ts.
Raises the score by about 3 points · Low effort · Test Quality
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 4 points · Medium effort · Keyboard semantics
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 3 points · Medium effort · Page structure

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Accessibility, at 35 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 2 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 2 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 12% on every change. The history of the code shows how much it changes: about 91,796 lines over the last 90 days, which is about 372,284 lines a year. At that pace, the extra work comes to an estimated 50.2 to 301.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch config config framer-motion framer-motion motion-dom motion-dom framer-motion->motion-dom motion-utils motion-utils framer-motion->motion-utils html-env html-env html-env->framer-motion motion motion html-env->motion html-env->motion-dom motion->framer-motion motion-dom->motion-utils next-env next-env next-env->motion react-19-env react-19-env react-19-env->motion react-env react-env react-env->framer-motion react-env->motion remix-env remix-env remix-env->motion

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

255 modules, with 354 dependencies between them. 2 loops run through 14 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 215 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 framer-motion.src.components.Reorder.types2 framer-motion.src.motion.types3 framer-motion.src.render.dom.scroll.types4 motion-dom.src.animation.keyframes.types5 motion-dom.src.utils.resolve-elements6 motion-utils.src.types.geometry7 motion-dom.src.animation.NativeAnimation8 motion-dom.src.gestures.drag.types9 motion-dom.src.value10 framer-motion.src.animation.animators.waapi.animate-elements11 framer-motion.src.motion.utils.use-visual-state12 motion-dom.src.render.html.types13 framer-motion.src.render.types14 motion-dom.src.node.types15 motion-dom.src.render.utils.animation-state16 motion-dom.src.render.VisualElement17 framer-motion.src.render.dom18 motion-dom.src.animation.interfaces19 motion-dom.src.animation.types20 motion-dom.src.render.Feature21 motion-dom.src.render.dom.DOMVisualElement22 motion-dom.src.render.svg.utils23 framer-motion.src.animation.sequence.types24 framer-motion.src.remix25 framer-motion.src.value26 motion-dom.src.animation.GroupAnimation27 motion-dom.src.animation.JSAnimation28 motion-dom.src.animation.animate29 motion-dom.src.gestures.drag.VisualElementDragControls30 motion-dom.src.render.html.HTMLVisualElement31 motion-dom.src.render.html.utils32 motion-dom.src.render.svg.SVGVisualElement33 motion-dom.src.render.types34 motion-dom.src.render.utils35 framer-motion.src36 framer-motion.src.animation.timeline37 motion-dom.src.projection.node.types38 motion-dom.src.gestures.drag39 motion-dom.src.projection.node40 motion-dom.src.projection.node.create-projection-node
1 framer-motion.src.components.Reorder.types
2 framer-motion.src.motion.types
3 framer-motion.src.render.dom.scroll.types
4 motion-dom.src.animation.keyframes.types
5 motion-dom.src.utils.resolve-elements
6 motion-utils.src.types.geometry
7 motion-dom.src.animation.NativeAnimation1
8 motion-dom.src.gestures.drag.types21
9 motion-dom.src.value1
10 framer-motion.src.animation.animators.waapi.animate-elements1
11 framer-motion.src.motion.utils.use-visual-state1
12 motion-dom.src.render.html.types1
13 framer-motion.src.render.types111
14 motion-dom.src.node.types1212
15 motion-dom.src.render.utils.animation-state1
16 motion-dom.src.render.VisualElement121111
17 framer-motion.src.render.dom111111
18 motion-dom.src.animation.interfaces11113
19 motion-dom.src.animation.types1121
20 motion-dom.src.render.Feature1
21 motion-dom.src.render.dom.DOMVisualElement111
22 motion-dom.src.render.svg.utils1211
23 framer-motion.src.animation.sequence.types1
24 framer-motion.src.remix21
25 framer-motion.src.value41
26 motion-dom.src.animation.GroupAnimation2
27 motion-dom.src.animation.JSAnimation13
28 motion-dom.src.animation.animate111
29 motion-dom.src.gestures.drag.VisualElementDragControls111
30 motion-dom.src.render.html.HTMLVisualElement11111
31 motion-dom.src.render.html.utils122111
32 motion-dom.src.render.svg.SVGVisualElement1111
33 motion-dom.src.render.types1111
34 motion-dom.src.render.utils33114
35 framer-motion.src214
36 framer-motion.src.animation.timeline1123
37 motion-dom.src.projection.node.types122141
38 motion-dom.src.gestures.drag111121
39 motion-dom.src.projection.node2113
40 motion-dom.src.projection.node.create-projection-node11211216
Uses a module listed above itPart of a loopThe module itself
1 framer-motion.src.components.Reorder.types2 framer-motion.src.motion.types3 framer-motion.src.render.dom.scroll.types4 motion-dom.src.animation.keyframes.types5 motion-dom.src.utils.resolve-elements6 motion-utils.src.types.geometry7 motion-dom.src.animation.NativeAnimation8 motion-dom.src.gestures.drag.types9 motion-dom.src.value10 framer-motion.src.animation.animators.waapi.animate-elements11 framer-motion.src.motion.utils.use-visual-state12 motion-dom.src.render.html.types13 framer-motion.src.render.types14 motion-dom.src.node.types15 motion-dom.src.render.utils.animation-state16 motion-dom.src.render.VisualElement17 framer-motion.src.render.dom18 motion-dom.src.animation.interfaces19 motion-dom.src.animation.types20 motion-dom.src.render.Feature21 motion-dom.src.render.dom.DOMVisualElement22 motion-dom.src.render.svg.utils23 framer-motion.src.animation.sequence.types24 framer-motion.src.remix25 framer-motion.src.value26 motion-dom.src.animation.GroupAnimation27 motion-dom.src.animation.JSAnimation28 motion-dom.src.animation.animate29 motion-dom.src.gestures.drag.VisualElementDragControls30 motion-dom.src.render.html.HTMLVisualElement31 motion-dom.src.render.html.utils32 motion-dom.src.render.svg.SVGVisualElement33 motion-dom.src.render.types34 motion-dom.src.render.utils35 framer-motion.src36 framer-motion.src.animation.timeline37 motion-dom.src.projection.node.types38 motion-dom.src.gestures.drag39 motion-dom.src.projection.node40 motion-dom.src.projection.node.create-projection-nodeframer-motion.src.components.Reorder.types1framer-motion.src.motion.types2framer-motion.src.render.dom.scroll.types3motion-dom.src.animation.keyframes.types4motion-dom.src.utils.resolve-elements5motion-utils.src.types.geometry6motion-dom.src.animation.NativeAnimation7motion-dom.src.gestures.drag.types8motion-dom.src.value9framer-motion.src.animation.animators.waapi.animate-elements10framer-motion.src.motion.utils.use-visual-state11motion-dom.src.render.html.types12framer-motion.src.render.types13motion-dom.src.node.types14motion-dom.src.render.utils.animation-state15motion-dom.src.render.VisualElement16framer-motion.src.render.dom17motion-dom.src.animation.interfaces18motion-dom.src.animation.types19motion-dom.src.render.Feature20motion-dom.src.render.dom.DOMVisualElement21motion-dom.src.render.svg.utils22framer-motion.src.animation.sequence.types23framer-motion.src.remix24framer-motion.src.value25motion-dom.src.animation.GroupAnimation26motion-dom.src.animation.JSAnimation27motion-dom.src.animation.animate28motion-dom.src.gestures.drag.VisualElementDragControls29motion-dom.src.render.html.HTMLVisualElement30motion-dom.src.render.html.utils31motion-dom.src.render.svg.SVGVisualElement32motion-dom.src.render.types33motion-dom.src.render.utils34framer-motion.src35framer-motion.src.animation.timeline36motion-dom.src.projection.node.types37motion-dom.src.gestures.drag38motion-dom.src.projection.node39motion-dom.src.projection.node.create-projection-node4012111111111212112111111111111113112111111211121412131111111111112211111111111331142141123122141111121211311211216+215 more modules (most-connected shown)

At a glance — Code Health · 64% · Adequate · gated by D2 ·

At a glance — Architecture · 55% · Adequate · gated by R11 ·

At a glance — Maturity · 60% · Adequate · gated by M2 ·

At a glance — Readiness · 36% · Weak · gated by R8, P2, P3 ·

At a glance — Security · 75% · Adequate · gated by D29 ·

At a glance — Accessibility · 35% · Weak · gated by AC1, AC3, AC4 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures40High / Critical
A05:2025 — Injection13High / Critical
A07:2025 — Authentication Failures3High / Critical
A02:2025 — Security Misconfiguration2Medium

Roadmap

Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Adopt pino (or winston) and log at meaningful points in the services you run.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with GroupAnimation.test.ts, JSAnimation.test.ts.+2.5 ptsLowTest Quality
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+3.9 ptsMediumKeyboard semantics
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+3.5 ptsMediumPage structure
Adopt pino (or winston) and log at meaningful points in the services you run.+3.4 ptsMediumObservability
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.+3.4 ptsMediumSecurity & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.4 ptsMediumDependency Hygiene
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.+2.2 ptsMediumText alternatives
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.+2.1 ptsMediumA11y enforcement

File quality

Per-file score 0–10 — a quality signature. Of 110 files carrying findings, judged against the Production bar: 1% slop · 54% mixed · 45% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts5.1MixedTest Quality: No assertions (empty test): .then() can be chained
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts5.5MixedCyclomatic Complexity: TransformAnimation.createGroup::retime (cyclomatic 34)
packages/motion-dom/src/projection/node/create-projection-node.ts6.0MixedExplicit Debt: TodoComment
packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts6.0MixedExplicit Debt: TodoComment
packages/motion-dom/src/animation/generators/keyframes.ts6.0MixedExplicit Debt: TodoComment
packages/motion-dom/src/animation/JSAnimation.ts6.0MixedExplicit Debt: TodoComment
packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx6.0MixedExplicit Debt: TodoComment
packages/framer-motion/cypress/integration/drag.ts6.9MixedExplicit Debt: TodoComment
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
tests/view/view-targets.spec.ts7.0MixedTest Quality: Skipped test: (unnamed test)
packages/motion-dom/src/frameloop/__tests__/index.test.ts7.0MixedTest Quality: No assertions: fires callbacks in the correct order
packages/framer-motion/src/animation/animate/__tests__/animate.test.tsx7.0MixedTest Quality: No assertions: Is typed correctly
dev/next/app/arcs/page.tsx7.0MixedChange Coupling: Boundary-crossing change coupling: page.tsx ↔ create-projection-node.ts
packages/framer-motion/src/remix.ts7.0MixedCyclomatic Complexity: remix.motionMixin (cyclomatic 40)
packages/motion-dom/src/render/utils/animation-state.ts7.2MixedCyclomatic Complexity: animation-state.createAnimationState.animateChanges (cyclomatic 83)
packages/framer-motion/src/remix-reorder.ts7.2MixedCyclomatic Complexity: remix-reorder.createReorder.Group (cyclomatic 36)
dev/inc/size-scenarios.mjs7.2MixedCyclomatic Complexity: main (cyclomatic 21)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 78

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 528

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 168

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 10

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 76 dimensions across the health lenses
D1D2D3D5D6D9D10D13D15D17D19D21D23D24D26D28D29D30D31D34D35D43D44AC1AC2AC3AC4AC6AC7AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 756 of 774 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1b727-0ddd-7b9b-b67d-53c130bf06ec.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — 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 dependency install for the repository root could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • 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 reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • 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 reliability for the jest suite in the repository root was NOT MEASURED: the dependency install for the repository root could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • 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 reliability for the jest suite in packages/framer-motion/ was NOT MEASURED: the dependency install for packages/framer-motion/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • 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 reliability for the jest suite in packages/motion/ was NOT MEASURED: the dependency install for packages/motion/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • 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 reliability for the jest suite in packages/motion-dom/ was NOT MEASURED: the dependency install for packages/motion-dom/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • 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 reliability for the jest suite in packages/motion-utils/ was NOT MEASURED: the dependency install for packages/motion-utils/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 29 production npm declaration(s) across 10 package.json (10 of them the product) were read for PINNING discipline (2 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, which could not be reached on this run, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (142 contributor(s) across 8982 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 141 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 (packages/motion-utils/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.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D27 Navigability — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/framer-motion/rollup.config.mjs`, `packages/framer-motion/src/debug.ts`, `packages/framer-motion/src/index.ts`, `packages/motion-dom/rollup.config.mjs`, `packages/motion-dom/src/animation/NativeAnimation.ts`, … (+6 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.
  • AC3 Page structure — 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. 478 further occurrence(s) are not listed individually; the score already reflects all 518.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> motion-one@0.0.0 dev / > turbo run dev / sh: 1: turbo: not found" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> motion-one@0.0.0 dev / > turbo run dev / sh: 1: turbo: not found" No runtime evidence was gathered.
  • 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
  • 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.
  • R11 Import Boundaries — 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. 225 further occurrence(s) are not listed individually; the score already reflects all 265.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • 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. 553 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • 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.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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

D1 · Cyclomatic Complexity4.4 / 10Weak✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.4 / 10 · rule-coverage 100% · ceiling Prevented

47 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was create-projection-node.createProjectionNode at 293. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being use-transform.useTransform at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/framer-motion/src/value/use-transform.ts (use-transform.useTransform at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

TransformAnimation.createGroup::retime (cyclomatic 34) · ×2packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277
create-projection-node.createProjectionNode (cyclomatic 293)packages/motion-dom/src/projection/node/create-projection-node.ts:173
start.startViewAnimation (cyclomatic 91)packages/motion-dom/src/view/start.ts:64
animation-state.createAnimationState.animateChanges (cyclomatic 83)packages/motion-dom/src/render/utils/animation-state.ts:82
Group.ReorderGroupComponent (cyclomatic 47)packages/framer-motion/src/components/Reorder/Group.tsx:90

+ 39 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with create-projection-node.createProjectionNode (cyclomatic 293). — Refactoring it lifts Cyclomatic Complexity from 4.4 to about 5.5/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity3.5 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 3.5 / 10 · rule-coverage 100% · ceiling Prevented

60 method(s) exceeded the cognitive complexity threshold of 15; the worst was create-projection-node.createProjectionNode at 270.

TransformAnimation.createGroup::retime (cognitive 44) · ×4packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277
create.createAnimationsFromSequence::resolveSequence::resolveValueSequence (cognitive 47) · ×2packages/framer-motion/src/animation/sequence/create.ts:127
create-projection-node.createProjectionNode (cognitive 270)packages/motion-dom/src/projection/node/create-projection-node.ts:173
start.startViewAnimation (cognitive 146)packages/motion-dom/src/view/start.ts:64
animation-state.createAnimationState.animateChanges (cognitive 88)packages/motion-dom/src/render/utils/animation-state.ts:82

+ 49 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with create-projection-node.createProjectionNode (cognitive 270), start.startViewAnimation (cognitive 146), animation-state.createAnimationState.animateChanges (cognitive 88). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 3.5 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes9.0 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Prevented

19 god class(es) detected.

FunctionTooLong: create-projection-node.createProjectionNode · ×13packages/motion-dom/src/projection/node/create-projection-node.ts:173
FileTooLong: node/create-projection-node.ts · ×3packages/motion-dom/src/projection/node/create-projection-node.ts
TooManyMethods: ProjectionNode · ×3packages/motion-dom/src/projection/node/create-projection-node.ts:191

What to do

  1. Resolve the 13 FunctionTooLong finding(s) in God Classes — start with remix-reorder.ts (2), animation-state.ts (2), create-projection-node.ts. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 3 FileTooLong finding(s) in God Classes — start with create-projection-node.ts, TransformAnimation.ts, remix.ts. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 TooManyMethods finding(s) in God Classes — start with create-projection-node.ts, VisualElement.ts, index.ts. — One of this dimension's main actionable groups (3 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling8.4 / 10Strong✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Prevented

10 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 8 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: motion-utils · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Verified

1 of 33 classes have LCOM4 above 3.

Low cohesion: TransformAnimation (LCOM4 6)packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:319

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with TransformAnimation.ts. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2791 test methods: 2791 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 2791 `it`/`test` case(s) across 355 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.3 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Prevented

53 skipped, 59 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2791 tests.

No assertions (empty test): .then() returns Promise · ×2packages/motion-dom/src/animation/__tests__/GroupAnimation.test.ts:103
No assertions: Enter follows a nested link · ×57tests/react/reorder-nested-controls.spec.ts:64
Skipped test: (unnamed test) · ×53tests/view/view-targets.spec.ts:69
Mock-dominated test: fires lifecycle callbacks · ×8packages/motion-dom/src/gestures/drag/__tests__/drag.test.ts:98

What to do

  1. Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with GroupAnimation.test.ts, JSAnimation.test.ts. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 57 No assertions finding(s) in Test Quality — start with animate.test.tsx (13), index.test.ts (11), JSAnimation.test.ts (5). — One of this dimension's main actionable groups (57 warning-level).
  3. Resolve the 53 Skipped test finding(s) in Test Quality — start with view-targets.spec.ts (32), index.test.tsx (4), scroll-view-timeline-parity.spec.ts (2). — One of this dimension's main actionable groups (53 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots8.5 / 10Strong✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/motion-dom/src/projection/node/create-projection-node.ts (38×293=11134); packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts (41×157=6437); packages/motion-dom/src/render/utils/animation-state.ts (15×83=1245) Repeated repair below the complexity floor: packages/framer-motion/src/motion/features/animation/exit.ts (3 of 4 changes were fixes)

Hotspot: packages/motion-dom/src/projection/node/create-projection-node.ts · ×34packages/motion-dom/src/projection/node/create-projection-node.ts:173
Repeated repair: packages/framer-motion/src/motion/features/animation/exit.tspackages/framer-motion/src/motion/features/animation/exit.ts:13

What to do

  1. Resolve the 34 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.ts (3), create-projection-node.ts, TransformAnimation.ts. — One of this dimension's main actionable groups (34 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with exit.ts. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.9 / 10Stronggated by 26 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

26 deducted task-comment markers across 49253 LoC (0.1/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.

TodoComment · ×26packages/motion-dom/src/utils/resolve-elements.ts:17

What to do

  1. Resolve the 26 TodoComment finding(s) in Explicit Debt — start with create-projection-node.ts (5), types.ts (3), drag.ts (3). — One of this dimension's main actionable groups (26 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 10 document(s) read across 11 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency5.5 / 10Adequate✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 5.5 / 10 · rule-coverage 100% · ceiling Verified

1 naming inconsistencies among 22 declarations measured against a convention their peers follow.

`createSvgRenderState` spells `Svg` where 21 names in the project spell it `SVG`packages/framer-motion/src/render/svg/utils/create-render-state.ts:4

What to do

  1. Resolve the 1 `createSvgRenderState` spells `Svg` where 21 names in the project spell… finding(s) in Naming Consistency — start with create-render-state.ts. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

25 domain type(s) cross context boundaries across 9 contexts; they are measured and withheld (not published, not scored). Contexts: framer-motion, html, motion, motion-dom, motion-utils, next, react, react-19, remix.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.9 9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 97% · ceiling Documented

2 of 1581 judged comments only repeat the code they sit on (0.1 %). 52 comment(s) in another language or script were not judged.

redundant comment · ×2packages/motion-dom/src/projection/node/create-projection-node.ts:686
doc comments repeat the names · ×3packages/framer-motion/src/animation/animate/index.ts:83

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion4.1 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 4.1 / 10 · rule-coverage 100% · ceiling Documented

3 of 10 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)1.9 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 1.9 / 10 · rule-coverage 100% · ceiling Documented

13 finding(s): 0 critical, 11 high, 2 medium, 0 low. 2 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 11 file(s) — `packages/framer-motion/rollup.config.mjs` (line 10, line 11), `packages/framer-motion/src/debug.ts` (line 1), `packages/framer-motion/src/index.ts` (line 4), `packages/motion-dom/rollup.config.mjs` (line 7, line 8), `packages/motion-dom/src/animation/NativeAnimation.ts` (line 286), … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

40 finding(s): 6 critical, 19 high, 13 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 18 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (18). — One of this dimension's main actionable groups (18 issue-level).
  2. Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
  3. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 0 high, 0 medium, 2 low.

REDACTED

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 136 of the 560 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: page.tsx↔create-projection-node.ts 69%; page.tsx↔types.ts 54%

Boundary-crossing change coupling: page.tsx ↔ create-projection-node.ts · ×2dev/next/app/arcs/page.tsx:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with page.tsx (2). — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives3.9 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×6) — dev/html/three-animate.html:22, dev/html/three-effects.html:24, dev/html/three-tsl.html:25, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure1.5 / 10Critical✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — dev/html/index.html:2
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×14) — dev/html/public/animate-layout/app-store-a-b-a.html:1, dev/html/public/animate-layout/app-store-layout.html:1, dev/html/public/animate-layout/basic-position-change.html:1, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×12) — dev/html/public/animate-layout/app-store-a-b-a.html:1, dev/html/public/animate-layout/basic-position-change.html:1, dev/html/public/animate-layout/data-layout-true.html:1, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×9) — dev/html/public/animate-layout/app-store-a-b-a.html:1, dev/html/public/animate-layout/app-store-layout.html:1, dev/html/public/animate-layout/modal-open-after-animate.html:1, …
  • 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="box">, so there is no content here to wrap — render the <main> from the component mounted into it. (×4) — dev/html/public/animate-layout/basic-position-change.html:1, dev/html/public/animate-layout/data-layout-true.html:1, dev/html/public/animate-layout/fire-and-forget.html:1, …

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.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×7) — dev/html/public/animate-layout/app-store-a-b-a.html:152, dev/html/public/animate-layout/app-store-a-b-a.html:171, dev/html/public/animate-layout/app-store-a-b-a.html:190, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 213 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:30

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IProjectionNode` declares 44 required operations: `mount`, `unmount`, `setOptions`, `isUpdateBlocked`, `blockUpdate`, `unblockUpdate`, `startUpdate`, `willUpdate`, `didUpdate`, `measure`, `measurePageBox`, `updateLayout`, `updateSnapshot`, `clearSnapshot`, `updateScroll`, `scheduleUpdateProjection`, `scheduleCheckAfterUnmount`, `checkUpdateFailed`, `registerSharedNode`, `getStack`, `hide`, `show`, `scheduleRender`, `getClosestProjectingParent`, `setTargetDelta`, `resetTransform`, `resetSkewAndRotation`, `applyTransform`, `resolveTargetDelta`, `removeRelativeTarget`, `calcProjection`, `applyProjectionStyles`, `clearMeasurements`, `resetTree`, `isProjecting`, `setAnimationOrigin`, `startAnimation`, `finishAnimation`, `isLead`, `promote`, and 4 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/motion-dom/src/projection/node/types.ts:40

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×33) — packages/framer-motion/cypress/integration/layout-shared.ts:215, packages/framer-motion/cypress/integration/layout-shared.ts:257, packages/framer-motion/cypress/integration/scroll.ts:310, …
  • `observe` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/framer-motion/src/jest.setup.tsx:28
  • `unobserve` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/framer-motion/src/jest.setup.tsx:29
  • `disconnect` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/framer-motion/src/jest.setup.tsx:30
  • `notifyReady` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:280
  • `rejectReady` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:281
  • `warning` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/motion-utils/src/errors.ts:9
  • `invariant` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/motion-utils/src/errors.ts:10

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)7.6 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 5 of 25 project(s) that lack one — worth up to 0.4 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging call was found in the 706 JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Adopt pino (or winston) and log at meaningful points in the services you run.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6334 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:30

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `fs.writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dev/inc/size-scenarios.mjs:420
  • `fs.readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — dev/inc/size-scenarios.mjs:429, dev/inc/size-scenarios.mjs:430
  • `fs.writeFileSync` in `signed` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — dev/inc/size-scenarios.mjs:490, dev/inc/size-scenarios.mjs:502

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • 9 duplicated blocks under packages/ have copies in at least two of the sibling directories framer-motion, motion, motion-dom, motion-utils — 8 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/motion-dom/rollup.config.mjs:1
  • packages/motion-dom/rollup.config.mjs:1 · packages/motion-utils/rollup.config.mjs:1 — these 2 files are line-for-line copies of one another — 78 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/motion-dom/rollup.config.mjs:1
  • dev/react-19/src/App.tsx:10 · dev/react/src/App.tsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/react-19/src/App.tsx:10
  • dev/html/src/three-animate.js:56 · dev/html/src/three-tsl.js:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/html/src/three-animate.js:56
  • dev/html/src/imports/script-animate.js:11 · dev/html/src/imports/script-undo.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/html/src/imports/script-animate.js:11
  • packages/framer-motion/rollup.config.mjs:33 · packages/motion/rollup.config.mjs:45 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/framer-motion/rollup.config.mjs:33
  • packages/framer-motion/rollup.size.config.mjs:7 · packages/motion-dom/rollup.size.config.mjs:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/framer-motion/rollup.size.config.mjs:7
  • packages/framer-motion/rollup.config.mjs:155 · packages/motion-dom/rollup.config.mjs:102 · packages/motion-utils/rollup.config.mjs:99 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/framer-motion/rollup.config.mjs:155
  • packages/framer-motion/src/components/Reorder/Group.tsx:185 · packages/framer-motion/src/remix-reorder.ts:185 — the two spans are one implementation copied and then locally edited — 151 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/framer-motion/src/components/Reorder/Group.tsx:185
  • dev/html/src/three-animate.js:108 · dev/html/src/three-tsl.js:114 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/html/src/three-animate.js:108
  • packages/framer-motion/rollup.config.mjs:93 · packages/motion/rollup.config.mjs:83 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/framer-motion/rollup.config.mjs:93
  • packages/framer-motion/rollup.config.mjs:125 · packages/motion-dom/rollup.config.mjs:81 · packages/motion-utils/rollup.config.mjs:78 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/framer-motion/rollup.config.mjs:125
  • dev/html/src/three-animate.js:116 · dev/html/src/three-effects.js:109 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/html/src/three-animate.js:116
  • packages/framer-motion/rollup.config.mjs:76 · packages/framer-motion/rollup.config.mjs:96 · packages/motion/rollup.config.mjs:86 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/framer-motion/rollup.config.mjs:76
  • packages/motion-dom/src/projection/geometry/delta-calc.ts:62 · packages/motion-dom/src/projection/geometry/delta-calc.ts:85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/motion-dom/src/projection/geometry/delta-calc.ts:62
  • packages/motion/src/three.ts:42 · packages/motion/src/vgpu.ts:83 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/motion/src/three.ts:42
  • packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:66 · packages/motion-dom/src/projection/node/create-projection-node.ts:952 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:66
  • packages/motion-dom/src/projection/geometry/delta-apply.ts:109 · packages/motion-dom/src/projection/node/create-projection-node.ts:1245 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/motion-dom/src/projection/geometry/delta-apply.ts:109
  • packages/framer-motion/src/render/components/m/elements.ts:8 · packages/framer-motion/src/render/components/m/elements.ts:18 · packages/framer-motion/src/render/components/m/elements.ts:28 · packages/framer-motion/src/render/components/m/elements.ts:38 · +37 more site(s) not listed — the 41 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/framer-motion/src/render/components/m/elements.ts:8
  • packages/motion-dom/src/projection/node/create-projection-node.ts:1351 · packages/motion-dom/src/projection/node/create-projection-node.ts:1556 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/motion-dom/src/projection/node/create-projection-node.ts:1351
  • dev/html/src/three-animate.js:6 · dev/html/src/three-xr.js:7 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — dev/html/src/three-animate.js:6
  • packages/framer-motion/src/value/use-combine-values.ts:35 · packages/motion-dom/src/value/subscribe-value.ts:10 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/framer-motion/src/value/use-combine-values.ts:35

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 Boundaries0.0 / 10Critical✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • dev/react-19/src/App.tsx:7 reaches into another package with a relative path (../../react/src/tests/*.tsx) — import the package by name instead. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-autoplay-false.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-cancel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-custom-mix.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-filter-blur.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-height-border-box.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-height.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-layout-timing.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-complete-multiple.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-height.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-no-op.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-layout.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-interrupt.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-layout-container.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-list.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-other-document.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-ref.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-rtl.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-shadow-root.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-subpixel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-propagate-empty.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-radix-dialog.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-remove.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-reorder.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-strict-dataset.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-suspense-reveal.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-switch-waapi.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-transition-exit.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-wait-exit-key-change.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-read-transform.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-reverse.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-sequence-spring.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-autoplay.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-complete.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-css-var.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-interrupt.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-pause.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-play.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7
  • dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-style-promise.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — dev/react-19/src/App.tsx:7

What to do

  • Fix the listed violations: move the shared test helper into a source directory production code may depend on (264 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row).
R2 · Cyclomatic Complexity8.3 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • scheduleUpdate has cyclomatic complexity 136 and cognitive complexity 140; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/projection/node/create-projection-node.ts:962
  • createProjectionNode has cyclomatic complexity 103 and cognitive complexity 129; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/projection/node/create-projection-node.ts:173
  • (anonymous) has cyclomatic complexity 53 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/render/utils/animation-state.ts:133
  • (anonymous) has cyclomatic complexity 35 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/remix.ts:1055
  • retime has cyclomatic complexity 34 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277
  • resolveValueSequence has cyclomatic complexity 32 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/animation/sequence/create.ts:127
  • (anonymous) has cyclomatic complexity 30 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/view/start.ts:506
  • animateTarget has cyclomatic complexity 29 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/animation/interfaces/visual-element-target.ts:34
  • onKeyDown has cyclomatic complexity 28 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/components/Reorder/Group.tsx:198
  • (anonymous) has cyclomatic complexity 27 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/view/start.ts:492
  • makeLatestValues has cyclomatic complexity 22 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/motion/utils/use-visual-state.ts:60
  • autoScrollIfNeeded has cyclomatic complexity 22 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/components/Reorder/utils/auto-scroll.ts:102
  • buildProjectionTransform has cyclomatic complexity 22 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/projection/styles/transform.ts:5
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/animation/interfaces/motion-value.ts:28
  • notifyLayoutUpdate has cyclomatic complexity 21 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/projection/node/create-projection-node.ts:2299
  • analyze has cyclomatic complexity 21 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dev/react/src/tests/start-transition-helpers.ts:247
  • mixTargetDelta has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/projection/node/create-projection-node.ts:1752
  • animate has cyclomatic complexity 20 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1106
  • makeLatestValues has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/framer-motion/src/remix.ts:443
  • main has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dev/inc/size-scenarios.mjs:413

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files8.8 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • packages/motion-dom/src/projection/node/create-projection-node.ts has 2260 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/projection/node/create-projection-node.ts:1
  • packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1
  • packages/framer-motion/src/remix.ts has 1226 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/framer-motion/src/remix.ts:1
  • packages/motion-dom/src/node/types.ts has 1050 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/node/types.ts:1
  • packages/motion-dom/src/view/start.ts has 851 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/view/start.ts:1
  • packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts has 832 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:1
  • packages/motion-dom/src/render/VisualElement.ts has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/render/VisualElement.ts:1
  • packages/motion-dom/src/animation/types.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/animation/types.ts:1
  • packages/framer-motion/src/animation/timeline/index.ts has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/framer-motion/src/animation/timeline/index.ts:1
  • packages/motion-dom/src/animation/JSAnimation.ts has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/animation/JSAnimation.ts:1
  • packages/motion-dom/src/value/index.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/value/index.ts:1
  • dev/inc/size-scenarios.mjs has 480 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dev/inc/size-scenarios.mjs:1
  • packages/framer-motion/src/animation/sequence/create.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/framer-motion/src/animation/sequence/create.ts:1
  • packages/motion-dom/src/animation/generators/spring.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/animation/generators/spring.ts:1
  • packages/framer-motion/src/remix-reorder.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/framer-motion/src/remix-reorder.ts:1
  • packages/framer-motion/src/components/Reorder/Board.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/framer-motion/src/components/Reorder/Board.tsx:1
  • packages/motion-dom/src/render/utils/animation-state.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/motion-dom/src/render/utils/animation-state.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.9 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — packages/framer-motion/src/remix.ts:1, dev/inc/size-scenarios.mjs:1, packages/framer-motion/src/remix-reorder.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code8.8 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 107 application, 19 tooling and 774 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/remix-reorder.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/framer-motion/src/remix.ts
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/remix.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/framer-motion/src/remix-reorder.ts
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×29) — packages/framer-motion/src/client.ts, dev/html/src/imports/script-animate.js, dev/html/src/imports/script-undo.js, …
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/animate-view.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/framer-motion/src/components/AnimateView/index.tsx
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/components/AnimateView/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/framer-motion/src/components/AnimateView/hooks/use-reset-view-transitions.ts, packages/framer-motion/src/components/AnimateView/shared-props.ts
  • no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/render/components/m/size.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/framer-motion/src/render/components/m/index.ts
  • Nothing imports this binding — it is safe to review for removal. (×4) — packages/framer-motion/src/animation/animate/subject.ts:26, packages/framer-motion/src/jest.setup.tsx:86, packages/framer-motion/src/motion/index.tsx:29, …

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 Hygiene2.0 / 10Critical✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — dev/remix/src/hydrate.tsx:1, packages/motion-dom/src/render/dom/__tests__/parse-transform.test.ts:1
  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports5.0 / 10Adequate✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts → packages/motion-dom/src/animation/NativeAnimationExtended.ts → packages/motion-dom/src/animation/NativeAnimation.ts → packages/motion-dom/src/utils/supports/scroll-timeline.ts → packages/motion-dom/src/index.ts → packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts (one verified cycle inside a mutually-dependent group of 35 files) — packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts:10

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `createAnimationsFromSequence` is exported, takes a document from its caller (line 45) and hands it to `resolveSequence`, which calls itself at line 102 (`resolveSequence`) with a piece of `sequence` — and nowhere in `resolveSequence` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveSequence` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/framer-motion/src/animation/sequence/create.ts:102

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/1 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.
  • `notifySlack` 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 })`. — scripts/notify-slack.js:61

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 guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `msg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — dev/html/src/imports/script-assert.js:12
  • `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — dev/html/src/three-tsl.js:155, dev/html/src/vgpu-scene.js:239, dev/html/src/vgpu.js:142

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — packages/motion-dom/src/animation/NativeAnimation.ts:164, packages/motion-dom/src/animation/utils/notify-inspector.ts:67, packages/motion-dom/src/animation/utils/notify-inspector.ts:89
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1258

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types7.5 / 10Strong✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 11/12 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~4.9 `!` null assertions per 1k TypeScript source lines — 213 assertion(s) across the 43487 source line(s) of the 527 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/motion-dom/src/projection/node/create-projection-node.ts (36), packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts (20), packages/framer-motion/src/components/Reorder/Board.tsx (16). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

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

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health64%Adequate — gated by D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture55%Adequate — gated by R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity60%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness36%Weak — gated by R8, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security75%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility35%Weak — gated by AC1, AC3, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D12 Dependency Hygiene — 92 observation(s) recorded · Not scored — 29 production npm declaration(s) across 10 package.json (10 of them the product) were read for PINNING discipline (2 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, which could not be reached on this run, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 53 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> motion-one@0.0.0 dev / > turbo run dev / sh: 1: turbo: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • D14 License Compliance — Not scored — this repository's 456 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 17 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 11 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • 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.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • 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: 553 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 78 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · <html> without a lang · ×14
  • <html> without a lang dev/html/public/animate-layout/app-store-a-b-a.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/app-store-layout.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/basic-position-change.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/data-layout-true.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/fire-and-forget.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/interrupt-animation.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-after-animate.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-close-interrupt.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-close-open-interrupt.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-close-open.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-close.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open-opacity.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/modal-open.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dev/html/public/animate-layout/parallel-calls-disjoint.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document without a <title> · ×12
  • Document without a <title> dev/html/public/animate-layout/app-store-a-b-a.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/basic-position-change.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/data-layout-true.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/fire-and-forget.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/interrupt-animation.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-after-animate.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-close-interrupt.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-close-open-interrupt.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-close-open.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-close.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open-opacity.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> dev/html/public/animate-layout/modal-open.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×7
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-a-b-a.html:152 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-a-b-a.html:171 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-a-b-a.html:190 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-layout.html:287 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-layout.html:328 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-layout.html:369 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> dev/html/public/animate-layout/app-store-layout.html:410 — A script attaches a click listener to this <li>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×2
  • No assertions (empty test): .then() returns Promise packages/motion-dom/src/animation/__tests__/GroupAnimation.test.ts:103 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): .then() can be chained packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:1282 — Test method has an empty body — it asserts nothing and exercises no code.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: page.tsx ↔ create-projection-node.ts dev/next/app/arcs/page.tsx:1 — `dev/next/app/arcs/page.tsx` (context dev) and `packages/motion-dom/src/projection/node/create-projection-node.ts` (context motion-dom) sit in DIFFERENT parts of the tree yet change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `8604ef3d` Make arcs injectable via `transition.path = arc()`; `f90fe294` add `orientToPath`; `4f481dcf` support keyframe arcs (at that commit the file was still `dev/next/app/layout-curve/page.tsx`) — run `git show` on any of them.
  • Boundary-crossing change coupling: page.tsx ↔ types.ts dev/next/app/arcs/page.tsx:1 — `dev/next/app/arcs/page.tsx` (context dev) and `packages/motion-dom/src/animation/types.ts` (context motion-dom) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8604ef3d` Make arcs injectable via `transition.path = arc()`; `f90fe294` add `orientToPath`; `71ea4507` cleaner example and api (at that commit the file was still `dev/next/app/layout-curve/page.tsx`) — run `git show` on any of them.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'remix' · ×1
  • Unlisted import 'remix' dev/remix/src/hydrate.tsx:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@thednp/dommatrix' · ×1
  • Unlisted import '@thednp/dommatrix' packages/motion-dom/src/render/dom/__tests__/parse-transform.test.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (5 files) · ×1
  • Import cycle (5 files) packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts:10 — packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts → packages/motion-dom/src/animation/NativeAnimationExtended.ts → packages/motion-dom/src/animation/NativeAnimation.ts → packages/motion-dom/src/utils/supports/scroll-timeline.ts → packages/motion-dom/src/index.ts → packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts (one verified cycle inside a mutually-dependent group of 35 files)
Serious — 528 finding(s)
D10 · Test Quality · No assertions · ×57
  • No assertions: Enter follows a nested link tests/react/reorder-nested-controls.spec.ts:64 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: whileHover returns to rest when the pointer leaves tests/react/while-hover-after-reorder.spec.ts:19 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: whileTap returns to rest when the press ends tests/react/while-hover-after-reorder.spec.ts:31 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: returns to constraints when clicked during the return animation tests/gestures/drag-constraints.spec.ts:253 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: change event is type-inferred packages/motion-dom/src/value/__tests__/motion-value.test.ts:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fires callbacks in the correct order packages/motion-dom/src/frameloop/__tests__/index.test.ts:4 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: cancels callbacks packages/motion-dom/src/frameloop/__tests__/index.test.ts:29 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fires callback on current frame if scheduled with `true` within the same step packages/motion-dom/src/frameloop/__tests__/index.test.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: re-runs a callback scheduled with `true` after it already ran in the same step packages/motion-dom/src/frameloop/__tests__/index.test.ts:63 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: runs a callback scheduled with `true` once, at the end of the step, if it hasn't run yet packages/motion-dom/src/frameloop/__tests__/index.test.ts:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: doesn't re-run a callback that schedules itself with `true` while running packages/motion-dom/src/frameloop/__tests__/index.test.ts:103 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: fires callback on next frame if scheduled with `true` outside the same step packages/motion-dom/src/frameloop/__tests__/index.test.ts:117 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: uses default elapsed time if first fire packages/motion-dom/src/frameloop/__tests__/index.test.ts:127 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: correctly cancels packages/motion-dom/src/frameloop/__tests__/index.test.ts:143 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: correctly keeps alive packages/motion-dom/src/frameloop/__tests__/index.test.ts:153 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: correctly cancels a keepAlive process packages/motion-dom/src/frameloop/__tests__/index.test.ts:161 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Fires onPlay packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: .then() correctly fires packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:1294 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: .then() correctly fires when animation already finished packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:1303 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: .then() returns new Promise when animation finished packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:1315 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Correctly ends animations with duration: 0 packages/motion-dom/src/animation/__tests__/JSAnimation.test.ts:1502 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: typechecks public declarations with React 18 and skipLibCheck disabled packages/motion/src/__tests__/react-animate-view.test.ts:10 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: keeps React 18 imports and rendering working in %s packages/motion/src/__tests__/react-animate-view.test.ts:95 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: is correctly typed packages/framer-motion/src/value/__tests__/use-transform.test.tsx:137 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: is correctly typed packages/framer-motion/src/value/__tests__/use-transform.test.tsx:442 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 32 more in this group — see findings.md.
D10 · Test Quality · Skipped test · ×53
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:69 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:85 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:96 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:114 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:128 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:142 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:159 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:172 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:189 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:203 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:216 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:229 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:242 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:265 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:284 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:300 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:320 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:337 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:358 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:377 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:393 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:412 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:428 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:445 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/view/view-targets.spec.ts:460 — Skipped — switched off by test.skip
  • + 28 more in this group — see findings.md.
R11 · Import Boundaries · Boundary violation [package · ×40
  • Boundary violation [package:relative-cross-package] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 reaches into another package with a relative path (../../react/src/tests/*.tsx) — import the package by name instead.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-autoplay-false.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-cancel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-custom-mix.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-filter-blur.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-height-border-box.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-height.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-layout-timing.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-complete-multiple.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-height.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-exit-no-op.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-layout.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-interrupt.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-layout-container.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-list.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-other-document.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-ref.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-rtl.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-shadow-root.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop-subpixel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-pop.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-propagate-empty.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-radix-dialog.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-remove.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] dev/react-19/src/App.tsx:7 — dev/react-19/src/App.tsx:7 imports dev/react/src/tests/animate-presence-reorder.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file packages/framer-motion/src/remix.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/inc/size-scenarios.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/framer-motion/src/remix-reorder.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/vgpu-scene.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/generate-changelog.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/imports/script-assert.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/three-tsl.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/vgpu.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/three-animate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/notify-slack.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/three-effects.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/next/app/layout-id/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/imports/script-animate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/inc/bundlesize.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/imports/script-undo.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/html/src/three-xr.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/framer-motion/src/components/AnimateView/index.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/framer-motion/scripts/check-bundle.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/react-19/src/App.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/react/src/App.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/push-to-site.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/next/app/arcs/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/next/app/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/inc/jsxRuntimeShim.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file dev/inc/collect-html-tests.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×34
  • Hotspot: packages/motion-dom/src/projection/node/create-projection-node.ts packages/motion-dom/src/projection/node/create-projection-node.ts:173 — packages/motion-dom/src/projection/node/create-projection-node.ts changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 293 in create-projection-node.createProjectionNode at line 173. 4 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/projection/node/create-projection-node.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:649 — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 157 in TransformAnimation.createGroup at line 649. 4 of those changes were fix/bug commits, and the other 37 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/render/utils/animation-state.ts packages/motion-dom/src/render/utils/animation-state.ts:82 — packages/motion-dom/src/render/utils/animation-state.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in animation-state.createAnimationState.animateChanges at line 82. 1 of those changes was a fix/bug commit, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/render/utils/animation-state.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/components/Reorder/Group.tsx packages/framer-motion/src/components/Reorder/Group.tsx:90 — packages/framer-motion/src/components/Reorder/Group.tsx changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in Group.ReorderGroupComponent at line 90. 2 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/components/Reorder/Group.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:158 — packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in VisualElementDragControls.start at line 158. 3 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/generators/spring.ts packages/motion-dom/src/animation/generators/spring.ts:272 — packages/motion-dom/src/animation/generators/spring.ts changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in spring.springGenerator at line 272. 2 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/generators/spring.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/gestures/press/index.ts packages/motion-dom/src/gestures/press/index.ts:89 — packages/motion-dom/src/gestures/press/index.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in index.press at line 89. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/gestures/press/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/animation/timeline/index.ts packages/framer-motion/src/animation/timeline/index.ts:478 — packages/framer-motion/src/animation/timeline/index.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Timeline.build at line 478. 1 of those changes was a fix/bug commit, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/animation/timeline/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/JSAnimation.ts packages/motion-dom/src/animation/JSAnimation.ts:205 — packages/motion-dom/src/animation/JSAnimation.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in JSAnimation.tick at line 205. 1 of those changes was a fix/bug commit, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/JSAnimation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/components/Reorder/Item.tsx packages/framer-motion/src/components/Reorder/Item.tsx:64 — packages/framer-motion/src/components/Reorder/Item.tsx changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Item.ReorderItemComponent at line 64. 2 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/components/Reorder/Item.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/interfaces/visual-element-target.ts packages/motion-dom/src/animation/interfaces/visual-element-target.ts:34 — packages/motion-dom/src/animation/interfaces/visual-element-target.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in visual-element-target.animateTarget at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/interfaces/visual-element-target.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/remix.ts packages/framer-motion/src/remix.ts:761 — packages/framer-motion/src/remix.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in remix.motionMixin at line 761. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/remix.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/animation/sequence/create.ts packages/framer-motion/src/animation/sequence/create.ts:45 — packages/framer-motion/src/animation/sequence/create.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in create.createAnimationsFromSequence at line 45. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/animation/sequence/create.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/render/VisualElement.ts packages/motion-dom/src/render/VisualElement.ts:449 — packages/motion-dom/src/render/VisualElement.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in VisualElement.mount at line 449. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/render/VisualElement.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/render/dom/scroll/attach-animation.ts packages/framer-motion/src/render/dom/scroll/attach-animation.ts:8 — packages/framer-motion/src/render/dom/scroll/attach-animation.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in attach-animation.attachToAnimation at line 8. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/render/dom/scroll/attach-animation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/remix-reorder.ts packages/framer-motion/src/remix-reorder.ts:117 — packages/framer-motion/src/remix-reorder.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in remix-reorder.createReorder.Group at line 117. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/remix-reorder.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts:72 — packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in DOMKeyframesResolver.readKeyframes at line 72. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/components/AnimatePresence/index.tsx packages/framer-motion/src/components/AnimatePresence/index.tsx:46 — packages/framer-motion/src/components/AnimatePresence/index.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in index.AnimatePresence at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/components/AnimatePresence/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/motion/utils/use-visual-element.ts packages/framer-motion/src/motion/utils/use-visual-element.ts:22 — packages/framer-motion/src/motion/utils/use-visual-element.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in use-visual-element.useVisualElement at line 22. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/motion/utils/use-visual-element.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/generators/keyframes.ts packages/motion-dom/src/animation/generators/keyframes.ts:26 — packages/motion-dom/src/animation/generators/keyframes.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in keyframes.keyframes at line 26. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/generators/keyframes.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/animate/effects.ts packages/motion-dom/src/animation/animate/effects.ts:65 — packages/motion-dom/src/animation/animate/effects.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in effects.animateValues at line 65. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/animate/effects.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/waapi/supports/waapi.ts packages/motion-dom/src/animation/waapi/supports/waapi.ts:32 — packages/motion-dom/src/animation/waapi/supports/waapi.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in waapi.supportsBrowserAnimation at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/waapi/supports/waapi.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts:91 — packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in AsyncMotionValueAnimation.onKeyframesResolved at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/motion-dom/src/animation/AsyncMotionValueAnimation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/components/AnimatePresence/PopChild.tsx packages/framer-motion/src/components/AnimatePresence/PopChild.tsx:123 — packages/framer-motion/src/components/AnimatePresence/PopChild.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PopChild.PopChild at line 123. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/components/AnimatePresence/PopChild.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/framer-motion/src/components/Reorder/Board.tsx packages/framer-motion/src/components/Reorder/Board.tsx:324 — packages/framer-motion/src/components/Reorder/Board.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Board.createBoard.receive at line 324. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/components/Reorder/Board.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 9 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×26
  • TodoComment packages/motion-dom/src/utils/resolve-elements.ts:17 — // TODO: Refactor to types package AnimationPlaybackControls[] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/utils/mix/color.ts:39 — // TODO Remove this cast - needed since Motion's stricter typing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/render/utils/setters.ts:31 — // TODO maybe throw if v.length - 1 is placeholder token? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/styles/scale-box-shadow.ts:10 — // TODO: Doesn't support multiple shadows — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/styles/__tests__/scale-correction.test.ts:102 — // TODO: Only supports a single shadow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/node/create-projection-node.ts:663 — // TODO: Check here if an animation exists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/node/create-projection-node.ts:1723 — // TODO: Schedule render — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/node/create-projection-node.ts:1727 — // TODO: Schedule render — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/node/create-projection-node.ts:2005 — // TODO Only running on root node — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/projection/node/create-projection-node.ts:2313 — // TODO Maybe we want to also resize the layout snapshot so we don't trigger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/node/types.ts:760 — // TODO: Replace with DragControls when ported to motion-dom — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:494 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:966 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:1081 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/animation/JSAnimation.ts:280 — // TODO: The exception for inertia could be cleaner here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/animation/types.ts:160 — // TODO: Replace with VisualElement when moved into motion-dom — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/animation/keyframes/KeyframesResolver.ts:206 — // TODO: This doesn't work if the final keyframe is a wildcard — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/motion-dom/src/animation/generators/keyframes.ts:124 — // TODO Maybe we should warn here if there's a length mismatch — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/src/render/dom/scroll/types.ts:23 — // TODO Rename before documenting — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/src/motion/__tests__/component.test.tsx:186 — // TODO: Replace dynamic variable test when we implement `custom` attribute: https://github.com/framer/company/issues/12508
  • TodoComment packages/framer-motion/src/events/__tests__/use-event.test.tsx:8 — // TODO maybe show a warning too? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/cypress/integration/drag-svg.ts:84 — // TODO: Figure out direction lock tests in Cypress — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/cypress/integration/drag-svg.ts:250 — // TODO: Figure out direction lock tests in Cypress — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/cypress/integration/drag.ts:76 — // TODO: This should actually be 400, but for some reason the test scroll — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/framer-motion/cypress/integration/drag.ts:101 — // TODO: This should actually be 400, but for some reason the test scroll — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 1 more in this group — see findings.md.
AC3 · Page structure · Page without a main landmark · ×14
  • Page without a main landmark dev/html/index.html:2 — 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="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark dev/html/public/animate-layout/app-store-a-b-a.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/app-store-layout.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/basic-position-change.html:1 — 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="box">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark dev/html/public/animate-layout/data-layout-true.html:1 — 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="box">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark dev/html/public/animate-layout/fire-and-forget.html:1 — 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="box">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark dev/html/public/animate-layout/interrupt-animation.html:1 — 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="box">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-after-animate.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-close-interrupt.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-close-open-interrupt.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-close-open.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-close.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open-opacity.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark dev/html/public/animate-layout/modal-open.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · FunctionTooLong · ×13
  • FunctionTooLong: create-projection-node.createProjectionNode packages/motion-dom/src/projection/node/create-projection-node.ts:173 — FunctionTooLong — createProjectionNode runs 1028 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 928 over it, 10.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: TransformAnimation.createGroup packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:649 — FunctionTooLong — createGroup runs 449 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 349 over it, 4.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: start.startViewAnimation packages/motion-dom/src/view/start.ts:64 — FunctionTooLong — startViewAnimation runs 399 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 299 over it, 3.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: remix-reorder.createReorder packages/framer-motion/src/remix-reorder.ts:112 — FunctionTooLong — createReorder runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: animation-state.createAnimationState packages/motion-dom/src/render/utils/animation-state.ts:66 — FunctionTooLong — createAnimationState runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Board.createBoard packages/framer-motion/src/components/Reorder/Board.tsx:116 — FunctionTooLong — createBoard runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: animation-state.createAnimationState.animateChanges packages/motion-dom/src/render/utils/animation-state.ts:82 — FunctionTooLong — createAnimationState.animateChanges runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: remix-reorder.createReorder.Group packages/framer-motion/src/remix-reorder.ts:117 — FunctionTooLong — createReorder.Group runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: spring.springGenerator packages/motion-dom/src/animation/generators/spring.ts:272 — FunctionTooLong — springGenerator runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: shared-element-nested-children-bottom.html.runTest dev/html/public/animate-layout/shared-element-nested-children-bottom.html:247 — FunctionTooLong — runTest runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.AnimatePresence packages/framer-motion/src/components/AnimatePresence/index.tsx:46 — FunctionTooLong — AnimatePresence runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: vgpu-scene.start dev/html/src/vgpu-scene.js:80 — FunctionTooLong — start runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.createScopedAnimate packages/framer-motion/src/animation/animate/index.ts:41 — FunctionTooLong — createScopedAnimate runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium CVE · ×13
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R7 · Dead Code · Dead file (~1 LoC) · ×9
  • Dead file (~1 LoC) packages/framer-motion/src/gestures/types.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/framer-motion/src/mini.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/framer-motion/src/render/components/m/index.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/render/components/m/size.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~1 LoC) packages/framer-motion/src/render/svg/types-attributes.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/motion/src/debug.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/motion/src/mini.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/motion/src/react-client.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/motion/src/react-m.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/motion/src/react-mini.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC1 · Text alternatives · <canvas> without a text alternative · ×6
  • <canvas> without a text alternative dev/html/three-animate.html:22 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative dev/html/three-effects.html:24 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative dev/html/three-tsl.html:25 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative dev/html/three-xr.html:25 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative dev/html/vgpu-scene.html:24 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative dev/html/vgpu.html:26 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
R7 · Dead Code · Dead file (~3 LoC) · ×6
  • Dead file (~3 LoC) dev/html/src/imports/anime.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~3 LoC) dev/html/src/imports/framer-motion-dom.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~3 LoC) dev/html/src/imports/projection.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~3 LoC) dev/html/src/imports/view.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~3 LoC) packages/framer-motion/src/components/AnimateView/shared-props.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/components/AnimateView/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~3 LoC) packages/motion/src/react-animate-view.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
PF3 · Async & latency hygiene · Sync-over-async blocking · ×5
  • Sync-over-async blocking dev/inc/size-scenarios.mjs:420 — `fs.writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dev/inc/size-scenarios.mjs:429 — `fs.readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dev/inc/size-scenarios.mjs:430 — `fs.readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dev/inc/size-scenarios.mjs:490 — `fs.writeFileSync` in `signed` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dev/inc/size-scenarios.mjs:502 — `fs.writeFileSync` in `signed` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
D2 · Cognitive Complexity · TransformAnimation.createGroup · ×4
  • TransformAnimation.createGroup::retime (cognitive 44) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277 — TransformAnimation.createGroup::retime has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 12, loops 3, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (TransformAnimation.createGroup::getEasing, TransformAnimation.createGroup::animate, TransformAnimation.createGroup::build) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • TransformAnimation.createGroup::animate (cognitive 31) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1106 — TransformAnimation.createGroup::animate has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 7, error handling 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (TransformAnimation.createGroup::getEasing, TransformAnimation.createGroup::retime, TransformAnimation.createGroup::build) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • TransformAnimation.createGroup::build (cognitive 18) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1401 — TransformAnimation.createGroup::build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (TransformAnimation.createGroup::getEasing, TransformAnimation.createGroup::animate, TransformAnimation.createGroup::retime) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • TransformAnimation.createGroup::getEasing (cognitive 17) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:820 — TransformAnimation.createGroup::getEasing has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 2, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (TransformAnimation.createGroup::animate, TransformAnimation.createGroup::retime, TransformAnimation.createGroup::build) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
R7 · Dead Code · Dead file (~2 LoC) · ×4
  • Dead file (~2 LoC) packages/framer-motion/src/debug.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~2 LoC) packages/framer-motion/src/dom-mini.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~2 LoC) packages/framer-motion/src/render/components/m/size.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~2 LoC) packages/framer-motion/src/render/components/motion/size.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×4
  • Untrusted text written into markup unescaped dev/html/src/imports/script-assert.js:12 — `msg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped dev/html/src/three-tsl.js:155 — `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped dev/html/src/vgpu-scene.js:239 — `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped dev/html/src/vgpu.js:142 — `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
D3 · God Classes · FileTooLong · ×3
  • FileTooLong: node/create-projection-node.ts packages/motion-dom/src/projection/node/create-projection-node.ts — FileTooLong — 1339 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: createProjectionNode (173-2288). The bar is 500 significant lines; this is 839 over it, 2.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: transforms/TransformAnimation.ts packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts — FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 258 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/remix.ts packages/framer-motion/src/remix.ts — FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 242 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: ProjectionNode packages/motion-dom/src/projection/node/create-projection-node.ts:191 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. Most of these members implement types.IProjectionNode (42 of 61 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: VisualElement packages/motion-dom/src/render/VisualElement.ts:90 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Timeline packages/framer-motion/src/animation/timeline/index.ts:136 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) packages/motion-dom/src/animation/NativeAnimation.ts:164 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/motion-dom/src/animation/utils/notify-inspector.ts:67 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/motion-dom/src/animation/utils/notify-inspector.ts:89 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D1 · Cyclomatic Complexity · TransformAnimation.createGroup · ×2
  • TransformAnimation.createGroup::retime (cyclomatic 34) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277 — TransformAnimation.createGroup::retime has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (TransformAnimation.createGroup::animate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • TransformAnimation.createGroup::animate (cyclomatic 21) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1106 — TransformAnimation.createGroup::animate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (TransformAnimation.createGroup::retime) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D12 · Dependency Hygiene · One package at two majors across the workspace · ×2
  • One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 18 in dev/html/package.json, dev/react/package.json; major 19 in dev/next/package.json, dev/react-19/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 18 in dev/html/package.json, dev/react/package.json; major 19 in dev/next/package.json, dev/react-19/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
D2 · Cognitive Complexity · create.createAnimationsFromSequence · ×2
  • create.createAnimationsFromSequence::resolveSequence::resolveValueSequence (cognitive 47) packages/framer-motion/src/animation/sequence/create.ts:127 — create.createAnimationsFromSequence::resolveSequence::resolveValueSequence has cognitive complexity 47 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 6 (14 pts), boolean chains 12, loops 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (create.createAnimationsFromSequence::resolveSequence) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • create.createAnimationsFromSequence::resolveSequence (cognitive 23) packages/framer-motion/src/animation/sequence/create.ts:72 — create.createAnimationsFromSequence::resolveSequence has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (8 pts), ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (create.createAnimationsFromSequence::resolveSequence::resolveValueSequence) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: motion-utils — motion-utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: motion — motion: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×2
  • Duplicated block (32 lines × 2 locations) packages/framer-motion/rollup.config.mjs:33 — packages/framer-motion/rollup.config.mjs:33 · packages/motion/rollup.config.mjs:45 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (32 lines × 2 locations) packages/framer-motion/rollup.size.config.mjs:7 — packages/framer-motion/rollup.size.config.mjs:7 · packages/motion-dom/rollup.size.config.mjs:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×2
  • Duplicated block (9 lines × 2 locations) packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:66 — packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:66 · packages/motion-dom/src/projection/node/create-projection-node.ts:952 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (9 lines × 2 locations) packages/motion-dom/src/projection/geometry/delta-apply.ts:109 — packages/motion-dom/src/projection/geometry/delta-apply.ts:109 · packages/motion-dom/src/projection/node/create-projection-node.ts:1245 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R7 · Dead Code · Dead file (~17 LoC) · ×2
  • Dead file (~17 LoC) dev/html/src/imports/animate-layout.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~17 LoC) packages/framer-motion/src/components/AnimateView/hooks/use-reset-view-transitions.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/components/AnimateView/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~6 LoC) · ×2
  • Dead file (~6 LoC) dev/html/src/imports/gsap.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~6 LoC) packages/framer-motion/src/render/utils/is-draggable.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung package.json:30 — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 213 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · create-projection-node.createProjectionNode (cyclomatic 293) · ×1
  • create-projection-node.createProjectionNode (cyclomatic 293) packages/motion-dom/src/projection/node/create-projection-node.ts:173 — create-projection-node.createProjectionNode has cyclomatic complexity 293 (threshold 15). Of this number, 261 points are the body's own statements and 32 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · start.startViewAnimation (cyclomatic 91) · ×1
  • start.startViewAnimation (cyclomatic 91) packages/motion-dom/src/view/start.ts:64 — start.startViewAnimation has cyclomatic complexity 91 (threshold 15). Most of this is not in the body itself: 3 of the 91 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 506, a function literal at line 492, a function literal at line 140, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · animation-state.createAnimationState.animateChanges (cyclomatic 83) · ×1
  • animation-state.createAnimationState.animateChanges (cyclomatic 83) packages/motion-dom/src/render/utils/animation-state.ts:82 — animation-state.createAnimationState.animateChanges has cyclomatic complexity 83 (threshold 15). Of this number, 16 points are the body's own statements and 67 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · Group.ReorderGroupComponent (cyclomatic 47) · ×1
  • Group.ReorderGroupComponent (cyclomatic 47) packages/framer-motion/src/components/Reorder/Group.tsx:90 — Group.ReorderGroupComponent has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 5 of the 47 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 198, a function literal at line 293, a function literal at line 282, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · remix.motionMixin (cyclomatic 40) · ×1
  • remix.motionMixin (cyclomatic 40) packages/framer-motion/src/remix.ts:761 — remix.motionMixin has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 18 function items inside it that branch (a function literal at line 1014, a function literal at line 961, acquireProjection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · remix.motionMixin.<returned closure> (cyclomatic 36) · ×1
  • remix.motionMixin.<returned closure> (cyclomatic 36) packages/framer-motion/src/remix.ts:1055 — remix.motionMixin.<returned closure> has cyclomatic complexity 36 (threshold 15). Of this number, 34 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remix-reorder.createReorder.Group (cyclomatic 36) · ×1
  • remix-reorder.createReorder.Group (cyclomatic 36) packages/framer-motion/src/remix-reorder.ts:117 — remix-reorder.createReorder.Group has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 13 function items inside it that branch (a function literal at line 193, a function literal at line 273, a function literal at line 177, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ProjectionNode.resolveTargetDelta (cyclomatic 36) · ×1
  • ProjectionNode.resolveTargetDelta (cyclomatic 36) packages/motion-dom/src/projection/node/create-projection-node.ts:1351 — ProjectionNode.resolveTargetDelta has cyclomatic complexity 36 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ProjectionNode.applyProjectionStyles (cyclomatic 35) · ×1
  • ProjectionNode.applyProjectionStyles (cyclomatic 35) packages/motion-dom/src/projection/node/create-projection-node.ts:2116 — ProjectionNode.applyProjectionStyles has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · create.createAnimationsFromSequence · ×1
  • create.createAnimationsFromSequence::resolveSequence::resolveValueSequence (cyclomatic 32) packages/framer-motion/src/animation/sequence/create.ts:127 — create.createAnimationsFromSequence::resolveSequence::resolveValueSequence has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProjectionNode.calcProjection (cyclomatic 30) · ×1
  • ProjectionNode.calcProjection (cyclomatic 30) packages/motion-dom/src/projection/node/create-projection-node.ts:1556 — ProjectionNode.calcProjection has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · index.AnimatePresence (cyclomatic 28) · ×1
  • index.AnimatePresence (cyclomatic 28) packages/framer-motion/src/components/AnimatePresence/index.tsx:46 — index.AnimatePresence has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 210, 219, 95, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · visual-element-target.animateTarget (cyclomatic 28) · ×1
  • visual-element-target.animateTarget (cyclomatic 28) packages/motion-dom/src/animation/interfaces/visual-element-target.ts:34 — visual-element-target.animateTarget has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create-projection-node.notifyLayoutUpdate (cyclomatic 28) · ×1
  • create-projection-node.notifyLayoutUpdate (cyclomatic 28) packages/motion-dom/src/projection/node/create-projection-node.ts:2299 — create-projection-node.notifyLayoutUpdate has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · use-visual-element.useVisualElement (cyclomatic 26) · ×1
  • use-visual-element.useVisualElement (cyclomatic 26) packages/framer-motion/src/motion/utils/use-visual-element.ts:22 — use-visual-element.useVisualElement has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · VisualElementDragControls.start (cyclomatic 26) · ×1
  • VisualElementDragControls.start (cyclomatic 26) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:158 — VisualElementDragControls.start has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (onMove, onStart, a function literal at line 200, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · keyframes.keyframes (cyclomatic 25) · ×1
  • keyframes.keyframes (cyclomatic 25) packages/motion-dom/src/animation/generators/keyframes.ts:26 — keyframes.keyframes has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · motion-value.animateMotionValue.<returned closure> (cyclomatic 24) · ×1
  • motion-value.animateMotionValue.<returned closure> (cyclomatic 24) packages/motion-dom/src/animation/interfaces/motion-value.ts:28 — motion-value.animateMotionValue.<returned closure> has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ProjectionNode.addLayoutListener (cyclomatic 23) · ×1
  • ProjectionNode.addLayoutListener (cyclomatic 23) packages/motion-dom/src/projection/node/create-projection-node.ts:636 — ProjectionNode.addLayoutListener has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 651). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · use-visual-state.makeLatestValues (cyclomatic 22) · ×1
  • use-visual-state.makeLatestValues (cyclomatic 22) packages/framer-motion/src/motion/utils/use-visual-state.ts:60 — use-visual-state.makeLatestValues has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · auto-scroll.autoScrollIfNeeded (cyclomatic 22) · ×1
  • auto-scroll.autoScrollIfNeeded (cyclomatic 22) packages/framer-motion/src/components/Reorder/utils/auto-scroll.ts:102 — auto-scroll.autoScrollIfNeeded has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · spring.springGenerator (cyclomatic 22) · ×1
  • spring.springGenerator (cyclomatic 22) packages/motion-dom/src/animation/generators/spring.ts:272 — spring.springGenerator has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (setRestThresholds, a function literal at line 478, a function literal at line 466, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · transform.buildProjectionTransform (cyclomatic 22) · ×1
  • transform.buildProjectionTransform (cyclomatic 22) packages/motion-dom/src/projection/styles/transform.ts:5 — transform.buildProjectionTransform has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProjectionNode.setAnimationOrigin (cyclomatic 22) · ×1
  • ProjectionNode.setAnimationOrigin (cyclomatic 22) packages/motion-dom/src/projection/node/create-projection-node.ts:1755 — ProjectionNode.setAnimationOrigin has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 45 methods over the threshold — including the worst — and 362 of the 802 points over it (45%), 4.8× the next-largest file (packages/motion-dom/src/view/start.ts at 76). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · main (cyclomatic 21) · ×1
  • main (cyclomatic 21) dev/inc/size-scenarios.mjs:413 — main has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Timeline.build (cyclomatic 20) · ×1
  • Timeline.build (cyclomatic 20) packages/framer-motion/src/animation/timeline/index.ts:478 — Timeline.build has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · start.startOptimizedAppearAnimation (cyclomatic 20) · ×1
  • start.startOptimizedAppearAnimation (cyclomatic 20) packages/framer-motion/src/animation/optimized-appear/start.ts:45 — start.startOptimizedAppearAnimation has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 124, a function literal at line 86, a function literal at line 166, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Item.ReorderItemComponent (cyclomatic 20) · ×1
  • Item.ReorderItemComponent (cyclomatic 20) packages/framer-motion/src/components/Reorder/Item.tsx:64 — Item.ReorderItemComponent has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 180, a function literal at line 116, grab, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · remix.makeLatestValues (cyclomatic 20) · ×1
  • remix.makeLatestValues (cyclomatic 20) packages/framer-motion/src/remix.ts:443 — remix.makeLatestValues has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.scopeMotion (cyclomatic 20) · ×1
  • index.scopeMotion (cyclomatic 20) packages/motion-dom/src/scope/index.ts:109 — index.scopeMotion has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (start, clear, kill, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · JSAnimation.tick (cyclomatic 20) · ×1
  • JSAnimation.tick (cyclomatic 20) packages/motion-dom/src/animation/JSAnimation.ts:205 — JSAnimation.tick has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DOMKeyframesResolver.readKeyframes (cyclomatic 19) · ×1
  • DOMKeyframesResolver.readKeyframes (cyclomatic 19) packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts:72 — DOMKeyframesResolver.readKeyframes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PopChild.PopChild (cyclomatic 18) · ×1
  • PopChild.PopChild (cyclomatic 18) packages/framer-motion/src/components/AnimatePresence/PopChild.tsx:123 — PopChild.PopChild has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 181, insertPopRule, a function literal at line 222, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · effects.animateValues (cyclomatic 18) · ×1
  • effects.animateValues (cyclomatic 18) packages/motion-dom/src/animation/animate/effects.ts:65 — effects.animateValues has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.press · ×1
  • index.press::startPress (cyclomatic 18) packages/motion-dom/src/gestures/press/index.ts:103 — index.press::startPress has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · size-scenarios.check (cyclomatic 17) · ×1
  • size-scenarios.check (cyclomatic 17) dev/inc/size-scenarios.mjs:360 — size-scenarios.check has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · waapi.supportsBrowserAnimation (cyclomatic 17) · ×1
  • waapi.supportsBrowserAnimation (cyclomatic 17) packages/motion-dom/src/animation/waapi/supports/waapi.ts:32 — waapi.supportsBrowserAnimation has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · delta-apply.applyTreeDeltas (cyclomatic 17) · ×1
  • delta-apply.applyTreeDeltas (cyclomatic 17) packages/motion-dom/src/projection/geometry/delta-apply.ts:81 — delta-apply.applyTreeDeltas has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · animate-view-layers.animateViewLayers (cyclomatic 16) · ×1
  • animate-view-layers.animateViewLayers (cyclomatic 16) packages/framer-motion/src/components/AnimateView/animate-view-layers.ts:22 — animate-view-layers.animateViewLayers has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · mix-values.mixValues (cyclomatic 16) · ×1
  • mix-values.mixValues (cyclomatic 16) packages/motion-dom/src/projection/animation/mix-values.ts:20 — mix-values.mixValues has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VisualElement.mount (cyclomatic 16) · ×1
  • VisualElement.mount (cyclomatic 16) packages/motion-dom/src/render/VisualElement.ts:449 — VisualElement.mount has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · VisualElementDragControls.resolveConstraints (cyclomatic 16) · ×1
  • VisualElementDragControls.resolveConstraints (cyclomatic 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:411 — VisualElementDragControls.resolveConstraints has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · VisualElementDragControls.startAnimation (cyclomatic 16) · ×1
  • VisualElementDragControls.startAnimation (cyclomatic 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:541 — VisualElementDragControls.startAnimation has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (axisVelocity, a function literal at line 587). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: @base-ui-components/react dev/react/package.json:13 — @base-ui-components/react 1.0.0-rc.0, declared in dev/react/package.json, is marked deprecated by its publisher: "Package was renamed to @base-ui/react". Replace it with the package or version that message names, or record why this one must stay.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: packages/framer-motion/src/motion/features/animation/exit.ts packages/framer-motion/src/motion/features/animation/exit.ts:13 — packages/framer-motion/src/motion/features/animation/exit.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ExitAnimationFeature.update at line 13), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix AnimatePresence exit never starting when a child mounts already exiting”; “Fix AnimatePresence popLayout for children that can't take a ref (#2503)”; “Fix AnimatePresence child stuck at initial after re-entering during exit (#3834)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:05:42 +01:00' --until='2026-11-06 15:05:42 +01:00' --full-history --no-merges -- packages/framer-motion/src/motion/features/animation/exit.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · create-projection-node.createProjectionNode (cognitive 270) · ×1
  • create-projection-node.createProjectionNode (cognitive 270) packages/motion-dom/src/projection/node/create-projection-node.ts:173 — create-projection-node.createProjectionNode has cognitive complexity 270 (threshold 15). Drivers by points: if/else 119 (147 pts), boolean chains 98, loops 11 (14 pts), ternaries 10 (11 pts) (nesting depth added 32). Of this number, 245 points are the body's own statements and 25 belong to 7 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · start.startViewAnimation (cognitive 146) · ×1
  • start.startViewAnimation (cognitive 146) packages/motion-dom/src/view/start.ts:64 — start.startViewAnimation has cognitive complexity 146 (threshold 15). Drivers by points: if/else 37 (71 pts), ternaries 15 (40 pts), boolean chains 23, loops 7 (11 pts), error handling 1 (nesting depth added 63). Most of this is not in the body itself: 2 of the 146 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 506, a function literal at line 492, a function literal at line 140, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · animation-state.createAnimationState.animateChanges (cognitive 88) · ×1
  • animation-state.createAnimationState.animateChanges (cognitive 88) packages/motion-dom/src/render/utils/animation-state.ts:82 — animation-state.createAnimationState.animateChanges has cognitive complexity 88 (threshold 15). Drivers by points: boolean chains 42, if/else 18 (30 pts), ternaries 7 (10 pts), loops 4 (6 pts) (nesting depth added 17). Most of this is not in the body itself: 15 of the 88 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 133, a function literal at line 315, resolveInitial). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · create-projection-node.notifyLayoutUpdate (cognitive 50) · ×1
  • create-projection-node.notifyLayoutUpdate (cognitive 50) packages/motion-dom/src/projection/node/create-projection-node.ts:2299 — create-projection-node.notifyLayoutUpdate has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (28 pts), ternaries 4 (12 pts), boolean chains 10 (nesting depth added 25). Of this number, 38 points are the body's own statements and 12 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Group.ReorderGroupComponent (cognitive 49) · ×1
  • Group.ReorderGroupComponent (cognitive 49) packages/framer-motion/src/components/Reorder/Group.tsx:90 — Group.ReorderGroupComponent has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 18, if/else 14 (17 pts), ternaries 7 (13 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 4 of the 49 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 198, a function literal at line 282, a function literal at line 293, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · use-visual-state.makeLatestValues (cognitive 43) · ×1
  • use-visual-state.makeLatestValues (cognitive 43) packages/framer-motion/src/motion/utils/use-visual-state.ts:60 — use-visual-state.makeLatestValues has cognitive complexity 43 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 4 (11 pts), ternaries 4 (10 pts), boolean chains 3 (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · remix.motionMixin.<returned closure> (cognitive 43) · ×1
  • remix.motionMixin.<returned closure> (cognitive 43) packages/framer-motion/src/remix.ts:1055 — remix.motionMixin.<returned closure> has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 10, loops 1 (nesting depth added 14). Of this number, 40 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remix.motionMixin (cognitive 37) · ×1
  • remix.motionMixin (cognitive 37) packages/framer-motion/src/remix.ts:761 — remix.motionMixin has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 13, ternaries 4 (nesting depth added 1). None of this is in the body itself: all 37 points belong to 18 function items inside it that branch (a function literal at line 1014, acquireProjection, startExit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · remix-reorder.createReorder.Group (cognitive 37) · ×1
  • remix-reorder.createReorder.Group (cognitive 37) packages/framer-motion/src/remix-reorder.ts:117 — remix-reorder.createReorder.Group has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 8 (13 pts), boolean chains 10 (nesting depth added 7). None of this is in the body itself: all 37 points belong to 13 function items inside it that branch (a function literal at line 193, a function literal at line 256, a function literal at line 273, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · visual-element-target.animateTarget (cognitive 36) · ×1
  • visual-element-target.animateTarget (cognitive 36) packages/motion-dom/src/animation/interfaces/visual-element-target.ts:34 — visual-element-target.animateTarget has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 8, ternaries 2 (4 pts), loops 1 (nesting depth added 13). Of this number, 35 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectionNode.applyProjectionStyles (cognitive 36) · ×1
  • ProjectionNode.applyProjectionStyles (cognitive 36) packages/motion-dom/src/projection/node/create-projection-node.ts:2116 — ProjectionNode.applyProjectionStyles has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 9, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · index.AnimatePresence (cognitive 35) · ×1
  • index.AnimatePresence (cognitive 35) packages/framer-motion/src/components/AnimatePresence/index.tsx:46 — index.AnimatePresence has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 7, ternaries 4, loops 2 (3 pts) (nesting depth added 7). Most of this is not in the body itself: 14 of the 35 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 118, 210, 219, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ProjectionNode.resolveTargetDelta (cognitive 31) · ×1
  • ProjectionNode.resolveTargetDelta (cognitive 31) packages/motion-dom/src/projection/node/create-projection-node.ts:1351 — ProjectionNode.resolveTargetDelta has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 13 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · DOMKeyframesResolver.readKeyframes (cognitive 30) · ×1
  • DOMKeyframesResolver.readKeyframes (cognitive 30) packages/motion-dom/src/animation/keyframes/DOMKeyframesResolver.ts:72 — DOMKeyframesResolver.readKeyframes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · size-scenarios.main (cognitive 29) · ×1
  • size-scenarios.main (cognitive 29) dev/inc/size-scenarios.mjs:413 — size-scenarios.main has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 8 (14 pts), if/else 7 (10 pts), loops 3 (5 pts) (nesting depth added 11). Of this number, 28 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · auto-scroll.autoScrollIfNeeded (cognitive 29) · ×1
  • auto-scroll.autoScrollIfNeeded (cognitive 29) packages/framer-motion/src/components/Reorder/utils/auto-scroll.ts:102 — auto-scroll.autoScrollIfNeeded has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 3 (8 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transform.buildProjectionTransform (cognitive 28) · ×1
  • transform.buildProjectionTransform (cognitive 28) packages/motion-dom/src/projection/styles/transform.ts:5 — transform.buildProjectionTransform has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 9, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · keyframes.keyframes (cognitive 27) · ×1
  • keyframes.keyframes (cognitive 27) packages/motion-dom/src/animation/generators/keyframes.ts:26 — keyframes.keyframes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 8, ternaries 6 (8 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VisualElementDragControls.start (cognitive 27) · ×1
  • VisualElementDragControls.start (cognitive 27) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:158 — VisualElementDragControls.start has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 9 (nesting depth added 3). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 5 function items inside it that branch (onMove, onStart, a function literal at line 200, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ProjectionNode.calcProjection (cognitive 26) · ×1
  • ProjectionNode.calcProjection (cognitive 26) packages/motion-dom/src/projection/node/create-projection-node.ts:1556 — ProjectionNode.calcProjection has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 12 (13 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · size-scenarios.check (cognitive 25) · ×1
  • size-scenarios.check (cognitive 25) dev/inc/size-scenarios.mjs:360 — size-scenarios.check has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 5 (10 pts), boolean chains 2, loops 2 (nesting depth added 8). Of this number, 23 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remix.makeLatestValues (cognitive 25) · ×1
  • remix.makeLatestValues (cognitive 25) packages/framer-motion/src/remix.ts:443 — remix.makeLatestValues has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (4 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Item.ReorderItemComponent (cognitive 23) · ×1
  • Item.ReorderItemComponent (cognitive 23) packages/framer-motion/src/components/Reorder/Item.tsx:64 — Item.ReorderItemComponent has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 10, loops 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 180, a function literal at line 116, grab, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · spring.springGenerator (cognitive 23) · ×1
  • spring.springGenerator (cognitive 23) packages/motion-dom/src/animation/generators/spring.ts:272 — spring.springGenerator has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts), ternaries 5 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 478, setRestThresholds, a function literal at line 466, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · animate-view-layers.animateViewLayers (cognitive 22) · ×1
  • animate-view-layers.animateViewLayers (cognitive 22) packages/framer-motion/src/components/AnimateView/animate-view-layers.ts:22 — animate-view-layers.animateViewLayers has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, ternaries 1 (3 pts), loops 1 (nesting depth added 7). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · subject.animateSubject (cognitive 21) · ×1
  • subject.animateSubject (cognitive 21) packages/framer-motion/src/animation/animate/subject.ts:75 — subject.animateSubject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Timeline.build (cognitive 21) · ×1
  • Timeline.build (cognitive 21) packages/framer-motion/src/animation/timeline/index.ts:478 — Timeline.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, ternaries 2 (nesting depth added 3). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · use-visual-element.useVisualElement (cognitive 21) · ×1
  • use-visual-element.useVisualElement (cognitive 21) packages/framer-motion/src/motion/utils/use-visual-element.ts:22 — use-visual-element.useVisualElement has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 10 (nesting depth added 1). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 177, 148, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · motion-value.animateMotionValue.<returned closure> (cognitive 21) · ×1
  • motion-value.animateMotionValue.<returned closure> (cognitive 21) packages/motion-dom/src/animation/interfaces/motion-value.ts:28 — motion-value.animateMotionValue.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), ternaries 3 (nesting depth added 2). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · stagger.stagger.<returned closure> (cognitive 21) · ×1
  • stagger.stagger.<returned closure> (cognitive 21) packages/motion-dom/src/utils/stagger.ts:42 — stagger.stagger.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 4 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · motion-values.updateMotionValuesFromProps (cognitive 21) · ×1
  • motion-values.updateMotionValuesFromProps (cognitive 21) packages/motion-dom/src/render/utils/motion-values.ts:10 — motion-values.updateMotionValuesFromProps has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 1 (4 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · effects.animateValues (cognitive 20) · ×1
  • effects.animateValues (cognitive 20) packages/motion-dom/src/animation/animate/effects.ts:65 — effects.animateValues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mix-values.mixValues (cognitive 20) · ×1
  • mix-values.mixValues (cognitive 20) packages/motion-dom/src/projection/animation/mix-values.ts:20 — mix-values.mixValues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectionNode.addLayoutListener (cognitive 20) · ×1
  • ProjectionNode.addLayoutListener (cognitive 20) packages/motion-dom/src/projection/node/create-projection-node.ts:636 — ProjectionNode.addLayoutListener has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (10 pts) (nesting depth added 3). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 651). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · ExitAnimationFeature.update (cognitive 19) · ×1
  • ExitAnimationFeature.update (cognitive 19) packages/framer-motion/src/motion/features/animation/exit.ts:13 — ExitAnimationFeature.update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 7). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · check-reorder.checkReorder (cognitive 19) · ×1
  • check-reorder.checkReorder (cognitive 19) packages/framer-motion/src/components/Reorder/utils/check-reorder.ts:5 — check-reorder.checkReorder has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (5 pts), boolean chains 3 (nesting depth added 5). Of this number, 13 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.scopeMotion (cognitive 19) · ×1
  • index.scopeMotion (cognitive 19) packages/motion-dom/src/scope/index.ts:109 — index.scopeMotion has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, loops 4 (5 pts), ternaries 3 (4 pts), if/else 3 (nesting depth added 2). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (start, clear, a function literal at line 128, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · VisualElement.mount (cognitive 19) · ×1
  • VisualElement.mount (cognitive 19) packages/motion-dom/src/render/VisualElement.ts:449 — VisualElement.mount has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JSAnimation.generate (cognitive 19) · ×1
  • JSAnimation.generate (cognitive 19) packages/motion-dom/src/animation/JSAnimation.ts:333 — JSAnimation.generate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransformAnimation.tween (cognitive 19) · ×1
  • TransformAnimation.tween (cognitive 19) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:444 — TransformAnimation.tween has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (7 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LayoutAnimationBuilder.flushPendingBuilders (cognitive 18) · ×1
  • LayoutAnimationBuilder.flushPendingBuilders (cognitive 18) packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:192 — LayoutAnimationBuilder.flushPendingBuilders has cognitive complexity 18 (threshold 15). Drivers by points: loops 9 (11 pts), ternaries 2 (4 pts), if/else 2 (3 pts) (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Board.createBoard.drag (cognitive 17) · ×1
  • Board.createBoard.drag (cognitive 17) packages/framer-motion/src/components/Reorder/Board.tsx:199 — Board.createBoard.drag has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · attach-animation.attachToAnimation (cognitive 17) · ×1
  • attach-animation.attachToAnimation (cognitive 17) packages/framer-motion/src/render/dom/scroll/attach-animation.ts:8 — attach-animation.attachToAnimation has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 3 (5 pts), boolean chains 4 (nesting depth added 4). Of this number, 10 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.addStyleValue (cognitive 17) · ×1
  • index.addStyleValue (cognitive 17) packages/motion-dom/src/effects/style/index.ts:26 — index.addStyleValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · delta-apply.applyTreeDeltas (cognitive 17) · ×1
  • delta-apply.applyTreeDeltas (cognitive 17) packages/motion-dom/src/projection/geometry/delta-apply.ts:81 — delta-apply.applyTreeDeltas has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeStack.promote (cognitive 17) · ×1
  • NodeStack.promote (cognitive 17) packages/motion-dom/src/projection/shared/stack.ts:45 — NodeStack.promote has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JSAnimation.tick (cognitive 17) · ×1
  • JSAnimation.tick (cognitive 17) packages/motion-dom/src/animation/JSAnimation.ts:205 — JSAnimation.tick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · index.createScopedAnimate.scopedAnimate (cognitive 16) · ×1
  • index.createScopedAnimate.scopedAnimate (cognitive 16) packages/framer-motion/src/animation/animate/index.ts:93 — index.createScopedAnimate.scopedAnimate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 5, ternaries 2 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PopChild.PopChild (cognitive 16) · ×1
  • PopChild.PopChild (cognitive 16) packages/framer-motion/src/components/AnimatePresence/PopChild.tsx:123 — PopChild.PopChild has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 4, if/else 4 (nesting depth added 2). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (insertPopRule, a function literal at line 181, a function literal at line 222, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ProjectionNode.willUpdate (cognitive 16) · ×1
  • ProjectionNode.willUpdate (cognitive 16) packages/motion-dom/src/projection/node/create-projection-node.ts:791 — ProjectionNode.willUpdate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/motion-dom/src/projection/node/create-projection-node.ts holds 7 of the 58 methods over the threshold — including the worst — and 344 of the 1025 points over it (34%), 2.6× the next-largest file (packages/motion-dom/src/view/start.ts at 131). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · index.press · ×1
  • index.press::startPress (cognitive 16) packages/motion-dom/src/gestures/press/index.ts:103 — index.press::startPress has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · VisualElementDragControls.resolveConstraints (cognitive 16) · ×1
  • VisualElementDragControls.resolveConstraints (cognitive 16) packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:411 — VisualElementDragControls.resolveConstraints has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: TransformAnimation (LCOM4 6) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:319 — TransformAnimation's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 706 JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (9 clone groups) packages/motion-dom/rollup.config.mjs:1 — 9 duplicated blocks under packages/ have copies in at least two of the sibling directories framer-motion, motion, motion-dom, motion-utils — 8 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (78 identical lines × 2 files) · ×1
  • Wholesale file copy (78 identical lines × 2 files) packages/motion-dom/rollup.config.mjs:1 — packages/motion-dom/rollup.config.mjs:1 · packages/motion-utils/rollup.config.mjs:1 — these 2 files are line-for-line copies of one another — 78 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) dev/react-19/src/App.tsx:10 — dev/react-19/src/App.tsx:10 · dev/react/src/App.tsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (40 lines × 2 locations) · ×1
  • Duplicated block (40 lines × 2 locations) dev/html/src/three-animate.js:56 — dev/html/src/three-animate.js:56 · dev/html/src/three-tsl.js:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×1
  • Duplicated block (37 lines × 2 locations) dev/html/src/imports/script-animate.js:11 — dev/html/src/imports/script-animate.js:11 · dev/html/src/imports/script-undo.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (30 lines × 3 locations) · ×1
  • Duplicated block (30 lines × 3 locations) packages/framer-motion/rollup.config.mjs:155 — packages/framer-motion/rollup.config.mjs:155 · packages/motion-dom/rollup.config.mjs:102 · packages/motion-utils/rollup.config.mjs:99 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (29 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (29 matched lines × 2 locations) packages/framer-motion/src/components/Reorder/Group.tsx:185 — packages/framer-motion/src/components/Reorder/Group.tsx:185 · packages/framer-motion/src/remix-reorder.ts:185 — the two spans are one implementation copied and then locally edited — 151 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) dev/html/src/three-animate.js:108 — dev/html/src/three-animate.js:108 · dev/html/src/three-tsl.js:114 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) packages/framer-motion/rollup.config.mjs:93 — packages/framer-motion/rollup.config.mjs:93 · packages/motion/rollup.config.mjs:83 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (18 lines × 3 locations) · ×1
  • Duplicated block (18 lines × 3 locations) packages/framer-motion/rollup.config.mjs:125 — packages/framer-motion/rollup.config.mjs:125 · packages/motion-dom/rollup.config.mjs:81 · packages/motion-utils/rollup.config.mjs:78 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) dev/html/src/three-animate.js:116 — dev/html/src/three-animate.js:116 · dev/html/src/three-effects.js:109 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (15 lines × 3 locations) · ×1
  • Duplicated block (15 lines × 3 locations) packages/framer-motion/rollup.config.mjs:76 — packages/framer-motion/rollup.config.mjs:76 · packages/framer-motion/rollup.config.mjs:96 · packages/motion/rollup.config.mjs:86 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) packages/motion-dom/src/projection/geometry/delta-calc.ts:62 — packages/motion-dom/src/projection/geometry/delta-calc.ts:62 · packages/motion-dom/src/projection/geometry/delta-calc.ts:85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) packages/motion/src/three.ts:42 — packages/motion/src/three.ts:42 · packages/motion/src/vgpu.ts:83 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 41 locations) · ×1
  • Duplicated block (8 lines × 41 locations) packages/framer-motion/src/render/components/m/elements.ts:8 — packages/framer-motion/src/render/components/m/elements.ts:8 · packages/framer-motion/src/render/components/m/elements.ts:18 · packages/framer-motion/src/render/components/m/elements.ts:28 · packages/framer-motion/src/render/components/m/elements.ts:38 · +37 more site(s) not listed — the 41 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (7 matched lines × 2 locations) packages/motion-dom/src/projection/node/create-projection-node.ts:1351 — packages/motion-dom/src/projection/node/create-projection-node.ts:1351 · packages/motion-dom/src/projection/node/create-projection-node.ts:1556 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1
  • Duplicated block (6 lines × 2 locations) dev/html/src/three-animate.js:6 — dev/html/src/three-animate.js:6 · dev/html/src/three-xr.js:7 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (5 matched lines × 2 locations) packages/framer-motion/src/value/use-combine-values.ts:35 — packages/framer-motion/src/value/use-combine-values.ts:35 · packages/motion-dom/src/value/subscribe-value.ts:10 — the two spans are one implementation copied and then locally edited — 52 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.
R2 · Cyclomatic Complexity · Complex function scheduleUpdate (cyclomatic 136, cognitive 140) · ×1
  • Complex function scheduleUpdate (cyclomatic 136, cognitive 140) packages/motion-dom/src/projection/node/create-projection-node.ts:962 — scheduleUpdate has cyclomatic complexity 136 and cognitive complexity 140; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function createProjectionNode (cyclomatic 103, cognitive 129) · ×1
  • Complex function createProjectionNode (cyclomatic 103, cognitive 129) packages/motion-dom/src/projection/node/create-projection-node.ts:173 — createProjectionNode has cyclomatic complexity 103 and cognitive complexity 129; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 53, cognitive 56) · ×1
  • Complex function (anonymous) (cyclomatic 53, cognitive 56) packages/motion-dom/src/render/utils/animation-state.ts:133 — (anonymous) has cyclomatic complexity 53 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 35, cognitive 49) · ×1
  • Complex function (anonymous) (cyclomatic 35, cognitive 49) packages/framer-motion/src/remix.ts:1055 — (anonymous) has cyclomatic complexity 35 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function retime (cyclomatic 34, cognitive 46) · ×1
  • Complex function retime (cyclomatic 34, cognitive 46) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1277 — retime has cyclomatic complexity 34 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveValueSequence (cyclomatic 32, cognitive 49) · ×1
  • Complex function resolveValueSequence (cyclomatic 32, cognitive 49) packages/framer-motion/src/animation/sequence/create.ts:127 — resolveValueSequence has cyclomatic complexity 32 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 30, cognitive 64) · ×1
  • Complex function (anonymous) (cyclomatic 30, cognitive 64) packages/motion-dom/src/view/start.ts:506 — (anonymous) has cyclomatic complexity 30 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function animateTarget (cyclomatic 29, cognitive 38) · ×1
  • Complex function animateTarget (cyclomatic 29, cognitive 38) packages/motion-dom/src/animation/interfaces/visual-element-target.ts:34 — animateTarget has cyclomatic complexity 29 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKeyDown (cyclomatic 28, cognitive 30) · ×1
  • Complex function onKeyDown (cyclomatic 28, cognitive 30) packages/framer-motion/src/components/Reorder/Group.tsx:198 — onKeyDown has cyclomatic complexity 28 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 27, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 27, cognitive 47) packages/motion-dom/src/view/start.ts:492 — (anonymous) has cyclomatic complexity 27 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function makeLatestValues (cyclomatic 22, cognitive 44) · ×1
  • Complex function makeLatestValues (cyclomatic 22, cognitive 44) packages/framer-motion/src/motion/utils/use-visual-state.ts:60 — makeLatestValues has cyclomatic complexity 22 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function autoScrollIfNeeded (cyclomatic 22, cognitive 34) · ×1
  • Complex function autoScrollIfNeeded (cyclomatic 22, cognitive 34) packages/framer-motion/src/components/Reorder/utils/auto-scroll.ts:102 — autoScrollIfNeeded has cyclomatic complexity 22 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildProjectionTransform (cyclomatic 22, cognitive 28) · ×1
  • Complex function buildProjectionTransform (cyclomatic 22, cognitive 28) packages/motion-dom/src/projection/styles/transform.ts:5 — buildProjectionTransform has cyclomatic complexity 22 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 19) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 19) packages/motion-dom/src/animation/interfaces/motion-value.ts:28 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function notifyLayoutUpdate (cyclomatic 21, cognitive 38) · ×1
  • Complex function notifyLayoutUpdate (cyclomatic 21, cognitive 38) packages/motion-dom/src/projection/node/create-projection-node.ts:2299 — notifyLayoutUpdate has cyclomatic complexity 21 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function analyze (cyclomatic 21, cognitive 21) · ×1
  • Complex function analyze (cyclomatic 21, cognitive 21) dev/react/src/tests/start-transition-helpers.ts:247 — analyze has cyclomatic complexity 21 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mixTargetDelta (cyclomatic 21, cognitive 17) · ×1
  • Complex function mixTargetDelta (cyclomatic 21, cognitive 17) packages/motion-dom/src/projection/node/create-projection-node.ts:1752 — mixTargetDelta has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function animate (cyclomatic 20, cognitive 36) · ×1
  • Complex function animate (cyclomatic 20, cognitive 36) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1106 — animate has cyclomatic complexity 20 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function makeLatestValues (cyclomatic 20, cognitive 29) · ×1
  • Complex function makeLatestValues (cyclomatic 20, cognitive 29) packages/framer-motion/src/remix.ts:443 — makeLatestValues has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 20, cognitive 28) · ×1
  • Complex function main (cyclomatic 20, cognitive 28) dev/inc/size-scenarios.mjs:413 — main has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/motion-dom/src/projection/node/create-projection-node.ts · ×1
  • packages/motion-dom/src/projection/node/create-projection-node.ts: 2260 lines of code packages/motion-dom/src/projection/node/create-projection-node.ts:1 — packages/motion-dom/src/projection/node/create-projection-node.ts has 2260 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts · ×1
  • packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts: 1375 lines of code packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1 — packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/framer-motion/src/remix.ts · ×1
  • packages/framer-motion/src/remix.ts: 1226 lines of code packages/framer-motion/src/remix.ts:1 — packages/framer-motion/src/remix.ts has 1226 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/node/types.ts · ×1
  • packages/motion-dom/src/node/types.ts: 1050 lines of code packages/motion-dom/src/node/types.ts:1 — packages/motion-dom/src/node/types.ts has 1050 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/view/start.ts · ×1
  • packages/motion-dom/src/view/start.ts: 851 lines of code packages/motion-dom/src/view/start.ts:1 — packages/motion-dom/src/view/start.ts has 851 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts · ×1
  • packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts: 832 lines of code packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts:1 — packages/motion-dom/src/gestures/drag/VisualElementDragControls.ts has 832 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/render/VisualElement.ts · ×1
  • packages/motion-dom/src/render/VisualElement.ts: 819 lines of code packages/motion-dom/src/render/VisualElement.ts:1 — packages/motion-dom/src/render/VisualElement.ts has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/animation/types.ts · ×1
  • packages/motion-dom/src/animation/types.ts: 724 lines of code packages/motion-dom/src/animation/types.ts:1 — packages/motion-dom/src/animation/types.ts has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/framer-motion/src/animation/timeline/index.ts · ×1
  • packages/framer-motion/src/animation/timeline/index.ts: 683 lines of code packages/framer-motion/src/animation/timeline/index.ts:1 — packages/framer-motion/src/animation/timeline/index.ts has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/animation/JSAnimation.ts · ×1
  • packages/motion-dom/src/animation/JSAnimation.ts: 503 lines of code packages/motion-dom/src/animation/JSAnimation.ts:1 — packages/motion-dom/src/animation/JSAnimation.ts has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/value/index.ts · ×1
  • packages/motion-dom/src/value/index.ts: 497 lines of code packages/motion-dom/src/value/index.ts:1 — packages/motion-dom/src/value/index.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · dev/inc/size-scenarios.mjs · ×1
  • dev/inc/size-scenarios.mjs: 480 lines of code dev/inc/size-scenarios.mjs:1 — dev/inc/size-scenarios.mjs has 480 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/framer-motion/src/animation/sequence/create.ts · ×1
  • packages/framer-motion/src/animation/sequence/create.ts: 479 lines of code packages/framer-motion/src/animation/sequence/create.ts:1 — packages/framer-motion/src/animation/sequence/create.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/animation/generators/spring.ts · ×1
  • packages/motion-dom/src/animation/generators/spring.ts: 470 lines of code packages/motion-dom/src/animation/generators/spring.ts:1 — packages/motion-dom/src/animation/generators/spring.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/framer-motion/src/remix-reorder.ts · ×1
  • packages/framer-motion/src/remix-reorder.ts: 467 lines of code packages/framer-motion/src/remix-reorder.ts:1 — packages/framer-motion/src/remix-reorder.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/framer-motion/src/components/Reorder/Board.tsx · ×1
  • packages/framer-motion/src/components/Reorder/Board.tsx: 435 lines of code packages/framer-motion/src/components/Reorder/Board.tsx:1 — packages/framer-motion/src/components/Reorder/Board.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/motion-dom/src/render/utils/animation-state.ts · ×1
  • packages/motion-dom/src/render/utils/animation-state.ts: 403 lines of code packages/motion-dom/src/render/utils/animation-state.ts:1 — packages/motion-dom/src/render/utils/animation-state.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~1365 LoC) · ×1
  • Dead file (~1365 LoC) packages/framer-motion/src/remix.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/remix-reorder.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~507 LoC) · ×1
  • Dead file (~507 LoC) packages/framer-motion/src/remix-reorder.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/remix.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~166 LoC) · ×1
  • Dead file (~166 LoC) packages/framer-motion/src/client.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~100 LoC) · ×1
  • Dead file (~100 LoC) dev/html/src/imports/script-animate.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~91 LoC) · ×1
  • Dead file (~91 LoC) dev/html/src/imports/script-undo.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~77 LoC) · ×1
  • Dead file (~77 LoC) packages/framer-motion/src/components/AnimateView/index.tsx — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/framer-motion/src/animate-view.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~20 LoC) · ×1
  • Dead file (~20 LoC) packages/framer-motion/src/render/dom/use-motion-value-child.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~16 LoC) · ×1
  • Dead file (~16 LoC) packages/motion/src/react.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~14 LoC) · ×1
  • Dead file (~14 LoC) packages/framer-motion/src/utils/safe-react-types.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~11 LoC) · ×1
  • Dead file (~11 LoC) dev/html/src/imports/optimized-appear.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~9 LoC) · ×1
  • Dead file (~9 LoC) packages/framer-motion/src/animate-view.ts — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~5 LoC) · ×1
  • Dead file (~5 LoC) dev/html/src/inc.js — no import path from any entry point (107 application, 19 tooling, 774 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency 'convert-tsconfig-paths-to-webpack-aliases' · ×1
  • Unused dependency 'convert-tsconfig-paths-to-webpack-aliases' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'path-browserify' · ×1
  • Unused dependency 'path-browserify' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'react-dev-utils' · ×1
  • Unused dependency 'react-dev-utils' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap packages/framer-motion/src/animation/sequence/create.ts:102 — `createAnimationsFromSequence` is exported, takes a document from its caller (line 45) and hands it to `resolveSequence`, which calls itself at line 102 (`resolveSequence`) with a piece of `sequence` — and nowhere in `resolveSequence` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveSequence` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: notifySlack scripts/notify-slack.js:61 — `notifySlack` 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 })`.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts:1258 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Minor — 164 finding(s)
D12 · Dependency Hygiene · Deprecated · ×91
  • Deprecated: @base-ui-components/utils REDACTED:490 — @base-ui-components/utils 0.2.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package was renamed to @base-ui/utils". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/add REDACTED:1450 — @lerna/add 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/bootstrap REDACTED:1468 — @lerna/bootstrap 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/changed REDACTED:1498 — @lerna/changed 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/check-working-tree REDACTED:1510 — @lerna/check-working-tree 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/clean REDACTED:1532 — @lerna/clean 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/cli REDACTED:1548 — @lerna/cli 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/collect-uncommitted REDACTED:1560 — @lerna/collect-uncommitted 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/collect-updates REDACTED:1571 — @lerna/collect-updates 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/command REDACTED:1584 — @lerna/command 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/conventional-commits REDACTED:1602 — @lerna/conventional-commits 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/create-symlink REDACTED:1621 — @lerna/create-symlink 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/create REDACTED:1632 — @lerna/create 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is an implementation detail of Lerna and is no longer published separately.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/describe-ref REDACTED:1658 — @lerna/describe-ref 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/diff REDACTED:1668 — @lerna/diff 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/exec REDACTED:1680 — @lerna/exec 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/filter-options REDACTED:1695 — @lerna/filter-options 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/filter-packages REDACTED:1707 — @lerna/filter-packages 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/get-npm-exec-opts REDACTED:1718 — @lerna/get-npm-exec-opts 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/get-packed REDACTED:1727 — @lerna/get-packed 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/github-client REDACTED:1738 — @lerna/github-client 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/gitlab-client REDACTED:1751 — @lerna/gitlab-client 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/global-options REDACTED:1762 — @lerna/global-options 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/has-npm-version REDACTED:1769 — @lerna/has-npm-version 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/import REDACTED:1779 — @lerna/import 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 66 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×33
  • Disabled test packages/framer-motion/cypress/integration/layout-shared.ts:215 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/cypress/integration/layout-shared.ts:257 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/cypress/integration/scroll.ts:310 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/cypress/integration/waapi.ts:70 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/cypress/integration/while-in-view.ts:131 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/animation/animators/waapi/__tests__/css-variables.test.tsx:144 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:461 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:497 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:967 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/gestures/drag/__tests__/index.test.tsx:1082 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/motion/__tests__/waapi.test.tsx:258 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/framer-motion/src/motion/__tests__/waapi.test.tsx:295 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/motion-dom/src/projection/node/__tests__/group.test.ts:5 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/motion-dom/src/render/dom/__tests__/parse-transform.test.ts:232 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/motion-dom/src/render/dom/__tests__/parse-transform.test.ts:243 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/animate/view.spec.ts:7 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/gestures/drag-basic.spec.ts:313 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/gestures/hover.spec.ts:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/gestures/press.spec.ts:15 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/animate-view.spec.ts:22 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/issue-3769-activity.spec.ts:16 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/issue-3942-activity.spec.ts:15 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/scroll-accelerate-partial-range.spec.ts:40 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/scroll-view-timeline-parity.spec.ts:113 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/react/scroll-view-timeline-parity.spec.ts:141 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 8 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×8
  • Mock-dominated test: fires lifecycle callbacks packages/motion-dom/src/gestures/drag/__tests__/drag.test.ts:98 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: press event listeners fire via keyboard packages/framer-motion/src/gestures/__tests__/press.test.tsx:70 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: press cancel event listeners fire via keyboard packages/framer-motion/src/gestures/__tests__/press.test.tsx:101 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: press cancel event listeners not fired via keyboard after keyUp packages/framer-motion/src/gestures/__tests__/press.test.tsx:132 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: propagate={{ tap: false }} prevents all ancestor onTap handlers (three levels) packages/framer-motion/src/gestures/__tests__/press.test.tsx:869 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: creates custom keyframes once even when several browser layers match packages/framer-motion/src/components/AnimateView/__tests__/animate-view-layers.test.ts:30 — This test sets up 4 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: keeps the group morph running when custom values replace the crossfade packages/framer-motion/src/components/AnimateView/__tests__/animate-view-layers.test.ts:62 — This test sets up 4 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: does not report completion after React cleans up an interrupted transition packages/framer-motion/src/components/AnimateView/__tests__/animate-view-layers.test.ts:96 — This test sets up 3 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
IC1 · Incompleteness & stubs · Empty method body · ×7
  • Empty method body packages/framer-motion/src/jest.setup.tsx:28 — `observe` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/framer-motion/src/jest.setup.tsx:29 — `unobserve` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/framer-motion/src/jest.setup.tsx:30 — `disconnect` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:280 — `notifyReady` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/motion-dom/src/layout/LayoutAnimationBuilder.ts:281 — `rejectReady` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/motion-utils/src/errors.ts:9 — `warning` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/motion-utils/src/errors.ts:10 — `invariant` has an empty body — confirm it's an intentional no-op and not an unfinished method.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate packages/framer-motion/src/components/Reorder/Group.tsx:201 — `event.defaultPrevented || event.target !== currentTarget || event.altKey || event.ctrlKey || event.metaKey` appears character-identically in 2 files — packages/framer-motion/src/components/Reorder/Group.tsx, packages/framer-motion/src/remix-reorder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/motion-dom/src/effects/prop/index.ts:33 — `typeof value === "string" || typeof value === "number"` appears character-identically in 3 files — packages/motion-dom/src/effects/prop/index.ts, packages/motion-dom/src/render/object/ObjectVisualElement.ts, packages/motion/src/three.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/framer-motion/src/components/Reorder/Group.tsx:132 — `valuesSet.has(value) || map.delete(value)` appears character-identically in 2 files — packages/framer-motion/src/components/Reorder/Group.tsx, packages/framer-motion/src/remix-reorder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D24 · Comment Value · redundant comment · ×2
  • redundant comment packages/motion-dom/src/projection/node/create-projection-node.ts:686 — "|| hasRelativeLayoutChanged" repeats the code it sits on: 3 of its 3 words (relative, layout, changed) are already in `const hasOnlyRelativeTargetChanged =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment scripts/generate-changelog.js:190 — "Write CSV file" repeats the code it sits on: 3 of its 3 words (write, csv, file) are already in `fs.writeFileSync(csvPath, csvContent, "utf8")`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×2
  • REDACTED
  • REDACTED
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IProjectionNode (44 required operations) packages/motion-dom/src/projection/node/types.ts:40 — `IProjectionNode` declares 44 required operations: `mount`, `unmount`, `setOptions`, `isUpdateBlocked`, `blockUpdate`, `unblockUpdate`, `startUpdate`, `willUpdate`, `didUpdate`, `measure`, `measurePageBox`, `updateLayout`, `updateSnapshot`, `clearSnapshot`, `updateScroll`, `scheduleUpdateProjection`, `scheduleCheckAfterUnmount`, `checkUpdateFailed`, `registerSharedNode`, `getStack`, `hide`, `show`, `scheduleRender`, `getClosestProjectingParent`, `setTargetDelta`, `resetTransform`, `resetSkewAndRotation`, `applyTransform`, `resolveTargetDelta`, `removeRelativeTarget`, `calcProjection`, `applyProjectionStyles`, `clearMeasurements`, `resetTree`, `isProjecting`, `setAnimationOrigin`, `startAnimation`, `finishAnimation`, `isLead`, `promote`, and 4 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D21 · Naming Consistency · `createSvgRenderState` spells `Svg` where 21 names in the project spell it `SVG` · ×1
  • `createSvgRenderState` spells `Svg` where 21 names in the project spell it `SVG` packages/framer-motion/src/render/svg/utils/create-render-state.ts:4 — 21 of 22 names in project motion-one spell the token `SVG` (21 of 22; unit: names in project motion-one containing `SVG`). Peers: packages.framer-motion.src.motion.types.MotionSVGProps (packages/framer-motion/src/motion/types.ts:55); use-visual-element.useVisualElement(isSVG) (packages/framer-motion/src/motion/utils/use-visual-element.ts:22); remix.isSVGElement (packages/framer-motion/src/remix.ts:435); remix.makeLatestValues(isSVG) (packages/framer-motion/src/remix.ts:443); remix.renderValues(isSVG) (packages/framer-motion/src/remix.ts:517). Rename to `createSVGRenderState`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 10 project(s) overshoot their size bounds, lowering Project Cohesion to 4.1/10. The most over is `packages/motion-dom` (22917 LoC, 390 module-visible types across 67 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6334 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:30 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
R7 · Dead Code · Unused export 'AnimationSubject' · ×1
  • Unused export 'AnimationSubject' packages/framer-motion/src/animation/animate/subject.ts:26 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'pointerCancel' · ×1
  • Unused export 'pointerCancel' packages/framer-motion/src/jest.setup.tsx:86 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'MotionComponentConfig' · ×1
  • Unused export 'MotionComponentConfig' packages/framer-motion/src/motion/index.tsx:29 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'CustomDomComponent' · ×1
  • Unused export 'CustomDomComponent' packages/framer-motion/src/render/components/create-proxy.ts:15 — Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/1 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.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 11/12 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~4.9 `!` null assertions per 1k TypeScript source lines — 213 assertion(s) across the 43487 source line(s) of the 527 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/motion-dom/src/projection/node/create-projection-node.ts (36), packages/motion-dom/src/animation/waapi/transforms/TransformAnimation.ts (20), packages/framer-motion/src/components/Reorder/Board.tsx (16). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 4 finding(s)
D24 · Comment Value · doc comments repeat the names · ×3
  • doc comments repeat the names packages/framer-motion/src/animation/animate/index.ts:83 — 1 of 27 documented parameters and 2 of 451 summaries in `framer-motion` only repeat the member or parameter name (e.g. "Animate an object" for `scopedAnimate`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/motion-dom/src/projection/node/create-projection-node.ts:1747 — 0 of 57 documented parameters and 2 of 816 summaries in `motion-dom` only repeat the member or parameter name (e.g. "Animation" for `animationValues`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names dev/react/src/tests/pop-layout-playground.tsx:297 — 0 of 0 documented parameters and 2 of 172 summaries in `react-env` only repeat the member or parameter name (e.g. "Ghosts" for `Ghost`). Delete the restating tags, or add what the name does not say.
D12 · Dependency Hygiene · Dependency hygiene PARTLY measured · ×1
  • Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (registry.npmjs.org unreachable) — This repository's npm dependencies were read for PINNING discipline: 29 production declaration(s) plus 79 development one(s) across 10 package.json (10 of them the product — the rest are example, documentation or fixture manifests, which are read and counted but screened off the rules below, because both prescribe a MOVE and "align your example apps" is not a remedy), against 1 committed lockfile(s). 2 pinning defect(s) are reported as separate rows below. That is only PART of dependency hygiene, so this dimension is NOT SCORED: whether any of these packages has a newer, deprecated or abandoned release is the dependency-CURRENCY question, and answering it needs registry.npmjs.org — which could not be reached on this run (3 of 13 lookup(s) went unanswered; first failure: registry returned 429), so the currency half was not established. This row abstains rather than reporting an unchecked dependency set as clean; a scan with egress to registry.npmjs.org scores it. A clean pinning pass is NOT an all-clear for these dependencies, and it is not a finding that they are all USED. Note also what is deliberately NOT charged here: a workspace legitimately carries ONE lockfile for many manifests, so no row is raised off the lockfile count, only reported. Known CVEs in the same dependency graph are a separate question again, reported under D30 wherever the manifest is OSV-readable.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fbbce2ab4b6e49258c018d02a63e9a98/history.json --exit-code 0 --source .1artifacts/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-fbbce2ab4b6e49258c018d02a63e9a98/tree.json --exit-code 0 --source .0artifacts/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 .13artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update40artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .2artifacts/raw/trivy-config.json
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 11 file(s) — `packages/framer-motion/rollup.config.mjs`, `packages/framer-motion/src/debug.ts`, `packages/framer-motion/src/index.ts`, `packages/motion-dom/rollup.config.mjs`, `packages/motion-dom/src/animation/NativeAnimation.ts`, … (+6 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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1b727-0ddd-7b9b-b67d-53c130bf06ec · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md