Welding-Torch/erpnext
stale
significant_divergence
Selected Choose this fork only if its added agriculture and India-specific workflows are directly valuable and you can own the maintenance. For most adopters, upstream ERPNext is the safer choice because this fork is years behind and substantially diverged.
ESS-LLP/erpnext-healthcare
stale
significant_divergence
Choose this fork only if you specifically need its healthcare-oriented legacy customization and are prepared to own maintenance. For most adopters, upstream ERPNext is the safer default because this fork is stale and materially behind.
zerodha/erpnext
stale
significant_divergence
Prefer upstream ERPNext unless you specifically need this exact snapshot. This fork shows no meaningful added functionality and is heavily behind active upstream development, so the main tradeoff is more maintenance risk for no clear product gain.
charlotteye835/erpnext
stale
significant_divergence
Prefer upstream ERPNext unless you specifically need this older snapshot; the fork adds no visible features and is materially behind active development.
alenque-82/erpnext
stale
significant_divergence
Prefer upstream ERPNext unless you specifically need this fork's exact 2025 snapshot. It adds no visible capabilities and is materially behind active upstream maintenance.
webnotes/erpnext
stale
significant_divergence
Choose this fork only if you must stay on ERPNext v3 for compatibility reasons. For any new deployment or active product work, upstream frappe/erpnext is the better choice.
ruchamahabal/erpnext
stale
significant_divergence
Prefer upstream unless you specifically need an old, unchanged ERPNext snapshot. For adopters, the main value here is stability by stasis, but the tradeoff is substantial feature and fix lag.
nabinhait/erpnext
stale
significant_divergence
Prefer this fork only if you already rely on its legacy customizations. For a new deployment, upstream ERPNext is the safer default because this fork is massively behind and appears to have substantial feature and localization loss.
Drakkarrr/erpnext
stale
significant_divergence
Treat this as a stale, upstream-lagging snapshot rather than a differentiated fork. Adopt it only if you specifically need the older baseline; otherwise prefer upstream or a fork with visible downstream maintenance.
nextchamp-saqib/erpnext
stale
significant_divergence
Prefer this fork only if its item-group/e-commerce customization is essential and you are prepared to maintain a large upstream gap. For most adopters, upstream ERPNext is the safer choice because this fork is materially stale and likely missing many newer fixes and features.