/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

laurent22/joplin

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:54:42.852Z

3mo ago

laurent22/joplin

Joplin is a large, actively maintained open source note-taking and to-do app with sync, offline-first storage, end-to-end encryption, and desktop/mobile/browser coverage. It has high fork and star counts, and recent commits show ongoing work across desktop, mobile, server, and dependency updates, which makes it a strong candidate if you care about a mature, broad-scope forkable codebase.

Loading tags...

Stars54,141

Forks6,030

Default branchdev

Last pushed2026-03-29T21:12:58Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you need Joplin with custom UI/platform behavior and can tolerate divergence from upstream. Choose upstream if you want the most current, broadest-supported release path and fewer merge-risk concerns.

Prefer upstream unless you specifically need this fork as a private staging area or mirror. As provided, it offers no visible feature advantage and is materially behind upstream.

Choose this fork only if its performance-focused desktop changes are the point. For most adopters, upstream Joplin is the safer choice because this fork is materially behind and appears to have stopped active maintenance.

Prefer this fork only if the Tomcat WebDAV and fork-specific behavior are important enough to justify falling behind upstream. If you want the most stable, current Joplin, upstream is the safer choice.

Choose this fork only if you need its repo-specific workflow and are willing to own merge debt. If you mainly want the latest stable Joplin experience, upstream is the safer choice.

Choose this fork if voice typing and deep customization matter more than staying close to upstream. Choose upstream if you want the latest fixes, easier maintenance, and lower merge risk.

Choose this fork only if voice typing is the point of adoption and you are prepared to own maintenance. If you want a stable Joplin base with current fixes, upstream is the safer choice.

Choose this fork only if voice-typing is the main requirement and you are prepared to own a long-lived divergence. For most adopters, upstream Joplin is the safer default because this fork is materially stale and much harder to maintain.

Choose this fork if you need the server/container and deployment changes it adds. Avoid it if you want the safest path to current upstream Joplin, because it is significantly behind and likely costlier to rebase.

Choose this fork if voice typing is the feature you need and you are comfortable carrying a stale, heavily diverged Joplin branch. If you want the most current Joplin fixes and broad platform stability, upstream is the safer base.

Fork comparison

personalizedrefrigerator/joplin

70/100

active

significant_divergence

Choose this fork if you need Joplin with custom UI/platform behavior and can tolerate divergence from upstream. Choose upstream if you want the most current, broadest-supported release path and fewer merge-risk concerns.

Likely purpose

A customization-oriented fork for users who want Joplin-like core functionality plus targeted platform and UI behavior changes, especially around browser/mobile compatibility and editor/dialog handling.

Best for

Users who already rely on Joplin and need fork-specific fixes before they can adopt upstream changes.; Teams embedding or extending Joplin who want a more customized browser/mobile behavior set.; Adopters who value pragmatic bug fixes over staying maximally close to upstream.; Developers comfortable maintaining a divergent TypeScript/Node monorepo.

Additional features

Safari support in the web experience.
Custom dialog behavior and fixes for stacked dialogs on web and mobile.
Desktop secondary-window crash prevention and plugin callback registry leak fixes.
Broader cross-platform UI consistency work, including shared base properties across platforms.
Ongoing test and infrastructure maintenance across desktop, mobile, server, and Windows-specific paths.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

It is about 200 commits behind upstream, so recent upstream fixes, dependency updates, and maintenance work are not included yet.
Some upstream stability improvements in desktop, mobile, server, and Windows-specific behavior are likely missing because of the lag.
The large removal in mobile resource-screen code suggests some upstream mobile resource-management behavior may be reduced or harder to use here.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Keeps the mature Joplin core: local-first notes, sync, encryption, and multi-platform support.
Adds practical fixes that matter for real users, not just internal refactors.
Recent activity suggests the fork is still being maintained rather than abandoned.
Potentially better fit for users blocked by browser or mobile UI edge cases upstream.

Risks

Large divergence makes future upstream merges harder.
The fork trails upstream, so adopters may miss recent bug fixes and dependency/security updates.
Some changes appear to be removals or refactors, which can create regressions in less-tested workflows.
With 621 changed files, assessing compatibility before adoption is important.

laurent22/joplin · Discofork