e1michi/hyperswitch
stale
significant_divergence
Selected Choose this fork only if you specifically want its custom payment-flow and connector changes and can own a large, stale divergence. If you want a maintained default, upstream is the safer base.
keshavthakur30/hyperswitch
stale
significant_divergence
Choose this fork only if you want its custom payment flows and connector/documentation reshaping enough to justify owning a significant maintenance burden. If you want close upstream compatibility or low-risk adoption, upstream is the safer choice.
HarryRegel/hyperswitch
stale
significant_divergence
Choose this fork only if you need its specific 2024 customizations and accept a large maintenance burden. For most adopters, upstream is the better choice because it is far more current and actively maintained.
crawl121/hyperswitch
stale
significant_divergence
Choose this fork only if you want a heavily customized payments switch and are willing to own the divergence. For most adopters, upstream is the safer default because this fork is far behind and appears to have removed or reshaped major parts of the API and connector layer.
radhishukla/hyperswitch
stale
significant_divergence
Prefer this fork only if you need its custom payment/workflow surface and are prepared to maintain a long-lived divergence. If you want current upstream features, connector fixes, and lower maintenance risk, upstream is the safer default.
Rafaelmdcarneiro/hyperswitch
stale
significant_divergence
Prefer this fork only if you need its specific custom API/test/config shape and are willing to own a large rebase burden. For most adopters, upstream is the better choice because this fork is stale and significantly behind.
bdsazzad3/hyperswitch
stale
significant_divergence
Choose this fork only if you want its specific payment/API customizations and are prepared to own divergence. If you want a broadly compatible, actively maintained Hyperswitch base, upstream is the safer choice.
SlaydeSequeira/hyperswitch
stale
significant_divergence
Prefer upstream unless you specifically need this fork's older customizations. This fork looks more like a bespoke maintenance branch than a healthy upstream alternative, with enough divergence that adopting it means inheriting significant rebase and support burden.
shubhexists/hyperswitch
stale
significant_divergence
Prefer upstream unless you specifically need this fork’s older analytics/email/connector-verification work and are prepared to maintain a large divergence. For new adopters, the fork’s stale state and deleted reference assets make it a poor default choice.
Hariharanpugazh/hyperswitch
stale
significant_divergence
Prefer this fork only if you need its custom payments and connector behavior. If your goal is to stay close to upstream Hyperswitch, this branch looks too divergent and too far behind to be the safer base.