filamentphp/filament

Prefer this fork only if you need its specific customizations and are prepared to maintain a legacy branch yourself. If you want the safest path for a new build, upstream is the better default.

Choose this fork only if you need legacy 2.x compatibility and can tolerate a stale, heavily divergent codebase. For new work or active maintenance, upstream is the safer default.

Choose this fork only if you need its existing 3.x-specific customizations and are prepared to maintain a divergent codebase. For new work or anyone wanting current Filament capabilities, upstream is the safer default.

Choose this fork only if you need its existing custom behavior and are prepared to own the divergence. For new work, upstream Filament is the safer default because it is active, current, and much better maintained.

Choose this fork only if you need the customized 2.x behavior and are prepared to maintain a deeply diverged codebase. If you want current Filament capabilities and active maintenance, upstream is the better choice.

Prefer this fork only if you need an old, frozen Filament 3.x snapshot. For most adopters, upstream is the better choice because it is actively maintained and far ahead.

Prefer this fork only if you want its specific 3.x customizations and are comfortable owning a divergent, stale codebase. If you want long-term maintenance or upstream parity, the upstream project is the safer choice.

Choose this fork only if its extra panel, table, select, translation, and docs work matches your product needs and you can absorb ongoing merge debt. If you want the safest path to current Filament fixes, upstream is the better default.

Choose the fork only if you must remain on Filament 3.x. For new work or active maintenance, upstream is the better choice because this fork adds no visible features and is far behind current upstream development.