cheeriojs/cheerio

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.