ueberdosis/tiptap

Choose this fork only if you specifically need its Vue-oriented snapshot and are willing to own divergence. For most adopters, upstream Tiptap is the safer choice because this fork is stale and significantly behind.

Prefer this fork only if you specifically need its older collaboration/demo-oriented snapshot and accept long-term maintenance debt. For most adopters, upstream is the better choice because it is much more current, actively maintained, and likely to have fewer missing fixes and features.

Prefer this fork only if you are already committed to its old Vue-specific integration. For new work, upstream Tiptap is the better choice because this fork is heavily stale and far behind on features, maintenance, and ecosystem breadth.

Prefer upstream unless you specifically need this older Vue-centric branch or must preserve fork-specific behavior. The fork looks stale and materially diverged, so it is best suited for legacy maintenance, not new development.

Choose this fork only if you need its older hashtag-focused customization and are willing to own long-term maintenance. For most teams, upstream is the safer choice because this fork is deeply stale and materially behind on fixes and platform updates.

Choose this fork only if you want a lightly managed internal branch and are willing to catch up to upstream yourself; otherwise upstream is the better default because this fork currently shows no added capabilities and is significantly behind.

Choose this fork only if you need the legacy baseline or already rely on fork-specific changes. For new work, upstream is the better default because this fork is materially stale and likely missing many important fixes and capabilities.

Prefer this fork only if you explicitly need its older snapshot and the small set of local behavior changes. For new work or active maintenance, upstream is the better choice because this fork is stale and far behind.

Choose this fork only if you need a legacy, customized Tiptap snapshot and are prepared to own the maintenance burden. If you want an actively maintained editor stack or expect to follow upstream, the divergence and staleness make this a poor adoption target.