Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
Munki is an open-source set of endpoint-management tools that lets macOS administrators manage software installations and removals on Mac clients, without a licence fee. It runs with a web-server-based package repository and can be set up on one machine without a separate web server, making it suited to teams managing fleets of Macs rather than individual users. It handles Apple packages and drag-and-drop disk images, with Managed Software Center helping users quit blocking applications or skip updates that require restart. Originated by Walt Disney Animation Studios in 2010, it had two tracked releases recently, with the latest 18 days ago.
Munki is a set of open-source tools for macOS administrators to manage software installs and removals on macOS client machines.
How can I ensure consistent rule enforcement across all my software deployments?
every run records the git reference its policies loaded from, showing a mismatch if a pipeline judges against an older copy
Which types of software can I manage installations and removals for?
it can install software packaged in the Apple package format and software distributed in "drag-and-drop" disk images
What options exist for handling updates that require user interaction?
users can be allowed to skip updates requiring a logout or restart to install remaining non-blocked updates from Managed Software Center
How can I manage software installation prerequisites across different operating systems?
it can prompt users to install pending Apple updates on both Intel and Apple silicon
What methods are available to manage applications that block system updates?
Managed Software Center can assist users with quitting and relaunching running applications that block pending updates, and offer to skip blocked updates to install remaining ones
+Client software lifecycle managementNot checked yet · Date unknownManages software installs and removals on macOS client machines using a webserver-based package repository.51 releases · 2 other sources · first seen Sep 2014▸
+munki-python symlink standardizationNot checked yet · Date unknownStandardizes the Python executable path to /usr/local/munki/munki-python, replacing the previous symlink location.2 releases · first seen Sep 2020▸
+Catalog integrity validationNot checked yet · Date unknownDetects hash mismatches in installer items before a catalog is published, enabling use as a CI gate on a Munki repository.1 other source · first seen Oct 2026▸
+Linux admin tooling supportNot checked yet · Date unknownAllows makecatalogs to be built and run on Linux, extending Munki's admin-side tooling beyond macOS.1 release · first seen Oct 2026▸
+Big Sur configuration profile emulationNot checked yet · Date unknownEnables macOS Big Sur's emulation of configuration profiles using MCX via the EmulateProfileSupport preference key.1 release · first seen Nov 2020▸
+Delayed authentication restart supportNot checked yet · Date unknownConfigures a delayed authentication restart on macOS 10.12+ via authrestartd.1 release · first seen Mar 2020▸
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for Munki, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Munki puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
What Munki connects to, runs on and detects, read from its release notes and docs. So far: 1 updated supported platform.
Show
1 change, tracked since Oct 27, 2026.
Oct 272026
updatedmacOS support range updated
With macOS 10.15, macOS 11, macOS 12, macOS 27
Munki 7.4.x will be the last releases to support macOS 10.15 and macOS 11. Munki 7.5 will drop support for those two macOS major versions and will support macOS 12 through macOS 27.
Nothing first seen in this window. That doesn't mean Munki shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-10
1
How we count
Read from 1 of 55 release notes and docs updates we hold for Munki. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Munki's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Issue, contributor and maintainer activity in munki/munki, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed100%of issues opened, last 12 months
Median time to close2.9 daysfirst maintainer reply 2.5 days
Open backlog67of 971 issues ever filed
Issues opened / month2 · 0communitymaintainers
Open backlog67
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
features 24%
other 76%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.