bhancockio/crewAI
stale
significant_divergence
Selected Prefer this fork only if you specifically need its older behavior or the handful of added core features; otherwise upstream is the better default because it is far more current, actively maintained, and materially ahead on release, docs, and enterprise workflows.
patchy631/crewAI
stale
significant_divergence
Prefer this fork only if you need its specific older/customized behavior and are willing to own the maintenance burden. If you want current CrewAI capabilities, documentation, and lower integration risk, upstream is the better choice.
thinkbigcd/crewAI
slowing
significant_divergence
Prefer this fork only if you need its specific executor/provider/release customizations and are prepared to maintain a long-lived divergence. If you want the current upstream CrewAI feature set, docs, and lower upgrade risk, upstream is the safer choice.
wandeha1/crewAI
stale
significant_divergence
Choose this fork only if you specifically need its AgentOps-oriented customization or legacy behavior. For most adopters, upstream CrewAI is the better default because this fork is stale and far behind current framework, docs, and enterprise workflow changes.
ashishpatel26/crewAI
stale
significant_divergence
Prefer this fork only if you need its specific tracing, enterprise-doc, or release-process customizations and are prepared to maintain a large divergence. For most adopters, upstream is the safer choice because this fork is materially behind and appears to have removed or rewritten substantial areas.
Emaratilicious/crewAI
stale
significant_divergence
Choose this fork only if its local customizations matter more than staying current with upstream. For most adopters, upstream CrewAI is the safer default; this fork is mainly for teams that need a pre-diverged, customized codebase and are prepared to maintain it themselves.
jeffara/CrewAIAutonomousAgents
stale
significant_divergence
Prefer this fork only if you want its older autonomous-agent experiments and are willing to own the maintenance burden. For most adopters, the upstream project is the safer choice because this fork is substantially stale and likely missing major modern features and fixes.
nhevers/crewAI
slowing
significant_divergence
Choose this fork if you want newer API/runtime capabilities and can tolerate substantial divergence from upstream. Choose upstream if you want the latest maintained release line, broader documentation, and lower integration risk.
wuloi/crewAI
stale
significant_divergence
Prefer this fork only if you specifically need its custom 2025-era behavior and are willing to maintain a large delta yourself. If you want current CrewAI capabilities, upstream is the safer choice; this fork looks materially stale and increasingly expensive to keep aligned.