Discofork
Repository brief

cheeriojs/cheerio

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-30T16:07:25.799Z
1mo ago

cheeriojs/cheerio

Cheerio is a mature, actively maintained Node.js library for parsing and manipulating HTML and XML with a jQuery-like API. It is popular and widely forked, with 30,244 stars and 1,690 forks, and it was updated very recently on 2026-03-30. Forks are most interesting if you want to extend HTML/XML scraping, parsing, or DOM-style transformation behavior, or if you want to customize its parsing stack or packaging.

GitHub
Loading tags...
Stars30,244
Forks1,690
Default branchmain
Last pushed2026-03-30T03:15:47Z
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 upstream Cheerio unless you specifically need this fork's parse5-oriented legacy behavior and are willing to absorb long-term maintenance debt. This fork is for legacy compatibility and experimentation, not for users who want an actively maintained default.

Choose this fork only if you need its non-native compatibility or legacy behavior and can accept substantial upstream drift. For most adopters, upstream Cheerio is the safer default because it is actively maintained and materially more current.

Choose upstream unless you specifically need legacy 2014 Cheerio behavior. This fork is heavily outdated and diverged, so it is a poor default choice for new work, but it may help with old compatibility-sensitive codebases.

Prefer upstream unless you specifically need this fork’s legacy behavior. This fork looks useful mainly as a compatibility snapshot, not as a modern default choice.

Choose this fork only if you specifically need its customized site/source behavior and are comfortable owning divergence from upstream. For most adopters who want the safest, most up-to-date Cheerio, upstream is the better default.

Prefer this fork only if you want a heavily customized Cheerio base and are willing to maintain a large divergence. If you just need a stable HTML/XML parser library, upstream is the safer choice.

Choose this fork only if you need its custom changes and are prepared to own a heavily diverged codebase. If you want a current, low-maintenance Cheerio dependency, upstream is the safer choice.

Choose this fork only if you need the legacy branch and its custom docs/tests/benchmarks; otherwise upstream Cheerio is the safer default because it is active, newer, and materially better maintained.

Prefer upstream unless you specifically need old Cheerio semantics or are maintaining a legacy dependency. This fork looks stale and materially behind, but it may still be useful as a compatibility shim for older server-side HTML/XML workflows.

Prefer this fork only if you need a simple frozen copy of Cheerio for teaching or local experimentation. For real adoption, upstream is the better choice because this fork adds nothing and is materially behind.