chriscurrycc/memos
active
significant_divergence
Selected Adopt this fork if you want Memos plus deeper integration and operator tooling, and you are willing to manage divergence from upstream. Avoid it if you want the safest, most up-to-date upstream baseline with minimal maintenance burden.
FuZoe/memos
stale
significant_divergence
Choose this fork only if you specifically want the Docker reproduction path or its downstream UI/localization changes. For most adopters, upstream is the safer choice because this fork is stale, heavily diverged, and likely missing recent fixes and security-related behavior.
davila7/memos
slowing
significant_divergence
Choose this fork if the added media support and UI polish matter more than staying close to upstream. Avoid it if you want the safest path for integrations, plugins, or low-maintenance upgrades from upstream Memos.
kuusei/memos
stale
significant_divergence
Choose this fork only if its custom search/filter behavior or tag-based release workflow is the reason you need it. For general adoption, upstream is the safer default because this fork is stale and materially behind on recent fixes and API behavior.
easyselfhost/memos
stale
significant_divergence
Choose this fork only if you specifically want its older custom API/workflow direction and are prepared to maintain it yourself. If you want a current, low-risk self-hosted notes app, upstream is the better fit.
Choose this fork if the added timestamp and filtering behavior matters more than staying fully current with upstream. If you want the newest upstream fixes and a larger support ecosystem, upstream is the safer default.
edonyzpc/memos
slowing
significant_divergence
Choose this fork if shared-note rendering, signed image exports, and custom attachment/share behavior matter more than staying current with upstream. If you want the broadest ecosystem compatibility and the newest upstream fixes, upstream is the safer default.
hidding-dev/memos
stale
significant_divergence
Choose this fork only if you need its specific downstream changes and are prepared to maintain a large divergence. If you want the most current, low-friction Memos experience, upstream is the safer default.
Yamico/memos
stale
significant_divergence
Choose this fork only if its memo display and API customizations matter more than staying current with upstream. For most adopters, the 200-commit lag and large divergence make upstream the safer default.
itschip/memos
stale
significant_divergence
Prefer upstream if you want a current, lower-maintenance self-hosted notes app. Prefer this fork only if you specifically need its custom memo-hub direction and are willing to own a stale, high-divergence codebase.