/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

jestjs/jest

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-30T11:56:50.808Z

3mo ago

jestjs/jest

jestjs/jest is the main Jest monorepo: a large, active JavaScript testing framework with a documentation site, TypeScript support, and a broad package-based codebase. It looks like a mature upstream worth watching if you care about testing infrastructure, release cadence, or fork-specific changes rather than a small standalone library.

Loading tags...

Stars45,331

Forks6,640

Default branchmain

Last pushed2026-03-29T15:12:50Z

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

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you need its older fork-specific behavior or a frozen training/research snapshot. For production use or anything that needs current Jest fixes and ecosystem compatibility, upstream is the better choice.

Prefer this fork only if you need the specific older-era behavior it carries and can accept a stale maintenance posture. For most users, current upstream Jest is the better choice because this fork is materially behind and likely to cause compatibility and security debt.

Prefer upstream unless you specifically need this old fork’s editor/workflow tweaks or legacy compatibility. For new or actively maintained projects, the fork is too stale and too far behind to be a good default choice.

Prefer this fork only if you specifically need its downstream documentation/workflow state and are prepared to maintain a large divergence. For most adopters, upstream Jest is the safer choice because this fork is stale and substantially behind current maintenance.

Choose this fork only if you need an older, frozen Jest baseline and are prepared to maintain it yourself. For most adopters, upstream Jest is the better choice because this fork is materially stale and likely missing many years of fixes and improvements.

Choose this fork only if you need a near-identical Jest snapshot. If you want new capabilities, active downstream maintenance, or faster access to upstream fixes, upstream Jest is the better default.

Choose this fork only if you need its specific compatibility patches and are willing to own the maintenance gap. If you want the current Jest release train, active security updates, and upstream docs/runtime fixes, upstream is the better default.

Choose this fork only if you need an older, customized Jest line with local backports and can accept substantial maintenance debt. If you want current Jest behavior, security fixes, and lower operational risk, upstream is the better choice.

Choose this fork only if you need an old, mostly static Jest snapshot and are prepared to own maintenance. If you want current Jest behavior, security fixes, or active ecosystem compatibility, upstream is the better choice.

Prefer this fork only if you explicitly need an older, frozen Jest 29.x base. For most adopters, upstream is the better choice because this fork is materially stale and likely missing a long run of fixes and compatibility work.

Fork comparison

MLH-Fellowship/jest

38/100

stale

significant_divergence

Prefer this fork only if you need its older fork-specific behavior or a frozen training/research snapshot. For production use or anything that needs current Jest fixes and ecosystem compatibility, upstream is the better choice.

Likely purpose

A legacy Fellowship fork used for hands-on contribution, experimentation, or teaching around Jest internals and documentation, not for tracking current upstream releases.

Best for

Teams intentionally maintaining an older Jest snapshot.; Students or fellows studying Jest internals and documentation workflows.; Maintainers who want a fork with custom test-environment and resolver behavior, not a current release train.

Additional features

Support for test environment options in docblocks.
Removal of the old `testURL` option in favor of `testEnvironmentOptions`.
Mandatory `context` argument for test environments.
Async resolver support in `jest-resolve`.
Ability to search for tests in `node_modules`.
Global config passed into the Jest environment constructor.

Missing features

It is far behind current upstream maintenance and release work, so newer Jest fixes, security updates, and dependency refreshes are likely missing.
It likely lacks upstream changes after the 2022 fork point, including the v30.x era documentation, changelog, and lockfile updates.
Users depending on current upstream website/docs or modern release behavior should expect substantial drift and possible incompatibilities.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Keeps the full Jest monorepo shape, including packages, docs, examples, e2e tests, benchmarks, and website infrastructure.
Contains fork-specific improvements around resolver behavior and test-environment configuration.
May be useful for contributors who need an older, easier-to-study codebase with explicit experimental changes.

Risks

Very stale activity: last push was in 2023, while upstream is active in 2026.
Large divergence across thousands of files makes rebasing and support costly.
Adopters may inherit outdated dependencies and behavior that no longer matches current Jest expectations.

jestjs/jest · Discofork