Discofork
Repository brief

SeleniumHQ/selenium

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-30T19:47:40.158Z
1mo ago

SeleniumHQ/selenium

SeleniumHQ/selenium is the main Selenium browser automation framework repository. It is active, widely used, and very large: 34,167 stars, 8,668 forks, and recent commits as of 2026-03-30. The repo hosts a multi-language ecosystem around WebDriver, with top-level code for Java, JavaScript, Python, C#, Ruby, Rust, and C++.

GitHub
Loading tags...
Stars34,167
Forks8,668
Default branchtrunk
Last pushed2026-03-30T16:13:13Z
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

9 of 9 fork briefs
Selected

Choose this fork if you want an actively maintained but strongly customized Selenium base and can accept losing some upstream workflow support. Avoid it if you need the broadest Selenium compatibility, the latest browser protocol coverage, or minimal merge overhead.

Prefer this fork if you need its Grid/Docker/BiDi-specific behavior and can tolerate substantial upstream drift. Prefer upstream if you want the broadest compatibility, freshest browser support, and lower maintenance risk.

Choose this fork only if you specifically want its repo/workflow customizations and are prepared to manage substantial upstream drift. If you want a broadly current Selenium distribution, upstream is the safer default.

Prefer this fork only if you need its specific local changes and are prepared to maintain a large divergence from upstream. For most adopters, upstream Selenium is the safer choice because it is much newer and this fork appears stale and behaviorally narrower in places.

Prefer upstream unless you explicitly need the fork's custom .NET/BiDi and generated-protocol changes. This fork is best treated as a specialized, stale branch for experimentation or pinning, not as a general-purpose Selenium replacement.

Adopt this fork only if you need its specific .NET and workflow customizations. For most users, upstream Selenium is the better choice because it is much newer, actively maintained, and far less risky to consume.

Choose this fork only if you need its custom build/release and dependency state and are prepared to maintain a large downstream branch. If you want current Selenium behavior, this fork is too stale and too divergent to be a low-maintenance choice.

Prefer this fork only if you specifically need an old, pinned Selenium baseline with a few historical compatibility tweaks. If you want current browser support, active maintenance, or a healthy upgrade path, upstream is the better choice.

Prefer upstream unless you specifically need this fork's older snapshot plus its build-system and workflow changes. This fork is only attractive if you want to own the maintenance burden and value the custom packaging/container direction more than current Selenium compatibility.