gibMacOS: downloading macOS installers from Apple's own catalog, without a Mac
Py2/py3 script that can download macOS components direct from Apple
At a glance
- What is it?
- gibMacOS is a Python 2/3 script that pulls macOS installer components straight from Apple's software update catalog and can assemble a bootable Internet Recovery USB on Windows. It is a catalog client, not an installer, and macOS 11 and later changed what it can build.
- Who is it for?
- gibMacOS fits people who need an Apple-hosted macOS installer on a machine that is not a Mac, or who want the installer files without going through the App Store. It does not fit anyone expecting a one-click installer: you get a downloader, a separate build step, and a hard stop at macOS 11 for the Windows USB route.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 150 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- corpnewt/gibMacOS7,372 ★ · +81
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| corpnewt/gibMacOS | 7.3k | 7.4k |
81 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What gibMacOS is for, and who actually needs it
Apple ships macOS through the App Store and through software update, both of which assume you already have a working Mac. gibMacOS takes a different route: it reads Apple's own catalog and downloads the installer components directly. The Readme describes it as a "Py2/py3 script that can download macOS components direct from Apple." That single sentence defines the audience. You are on Windows or Linux, or on a Mac whose App Store path is broken, and you want the installer payload rather than a store download.
The second audience is the one the Readme calls out explicitly: building Internet Recovery USB installers from Windows, using dd and 7zip. That is a narrower and more fragile job than downloading, and the Readme immediately qualifies it. Since macOS 11 (Big Sur), Apple changed how macOS is distributed, and Internet Recovery USBs can no longer be built via MakeInstall on Windows. Versions through Catalina still work.
The tool is a catalog client. It does not install anything, it does not patch anything, and it does not make an unsupported Mac supported. If that is what you were hoping for, you want a different tool.
How the catalog download and the Windows USB build fit together
The repository is split by platform at the top level. gibMacOS.py is the core script, with gibMacOS.command and gibMacOS.bat as launchers for macOS and Windows. MakeInstall.py, with MakeInstall.bat, is the Windows-side installer builder. BuildmacOSInstallApp.py and BuildmacOSInstallApp.command handle creating the install application on macOS. Scripts/ holds the supporting modules.
The data flow is: the script downloads macOS components from Apple, and then a second step turns those components into something bootable or installable. The Readme credits FoxletFox's FetchMacOS for "outlining the URL setup," which is the part of the project that talks to Apple, and credits munki's macadmin-scripts and timsutton's brigadier as prior work in the same space. BuildmacOSInstallApp.command is based on wolfmannight's manOSDownloader_rc.
That separation matters when you plan. Downloading and building are distinct operations with distinct failure modes, and on Windows the build step is the one that stopped working at Big Sur. The Readme's second note adds another wrinkle for macOS 11 and later: Apple distributes the OS as an InstallAssistant.pkg file, and BuildmacOSInstallApp.command is not needed to create the install application in that case. You run InstallAssistant.pkg and it places the install app in /Applications. So the tool's own build helper is bypassed on modern macOS by Apple's packaging change.
Installing gibMacOS and running a first download
There is no package to install. The Readme points to the GitHub repository as the source, and the repository is a set of scripts you run in place. Clone it or download it, then invoke the launcher for your platform. On Windows that is the batch file:
git clone https://github.com/corpnewt/gibMacOS.git
cd gibMacOS
gibMacOS.batOn macOS the equivalent launcher is the command file, and the Python script can be run directly on either platform:
./gibMacOS.commandpython3 gibMacOS.pyThe Readme does not document the script's options or the resulting directory layout, so treat the first run as exploratory: select one version, watch where the files land, and confirm the download completed before you select anything else.
If your goal is the Windows Internet Recovery USB, the second step uses MakeInstall with dd and 7zip, both linked from the Readme rather than bundled:
MakeInstall.batThat path is the one the Readme limits to macOS versions through Catalina. For Big Sur and later on macOS, the Readme's instruction is to run the downloaded InstallAssistant.pkg, which places the install app in /Applications, and to skip BuildmacOSInstallApp.command entirely.
The Big Sur boundary is the limitation that decides your use case
The most consequential thing in the Readme is not a feature, it is a cutoff. Internet Recovery USBs cannot be built via MakeInstall on Windows for macOS 11 and later. If your reason for using gibMacOS is that you have a Windows machine and a Mac that will not boot, the tool covers Catalina and earlier and stops there. Everything after that needs a different approach, and the Readme does not describe one.
The second limitation is that the tool tracks Apple's distribution format, which Apple changes. Big Sur moved macOS to an InstallAssistant.pkg, which made BuildmacOSInstallApp.command unnecessary on macOS. That is a graceful degradation rather than a break, but it shows the coupling: when Apple reshapes distribution, parts of this repository become redundant or stop working, and the Readme is where that gets recorded rather than a changelog. The repository has no published GitHub releases, so there is no versioned changelog to consult for when a behaviour changed.
The third limitation is trust. The Readme carries a note that others are attempting to leverage the gibMacOS name to potentially deliver malware, and that valid copies can always be retrieved from the GitHub repository. Any tutorial, mirror, or repackaged archive you find elsewhere is outside the project's stated distribution channel. That is a real operational constraint, not a formality.
gibMacOS against brigadier and macadmin-scripts
The Readme names the prior work directly, which makes comparison easy. The Readme thanks brigadier, by timsutton, and munki's macadmin-scripts without describing what they do or how they are packaged. gibMacOS is a flat repository of scripts with .command and .bat launchers, designed to be run from a checkout on either Windows or macOS.
That flat layout is the actual distinction. There is no install step, no dependency manifest to resolve, and no entry point registered on your PATH. You clone and run. For a one-off recovery job on a Windows box, that is less friction than setting up a Python environment. For anything you want to call from other automation, the lack of packaging is a cost: you are invoking a script by path and parsing its interactive output.
The Windows Internet Recovery USB build is the capability with the Big Sur cutoff. If you need Catalina or earlier on Windows, gibMacOS is the direct fit. If you need current macOS, the catalog download still works but the USB build does not, and a Mac-side tool is the better choice.
Licence and what maintenance costs you
gibMacOS is MIT licensed. That is permissive: you can use, copy, modify, merge, publish, and distribute it, including in commercial contexts, provided the copyright notice and permission notice are retained. The repository includes a LICENSE file at the top level, which is what you would ship alongside any redistribution. This is a description of the licence text, not legal advice; if you are embedding the scripts in a product, read the LICENSE file and get your own counsel.
The practical upgrade cost is low and unusual. The repository has no published GitHub releases, so there is no version to pin and no upgrade procedure to follow. You track the master branch, and the launchers run from wherever you cloned them. The cost is not upgrading, it is re-verifying after Apple changes something. The Big Sur notes in the Readme are the record of the last time that happened, and they were added as prose rather than as a versioned change.
The last push to the repository was on 2026-06-18. The repository is not archived. Whether that recency means anything depends on whether Apple has changed its distribution format since; the Readme's notes are the place that would show it.
Editorial conclusion
gibMacOS fits people who need an Apple-hosted macOS installer on a machine that is not a Mac, or who want the installer files without going through the App Store. It does not fit anyone expecting a one-click installer: you get a downloader, a separate build step, and a hard stop at macOS 11 for the Windows USB route. Before adopting it, check that the catalog entry you want is still served, confirm you are pulling from github.com/corpnewt/gibMacOS rather than a rehost, and read the three notes at the top of the Readme, which set the Big Sur boundary and the malware warning.
Frequently asked questions
How do I use gibMacOS?
Clone the repository from GitHub, then run the launcher for your platform: gibMacOS.bat on Windows or gibMacOS.command on macOS. The script downloads macOS components direct from Apple. The Readme does not document its options, so the first run is exploratory.
How do I use gibMacOS on Windows?
Run gibMacOS.bat from a checkout of the repository to download components. To build an Internet Recovery USB you also need dd and 7zip, both linked from the Readme, and you run MakeInstall.bat. The Readme states that this USB build no longer works for macOS 11 and later, only through Catalina.
How do I install gibMacOS?
There is no install step. The Readme points to the GitHub repository as the source, and you run the scripts from the checkout with the platform launcher or by invoking gibMacOS.py directly with Python.
Is gibMacOS safe?
The Readme states that others are attempting to leverage the gibMacOS name to potentially deliver malware, and that valid copies can always be retrieved from the GitHub repository. It advises avoiding third party rehosts. Source your copy from github.com/corpnewt/gibMacOS.
What is a gibMacOS alternative?
The Readme thanks brigadier by timsutton, munki's macadmin-scripts and FoxletFox's FetchMacOS, but does not describe them. gibMacOS itself is a flat repository of scripts with .command and .bat launchers.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/corpnewt-gibmacos)Star history chart for your README
[](https://hysenlabs.com/projects/corpnewt-gibmacos)Was this useful?