ocrmypdf/OCRmyPDF

Choose this fork only if you need its older backported behavior or environment-specific patches. For new adopters, current upstream is the safer default because this fork is stale and substantially behind.

Prefer upstream unless you have a hard reason to stay on an older snapshot. This fork offers no visible added capability and is far enough behind that it is mainly useful as a pinned historical copy.

Prefer upstream unless you specifically need this older frozen state. The fork adds no visible capabilities and is far enough behind that it is a poor default choice for new adopters.

Prefer upstream unless you specifically need this exact small patch. This fork does not materially expand OCRmyPDF; it mainly preserves upstream behavior while lagging far behind current mainline.

Choose the fork only if you need legacy compatibility or its packaging/deployment tweaks. For new adopters, upstream is the better default because this fork is far behind and appears to have stalled.

Prefer upstream unless you specifically need a 2019-era compatibility fork. This fork is best seen as a legacy preservation branch with a few backported fixes, not a modern replacement.

Prefer upstream unless you specifically need this fork’s downstream packaging or internal pipeline behavior. This fork looks like a legacy, heavily diverged branch that may still work for a fixed workflow, but it is a poor choice for users who want current OCRmyPDF features, bug fixes, and low-maintenance adoption.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible capabilities and mainly carries the risk of missing upstream fixes.

Prefer upstream unless you specifically need this older snapshot. This fork does not add capabilities, and its main tradeoff is lag: you inherit an older codebase without the newer fixes and workflow improvements upstream has already shipped.