Introducing Munki Theme Maker
For many Mac administrators in a variety of sectors an open source tool called Munki, a patch management tool, is more than prolifically used. Our mantra of being a technology agnostic consultancy agency exposes us to a wide range of Mac tools. Munki is one that we internally have used for years.
Last year at the Mac Admins Conference at Penn State we gave a talk and showed off a script that we had been using internally to take the Munki product and make it fit more seamlessly into the look and feel of any organization. On that note we are pleased to announce the next step release of that then script.
Munki Theme Maker takes the concepts of the script that we demonstrated and wraps it with an elegant GUI interface making it easy for even the novice Mac Admin to take it off the shelf and start creating a custom and branded experience for their Mac users.
Munki Theme Maker allows you to create custom color based scheme themes for Munki. This app picks up on the amazing work of the Munki project and the Munki Rebrand project. The theme maker allows you to have a more modern color schemed UI made for your brand. Change the background color, featured item color and the sidebar link colors. The default new theme includes new icons on the top header row. More modern and clean rounded corner look and feel. Adding the sidebar to category pages as well as the main header slideshow or header graphic area.
Usage
Upon launching the app you must set all variables. If any variables or customized items are missing it will fail to run. The most important items are the Source Folder (Where Munki is downloaded and compiled), the Output folder where you will get 2 copies of Munki the unbranded and the branded and themed versions. The App Name (the new name of the Managed Software Update App that you wish it to be). The signing certificate authority (for use when signing the final package - Developer ID Installer) and the App certificate authority (for used to sign the binaries of Munki - Developer ID Application).
Pick the colors of the theme in the next tab (Colors) and then finally set the icon that you will use for the final touch. Once all set hit “Generate” and let the Munki Theme Builder do its thing.
It will download and clone into your source folder Munki, Munki Rebrand and the base Munki Theme with all injectable files. Injection happens, and then Munki builds.
The App has backwards compatibility for Munki version 4.1.4 as of writing this through to version 5.0.0. We plan to relase new baseline themes and modifications for each dot iteration of the Munki core release.
Open Source
We are opening this up to the Mac Admin’s community with hopes that Munki Theming and or native support for easy to manage themes for the Munki GUI interface will become more prolifically used and supported. Version 1.0 is now available for download in full source mode or as a precompiled and signed (not notarized ) download. Pull requests are welcome!
Here is a little video of it in action. We hope you love it!
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.03 · Low AI Influence
Summary
Munki Theme Maker is a GUI interface for creating custom and branded themes for Munki. It allows users to change the background color, featured item color, and sidebar link colors. The default new theme includes new icons on the top header row and a more modern and clean rounded corner look and feel.
Related Posts
Preparing a BlueSCSI Card for My PowerBook 145 with Basilisk II
A step-by-step walkthrough for preparing a BlueSCSI v2 PowerBook card image with Basilisk II: download the pieces, configure the emulator, boot a working classic Mac image, mount the target System 7.1 image, stage tools, and shut down cleanly before moving the image to the card.
How I Keep Up With ISC2 CPE Credits Without Making It a Second Job
Keeping up with ISC2 CPE credits is easier when you treat it like a normal professional habit instead of a renewal emergency. Here is the system I use across CISSP, CCSP, SSCP, and CSSLP, with free and low-friction sources for webinars, books, training, and work-based credits.
When AI Agents Trust the Wrong Tool Description
Microsoft's MCP tool-poisoning research shows why AI agent security has to treat tool descriptions, schemas, and metadata as part of the control plane instead of harmless documentation.
Jamf Was My Mac Evidence Layer for CMMC
How Jamf Compliance helped support the Mac portion of a CMMC assessment, and why I added a small read-only CSV summary script for auditor-ready failed-result evidence.
How a Floppy Disk Turned My PowerBook 145 Around
A replacement adapter finally brought my PowerBook 145 back to life, but the storage bay had a stranger problem than I first thought: the drive inside was an IDE drive, not the SCSI storage this machine needs. The surprise was that 6 MB of RAM made a System 7.1 RAM Disk boot possible while I wait on a replacement cable and BlueSCSI.
What I Check Before I Trust a Homebrew Formula or Cask
Homebrew gives Mac admins a useful first-pass inspection workflow before trusting a formula or cask: check the source, checksum, version, tap state, availability, and upstream maintenance story.
When a Local AI Tool Belongs in My Workflow and When It Stays in the Lab
Running AI locally on a Mac has become a real part of my workflow, but only once I stopped treating local models like general-purpose answers and started treating them like constrained components inside a system I can still inspect.
Apple’s WWDC26 AI Story Is About Control, Not Just Models
Apple’s WWDC26 special presentation on Apple Intelligence and Xcode was less about adding a chat box to developer tools and more about making AI part of the platform boundary. Xcode agents, App Intents, Foundation Models, Core AI, and MLX all point toward the same idea: intelligent features need context, permissions, testing, and clear ownership before they belong in production software.
What a Dead PowerBook 145 Still Told Me
I picked up a clean PowerBook 145 knowing it might be a gamble. What I found was a machine that looked promising on the outside, demanded the correct 7.5V power approach, revealed a torn hard drive ribbon cable inside, and still refused to chime. That first teardown ended up being less about a successful revival and more about the reality of vintage Apple restoration.
The CMMC Evidence Collection Guide I Wish I Had Before My Assessment
When I started preparing for a CMMC assessment, I expected to spend most of my time focused on policies, procedures, and the System Security Plan. Those things are certainly important, but what surprised me was how much of the assessment ultimately came down to evidence.
