SeleniumHQ/selenium

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.