motiondivision/motion

Prefer this fork only if you need its layout-focused test/demo work or already depend on its older code state. If you want current Motion features and lower maintenance cost, upstream is the better default.

Prefer this fork only if you need its custom 2023-era Motion changes and are willing to maintain a large divergence yourself. If you want a production animation library to adopt today, upstream is the safer choice.

Prefer upstream for almost all new work. Choose this fork only if you need its specific custom animation/layout changes and are willing to own a long-term rebase or porting effort.

Prefer upstream unless you specifically need this fork’s custom layout/projection work or must stay on an older patched branch. For new adoption, the fork is too stale and too far behind upstream to be the safer default.

Prefer this fork only if you already depend on its older React-specific behavior and do not need upstream parity. For new work, or for teams that value active maintenance, platform breadth, and current Motion features, upstream is the better choice.

Choose this fork only if you want the fork-specific MotionCanvas/customization direction and can accept major upstream drift. For most adopters, upstream Motion is the safer choice because this fork is stale, highly divergent, and likely missing many current fixes and workflows.

Prefer upstream unless you specifically need this older snapshot. This fork is best for legacy preservation or highly constrained local experimentation, not for new work or active maintenance.

Prefer upstream unless you explicitly need this older snapshot. This fork does not appear to add capabilities, and its main drawback is lagging behind current Motion work.

Adopt this only if you specifically want a frozen snapshot and are prepared to catch up manually; otherwise upstream is the better choice because this fork shows no added features and is far behind.