/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

TriliumNext/Trilium

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:46:59.591Z

1mo ago

TriliumNext/Trilium

TriliumNext/Trilium is a large, actively maintained open-source personal knowledge base app. It targets cross-platform hierarchical note-taking with a strong focus on large note trees, versioning, search, and rich editing, and it has significant community interest (35,235 stars, 2,348 forks) with recent commits on 2026-03-29/30.

Loading tags...

Stars35,235

Forks2,348

Default branchmain

Last pushed2026-03-30T13:11:20Z

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 only if you intentionally want a legacy Trilium branch with some stability and UX tweaks. If you want current features, active maintenance, and lower risk, upstream TriliumNext is the better default.

Prefer this fork only if its API/website/localization changes are directly useful to you. If you mainly want the full upstream feature set with low maintenance risk, upstream is the safer choice.

Choose this fork only if its specific rendering/UI changes are important to you. If you want the broadest compatibility, fastest fixes, and least maintenance risk, upstream is the safer choice.

Prefer upstream unless you specifically need this fork's older baseline or its small local patches. This fork is materially behind, looks unmaintained, and is best treated as a custom snapshot rather than a healthy alternative distribution.

Choose this fork if you want a worldbuilding-focused Trilium variant with draft hiding and RPG templates. Choose upstream if you need the full, mature Trilium feature set, documentation, and broad platform coverage.

Choose this fork if you want the localized/command-palette/preview improvements and can tolerate a large upstream lag. Choose upstream if you want the broadest feature set, latest fixes, and easiest long-term maintenance.

Prefer upstream unless you explicitly need this historical snapshot; this fork shows no added value and is significantly behind current upstream.

Choose this fork only if the presentation/slide workflow is the main requirement. If you want a stable, broadly current Trilium install, upstream is the safer choice.

Prefer this fork only if its API/documentation or localized deployment work matches your needs. If you want the full upstream feature set and current fixes, upstream is the safer choice.

Choose this fork only if you specifically need its older, customized behavior. For most adopters, upstream is the better default because it is actively maintained and far ahead in fixes and features.

Fork comparison

baddate/trilium

38/100

stale

significant_divergence

Choose this fork only if you intentionally want a legacy Trilium branch with some stability and UX tweaks. If you want current features, active maintenance, and lower risk, upstream TriliumNext is the better default.

Likely purpose

Preserve and tweak an older Trilium release for continued use, with emphasis on sync robustness, UI polish, and bundled docs/assets rather than tracking upstream development.

Best for

Existing Trilium users pinned to the 0.61-era experience who need a maintained local fork.; Operators who value incremental stability fixes over new upstream features.; People with an existing deployment that depends on the fork's older behavior or bundled docs.

Additional features

More forgiving sync/network handling, including graceful handling of connection and ERR_* failures.
UI polish in note interaction, including improved zoom behavior and fuller note tooltip previews.
Sync/storage hardening such as blob-erasure cleanup and blobId indexing.
Custom documentation and packaged assets that suggest a locally maintained distribution and docs site.
Vendor/library refreshes around editor/rendering dependencies and bundled frontend assets.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

Thousands of upstream commits and recent fixes are absent; this fork is far behind current TriliumNext.
Current upstream maintenance cadence, nightly builds, and fresh dependency updates are missing.
Newer upstream documentation, API/docs generation, and cross-app refinements are likely not present.
Adopters lose the latest upstream bugfixes, security patches, and compatibility work after mid-2023.
It trails upstream by 9013 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Older codebase may feel more predictable for users already deployed on that release line.
Includes practical stability fixes around sync, errors, and note interaction.
Large amount of bundled assets/docs suggests a self-contained distribution path.

Risks

Very stale relative to upstream, so security and compatibility risk is high.
Huge divergence means future merges from upstream will be difficult.
User-facing behavior may differ in subtle ways from current Trilium docs and support guidance.