Independent guide. Not affiliated with Dortania or the OpenCore Legacy Patcher project.Official project on GitHub
OCLP Field Guideoclp.dev
OCLP 2.5.1/3.0.0 RC5

Compare

OCLP forks: Mod, Plus and the T2 fork

During the year without a Tahoe release, several forks of OpenCore Legacy Patcher became popular. Here is what each one is, where it stands now, and whether you should use it. We read each project's own README on November 5, 2026.

Checked against OCLP 2.5.1 and 3.0.0Updated 2 min read
On this page 4 sections
  1. Why we do not recommend forks
  2. How to tell the original from a modified build
  3. What about T2 Macs?
  4. Common questions

Short answer

For almost everyone: use the original OpenCore Legacy Patcher. Its 3.0.0 builds now support Tahoe, which was the main reason people looked at forks. OCLP-Mod is archived (June 13, 2026), OCLP-Plus is frozen (June 28, 2026) and was only ever meant for Hackintoshes, and BridgePatcher (formerly OpenCore-Legacy-Patcher-T2) is an experimental alpha whose T2 support its author calls “not ready for general use”. The OCLP developers do not support modified versions.

ForkWhat it addsStatusFor
OCLP-Mod laobamacChinese interface, Intel Wi-Fi in Sequoia, faster KDK and MetalLib download mirrorsArchived June 13, 2026; its API nodes are shutting downNo one, now
OCLP-Plus YBronstA Tahoe root-patch set (Broadcom Wi-Fi, legacy audio) built on OCLPFrozen June 28, 2026“Exclusively for advanced Hackintosh systems”; its README says it is “NOT a project to create patches for unsupported Macs”
BridgePatcher albert-mueller, formerly OCLP-T2Sequoia and Tahoe for unsupported Macs, experimental T2 work (MacBook Air 2018–2019 can boot the installer)“Experimental fork… still in alpha”; disables SIP completely on T2 MacsTinkerers with a spare T2 Mac and full backups

Why we do not recommend forks

  • The OCLP developers do not support modified builds, and ask users not to report fork problems to them.
  • Forks lag behind fixes in the original, and two of the three have stopped.
  • Binaries from unofficial sources cannot be verified the way the signed, notarized OCLP packages can. We do not link to fork binaries.
  • Tahoe, the main draw, is now in OCLP 3.0.0.

How to tell the original from a modified build

We checked the official packages on a GitHub macOS machine with pkgutil --check-signature. OpenCore-Patcher.pkg and OpenCore-Patcher-Uninstaller.pkg from releases 2.5.1 and 3.0.0-rc.5 are all signed by Developer ID Installer: Mykola Grymalyuk (S74BDJXQMD) and notarized by Apple. AutoPkg-Assets.pkg, the large file of bundled components, is not signed, so check its SHA-256 against ours instead. A fork's package will normally carry a different signer, or none, and the OCLP team cannot vouch for it. The exact commands and our hashes are on the download page, and the raw output is in our test files.

What about T2 Macs?

The only reason left to look at a fork is a 2018–2020 T2 Mac. Read T2 Macs first: most of them still run a supported macOS, and the T2 fork is alpha software.

Common questions

Is OCLP-Plus better than OCLP?

It was a Tahoe stopgap aimed at Hackintoshes, frozen since June 2026. For a real Mac, OCLP 3.0.0 is the right tool.

What is OCLP-Mod?

A Chinese-community fork that added Intel Wi-Fi and download mirrors. It was archived in June 2026.

Keep going

T2 Macs (2018–2020)Why 2018–2020 Macs are differentDownload OCLPThe official download, which file you need, how to verify itIs OCLP safe?What it changes, what it does not, and real risks

Something wrong or out of date on this page? Email hello@oclp.dev and we will fix it (see our corrections policy).