wannacfuture/directus
stale
significant_divergence
Selected Prefer this fork only if you specifically need its older, customized Directus behavior and can own the maintenance debt. For most adopters, active upstream is the safer choice because this fork is stale, highly divergent, and likely missing recent fixes and features.
multijump/directus
stale
significant_divergence
Choose this fork only if you specifically need its LDAP/login and other custom behavior and are willing to carry the cost of a stale, divergent Directus branch. For most adopters, upstream is the safer default because it is much newer and actively maintained.
guilhermejansen/directus
stale
significant_divergence
Prefer this fork only if you need its specific custom behavior and are prepared to maintain a large divergence yourself. For most adopters, upstream Directus is the safer choice because this fork is stale and likely missing recent fixes and UX improvements.
avrtt/directus
stale
significant_divergence
Choose this fork only if its custom behavior is the product. It looks substantially diverged and stale relative to active upstream, so it fits teams prepared to maintain a long-lived fork, not teams wanting easy upgrades or the latest Directus fixes.
rijkvanzanten/directus
stale
significant_divergence
Prefer this fork only if you need its bespoke behavior and are willing to own a substantial rebase/maintenance burden. If you want a current, well-supported Directus base, upstream is the safer choice.
seymoe/directus
stale
significant_divergence
Prefer this fork only if you explicitly need its custom behavior and can absorb the maintenance burden. If you want current Directus features, security fixes, and easier upgrades, upstream is the better default.
thedaviddias/directus
stale
significant_divergence
Prefer this fork only if you need its 2024 snapshot and are willing to own maintenance. For most adopters, upstream Directus is the better choice because this fork is stale and likely missing a large amount of security, bug-fix, and product work.
smokeyfro/directus
stale
significant_divergence
Prefer this fork only if you need its older, customized Directus state and are willing to maintain a large upstream gap. For new adopters or teams that want current features, security fixes, and lower maintenance burden, upstream Directus is the better default.
schacon/directus
stale
significant_divergence
Prefer this fork only if you specifically need its older, customized state and are prepared to maintain it yourself. If you want current Directus features, fixes, and security updates, upstream is the better choice.
bylickilabs/directus
stale
significant_divergence
Choose this fork only if you specifically need an old, highly customized Directus codebase and are prepared to maintain it yourself. For most adopters, upstream Directus is the safer choice because this fork is materially stale and heavily diverged.