Prefer upstream unless you specifically need the fork’s February 11, 2026 state for reproducibility or compatibility. This fork adds no visible capabilities and is stale relative to an actively maintained upstream.
Prefer this fork if you specifically want a CLI-centered DSPy variant for agent workflows and are comfortable carrying upstream merge debt. Prefer upstream if you want the broadest feature set, current fixes, and lower maintenance risk.
hwchase17/dspy
stale
significant_divergence
Prefer this fork only if you explicitly want the older demo-heavy codebase and are comfortable freezing on an aging branch. If you want an actively maintained DSPy framework, upstream is the better fit.
tsunrise/dsp
stale
significant_divergence
Choose this fork only if you need the older DSP/DSPy-era code and its notebook-heavy experimental workflow. For new work, upstream is the better default because this fork is materially behind and appears maintenance-stale.
thomasahle/dspy
stale
significant_divergence
Prefer upstream unless you specifically need the fork’s older-runtime support or one of its local integration/caching changes. For most adopters, this fork is too stale and too far from current DSPy to be the safer default.
jalammar/dspy
stale
significant_divergence
Prefer this fork only if its notebooks or inspect app match your workflow and you are willing to own the maintenance burden. For most adopters, upstream is the better choice because this fork is materially older and likely missing newer framework improvements.
jerryjliu/dspy
stale
significant_divergence
Prefer upstream unless you specifically need this fork's inspect-app and notebook-heavy experimentation stack. This fork looks like a useful research/demo branch, but its age and scale of divergence make it a poor default choice for production or long-lived adoption.
kevon217/dspy
stale
significant_divergence
Prefer this fork only if you specifically need its older local-model and notebook-heavy workflow. For most adopters, upstream is the better default because this fork is stale and significantly diverged.
tom-doerr/dspy
active
significant_divergence
Choose this fork if you specifically want the custom GEPA-oriented and internal refactor work it adds, and you can absorb missing upstream material. Choose upstream if you want the fuller tutorial set, broader regression coverage, and lower upgrade friction.
ThanabordeeN/dspy_mcp_intregration
stale
significant_divergence
Choose this fork if MCP integration is the goal. Avoid it if you need the latest upstream DSPy behavior, broad ecosystem support, or low-risk maintenance.