Discofork
Repository brief

AlistGo/alist

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:49:37.625Z
3mo ago

AlistGo/alist

Alist is an actively maintained Go-based file listing and WebDAV server for multiple storage backends. It is mature and popular, with 49,235 stars and 7,965 forks, and it is currently receiving recent commits on 2026-03-30. The repository includes Docker support, a web frontend, and broad storage-driver coverage.

GitHub
Loading tags...
Stars49,235
Forks7,965
Default branchmain
Last pushed2026-03-30T06:01:37Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want custom storage workflows and are willing to absorb divergence from upstream. If you mainly want the newest upstream fixes, broad compatibility, and lower maintenance risk, upstream is the safer choice.

Choose this fork only if you want an older pinned snapshot and accept missing upstream progress. For most adopters, upstream Alist is the better choice because it is actively maintained and far ahead.

Choose this fork if your priority is iOS compatibility and the fork’s simplified operational behavior. Stick with upstream if you need Meilisearch search, broader upstream parity, or the newest fixes and driver work.

Choose upstream unless you explicitly need this older, unchanged snapshot. The fork appears to be a stale mirror rather than a differentiated distribution, so it offers little advantage and likely misses a large amount of recent upstream work.

Prefer this fork if the added storage-driver support and deployment customizations match your workload. Prefer upstream if you want the newest fixes, broadest compatibility, and lower maintenance risk.

Prefer this fork only if its modified storage-driver behavior matches your needs and you are comfortable owning upgrades yourself. For most adopters, upstream is the safer default because it is much more current and actively maintained.

Prefer this fork only if you want a private-cloud oriented, selectively trimmed Alist build and its specific compatibility tweaks. If you need broad provider support, ongoing fixes, or easy upstream tracking, the upstream project is the safer choice.

Choose this fork only if its 123-driver tweaks solve a real problem for you. If you want the newest Alist features, fixes, and storage support, upstream is the safer choice.

Prefer upstream unless you specifically need this fork's older custom token and OneDrive tweaks and are willing to own maintenance. For new deployments, this fork is too stale and too divergent to be the default choice.

Choose this fork only if its older provider-specific patches are exactly what you need and you are willing to absorb a large maintenance gap. For most adopters, upstream is the safer default because this fork is significantly stale and appears to have removed substantial functionality.

AlistGo/alist · Discofork