Prefer this fork if you want Quill plus framework wrappers, markdown tooling, and a more productized editor surface. Stick with upstream if you want the smallest-maintenance, most standard Quill distribution.
DevExpress/devextreme-quill
active
significant_divergence
Prefer this fork if you are building on DevExtreme HtmlEditor or want DevExpress-specific editor behavior and support. Prefer upstream Quill if you need the broadest compatibility, latest Quill fixes, and easier ecosystem alignment.
voxmedia/quill
stale
significant_divergence
Choose this fork only if you need its older custom editor behavior and are comfortable owning maintenance. If you want current Quill capabilities, browser fixes, and active upstream support, the upstream project is the better base.
Scholar-6/quill
stale
significant_divergence
Choose this fork only if you need a legacy, self-contained Quill snapshot with bundled dist files and Windows-oriented docs. If you want current Quill behavior, active maintenance, or easy upstream syncing, the upstream repo is the better fit.
Choose this fork if you are building on Vaadin and need editor behavior tuned for Shadow DOM and integration quirks. Choose upstream if you want the latest Quill fixes and broader ecosystem alignment with less fork-specific maintenance.
Choose this fork if you want a Quill codebase tuned for practical editor UX and reliability work, especially around scrolling, accessibility, and non-Latin input. Choose upstream instead if you want maximum compatibility and the lowest merge burden.
Choose this fork only if you specifically want Reedsy’s editor behavior and maintenance workflow. For most new adopters, upstream Quill is the safer default because it is far more active and current.
Automattic/quill
stale
significant_divergence
Choose this fork only if you specifically need its legacy behavior or old tooling. For new work, upstream Quill is the safer choice because this fork is very stale and substantially behind.
yananym/quill
stale
significant_divergence
Choose this fork only if its Shadow DOM and legacy behavior fixes match an existing dependency. For new work or long-term maintenance, upstream Quill is the safer default because this fork is materially stale and likely missing many later editor and stability improvements.
2Pacalypse-/quill
stale
significant_divergence
Prefer this fork only if its table-centric legacy behavior is the requirement and you can live without modern upstream maintenance. For new work or long-term maintenance, upstream Quill is the safer choice.