Repo brief: motiondivision/motion

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T16:33:39.663Z · commit 1b037b003257

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit today
• 2 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Motion is a unified animation library for React, JavaScript, and Vue that provides GPU-accelerated animations through a hybrid engine combining JavaScript logic with Web Animations API (WAAPI). It replaces Framer Motion with a smaller footprint and production-ready features including gestures, springs, layout transitions, and timeline sequences across multiple platforms. Monorepo structure: packages/motion/ contains the core JavaScript/vanilla export layers (animate, hooks, debug modes), packages/framer-motion/ houses React-specific components (AnimatePresence, LayoutGroup, LazyMotion) and animation system (WAAPI animators, sequence utilities, optimized-appear handoff logic). Entry…

Start here

Open these first:

• packages/framer-motion/src/index.ts — Main entry point exporting all public APIs for the Framer Motion animation library.
• packages/motion/src/index.ts — Main entry point for the Motion library, exposing cross-framework animation APIs.
• packages/framer-motion/src/animation/animate/index.ts — Core animate function orchestrating animation execution across subjects and sequences.
• packages/framer-motion/src/animation/animators/waapi/animate-elements.ts — WAAPI-based element animator implementing low-level DOM animation using Web Animations API.
• packages/framer-motion/src/motion/features/animations.ts — Feature module defining animation capabilities integrated into motion component lifecycle.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository, then run npm install (inferred from TypeScript package structure and Makefile presence). No setup commands can be verified without access to package.json, so consult the repository's root manifes…

Daily commands:

Not determinable from provided data. Verify package.json in repository root for exact dev server commands. Makefile presence suggests make targets may exist; check Makefile for dev/build/test commands.

…shortened for this brief.

Key cautions & unknowns

• Small team — 2 contributors active in recent commits
• Single-maintainer risk — top contributor 90% of recent commits
• The library has multiple entry points (motion/react, motion, motion-v) with different bundle sizes (full, mini, client variants in packages/motion/src/). Ensure you're importing from the correct package for your…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.