Discofork
Repository brief

jgm/pandoc

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-30T20:04:02.618Z
1mo ago

jgm/pandoc

Pandoc is a very mature, high-activity Haskell project for converting between many markup formats. It looks attractive for forks if you want to experiment with document conversion, writer/parser behavior, templates, or packaging, because the repo is large, actively maintained, and has clear modular subprojects for CLI, Lua engine, server, and platform support.

GitHub
Loading tags...
Stars42,990
Forks3,801
Default branchmain
Last pushed2026-03-28T03:56:31Z
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 only if ScholarlyMarkdown support is the primary requirement. For general Pandoc use, upstream is the better choice because this fork is old, heavily diverged, and likely missing many newer capabilities and fixes.

Choose this fork only if its local conversion behavior or reduced surface area matches your needs. If you want the broadest format support and the latest fixes, upstream Pandoc is the safer default.

Prefer this fork if you need the added office-document inputs or want a wasm-oriented Pandoc derivative and can tolerate divergence. Prefer upstream if you want the most stable, best-supported, and most up-to-date Pandoc with the full release and test cadence.

Prefer this fork only if you need an older, customized Pandoc baseline and are willing to give up current upstream fixes. Most users should stay on upstream unless they specifically want the fork’s build/release and output customizations.

Choose this fork only if you need its legacy paper-rendering behavior and can accept a very old, heavily diverged Pandoc base. For most adopters, upstream is the safer and more capable choice.

Prefer this fork only if you specifically want its local writer fixes or Nix workflow and are willing to own long-term divergence. If you want the broadest format support and lowest maintenance risk, upstream Pandoc is the better default.

Prefer upstream unless you explicitly need this fork’s older baseline and its local compatibility/documentation changes. Choose the fork only if you value a frozen, customized Pandoc more than current fixes and ongoing upstream evolution.

Prefer upstream unless you specifically need this fork's older Jira/DocBook/Lua-related behavior or a frozen 2020 codebase. For most adopters, the staleness and 200-commit lag outweigh the fork-specific changes.

Prefer upstream unless you specifically need an old Pandoc snapshot for legacy compatibility or archaeology. This fork looks useful for historical behavior and a few early feature changes, but it is too stale and too far from current Pandoc to be a good default choice for new work.

Prefer upstream unless you specifically need this legacy 2012 branch or its custom old-format behavior. For adopters, this fork is a niche historical base, not a current-purpose Pandoc distribution.