Discofork
Repository brief

mattermost/mattermost

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-30T15:31:39.686Z
1mo ago

mattermost/mattermost

Mattermost/mattermost is the main upstream repository for Mattermost, an open core self-hosted collaboration platform. It is active, large, and widely forked, with Go and React code, PostgreSQL, and monthly MIT-licensed releases.

GitHub
Loading tags...
Stars36,004
Forks8,466
Default branchmaster
Last pushed2026-03-30T15:13:22Z
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

Prefer this fork if you want deployment automation and are comfortable losing Content Flagging plus carrying significant upstream drift. Prefer upstream if you need the full supported feature set, easier upgrades, and closer release parity.

Prefer this fork only if Redis PubSub clustering is the point and you can treat it as a maintained internal branch. For most adopters, upstream Mattermost is the safer choice because this fork is materially stale and likely missing many years of fixes and features.

Choose this fork only if you need its legacy customizations and are prepared to maintain a heavily outdated codebase. For most adopters, current upstream is the safer and lower-cost choice.

Prefer this fork only if you need its specific legacy patches and are prepared to own maintenance. For most adopters, current upstream is the safer choice because this fork is stale and substantially diverged.

Choose this fork if you want a customized Mattermost distribution and are willing to own substantial downstream maintenance. Avoid it if you need close upstream compatibility, easy upgrades, or the broadest set of current Mattermost features.

Choose this fork only if ADFS 3.0 support is the primary requirement and you can accept an aging, heavily diverged codebase; otherwise upstream Mattermost is the safer choice.

Prefer upstream unless you specifically need an old 2018 Mattermost snapshot. This fork is far behind, effectively unmaintained, and its value is mainly as a legacy reference or frozen deployment base rather than a practical starting point for new adopters.

Choose this fork if you value its added guest-auth, agents, and UI/workflow customization more than upstream freshness. Avoid it if you need a low-maintenance Mattermost deployment or expect easy future upgrades from upstream.

Prefer this fork if OpenID/Keycloak integration is the main reason you are forking and you are prepared to maintain a divergent codebase. Avoid it if you want the current Mattermost feature set, easier upgrades, or broad plugin/deployment compatibility.

Prefer this fork only if its custom search, boards, and automation changes are the point of adoption. If you want a current Mattermost base with low maintenance risk, upstream is the safer choice.