Discofork
Repository brief

cypress-io/cypress

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:55:25.775Z
3mo ago

cypress-io/cypress

Cypress is a large, active MIT-licensed open source browser testing framework. It is widely adopted (49,610 stars, 3,400 forks) and still receiving frequent commits as of 2026-03-29. Forks are most likely interesting if you care about end-to-end or component testing tooling, binary/runtime build flows, or ecosystem integrations around browser testing.

GitHub
Loading tags...
Stars49,610
Forks3,400
Default branchdevelop
Last pushed2026-03-29T20:56:27Z
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

8 of 8 fork briefs
Selected

Prefer the upstream project unless you specifically need this 2019-era fork state or one of its legacy compatibility patches; this fork is too stale and diverged for general adoption.

Prefer this fork only if its CI and framework-matrix changes match your exact environment and you are prepared to maintain a large divergence. If you mainly want current Cypress stability and upstream support, the upstream repo is the safer choice.

Choose this fork only if you need its older, customized Cypress baseline and can own the long-term maintenance cost. For most adopters, upstream is the better choice because it is active, much newer, and far easier to keep secure and compatible.

Prefer this fork only if you specifically need its custom, pared-down baseline and can absorb the maintenance cost. If you want current Cypress behavior, active upstream compatibility, or full test/release coverage, upstream is the safer choice.

Choose this fork only if you need its custom testing/runtime changes and are prepared to maintain a large downstream delta. If you want current Cypress behavior and low operational risk, upstream is the safer default.

Prefer this fork only if you need an older, customized Cypress baseline and are willing to own maintenance. If you want current Cypress capabilities, active bugfixes, and lower long-term integration cost, upstream is the safer choice.

Choose this fork only if you need its customized, older Cypress environment and are prepared to maintain it yourself. If you want a current, broadly supported browser-testing framework, upstream is the better choice.

Prefer upstream unless you specifically need an older, customized Cypress baseline. This fork looks valuable for pinned internal usage or bespoke build/runtime changes, but it is too stale and too divergent for most adopters who want current Cypress behavior and maintenance.