Discofork
Repository brief

slab/quill

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T13:14:28.519Z
3mo ago

slab/quill

Quill is a widely used, actively maintained rich text editor monorepo for compatibility and extensibility. It has a large ecosystem footprint, with 47,006 stars and 3,630 forks, and recent commits in July 2025 show ongoing maintenance and test/editor behavior work. Forks are likely most interesting if you care about editor behavior, scrolling, stability, or packaging around a mature WYSIWYG codebase.

GitHub
Loading tags...
Stars47,006
Forks3,630
Default branchmain
Last pushed2025-07-25T06:09:23Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

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.

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.

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.

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.

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.

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.

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.