The short version
A modern Mac app library is not managed by one updater. macCurrent beta scan data from July 2026 puts a number on it: 2,036 distinct apps not yet in the curated catalog, self-reporting updates across 8 channels. Apple owns App Store updates, Homebrew owns casks, Sparkle apps update themselves, vendors like Microsoft and Adobe run their own services, and a long tail of direct downloads still expects a manual visit to a release page. That fragmentation is why a single update checklist misses real apps.
What this report measures
The figures below come from macCurrent beta scan data, July 2026: 7,364 privacy-scoped scan reports submitted by beta users. Each report describes one installed app the curated catalog did not yet recognize, including the update channel the app declares. Across those reports, 2,036 distinct apps appear.
Two caveats keep the numbers honest. First, the reports are privacy-scoped: no file paths, no usernames, no device identifiers, so the data counts apps and channels, nothing about who runs them. Second, the sample is skewed by design: apps the catalog already recognizes, including every Mac App Store app, never appear as unknown, so the direct-download share below looks larger than it would across a whole Mac.
The headline numbers
The 2,036 unknown apps self-report updates across 8 distinct channels:
| Self-reported update channel | Distinct apps |
|---|---|
| Direct download | 1,931 |
| Sparkle | 82 |
| Homebrew Cask | 13 |
| Microsoft AutoUpdate | 7 |
| Adobe Remote Update Manager | 6 |
| Google Software Update | 4 |
| Microsoft EdgeUpdater | 1 |
| Docker Desktop | 1 |
Direct download accounts for 1,931 of the 2,036 apps. Read that with the caveat above: these are apps no established channel had claimed, so direct downloads and niche vendor updaters are what is left over. The long tail is still real: dozens of apps update through Sparkle feeds or vendor services no single updater watches.
What the curated catalog shows
The other half of the picture is the curated catalog: 562 apps with verified update sources enabled. Fragmentation shows up there too.
- 419 apps resolve updates through a Homebrew cask.
- 132 apps update through the Mac App Store.
- 17 apps are vendor-managed (Microsoft AutoUpdate, Adobe, and similar).
- A few use single GitHub-releases, Sparkle-appcast, or vendor-specific feeds.
- 13 apps track more than one enabled source, so source counts overlap the 562 total.
For scale, the Homebrew cask index behind the catalog covers 7,746 casks. Even that most complete third-party channel is only one slice of a real machine's library.
The six common update channels
Zoom out from the counts and most Mac apps fall into one of six update paths: App Store receipts, Homebrew formulae and casks, Sparkle appcasts, vendor-managed updaters, direct-download replacement archives, and manual release pages. Each has a different trust signal, install method, and failure mode. The update sources guide walks through each in detail.
What each channel needs before you trust it
App Store updates should match the installed receipt, Homebrew updates the installed cask or formula identity, and Sparkle updates should verify appcast and archive signatures. Direct replacements should preserve bundle ID and signing team. Vendor updaters should be recognized as intentionally vendor-managed, and manual updates should slow down for review instead of installing silently. The scan data shows why: the largest group of unknown apps has the weakest built-in trust signals.
Why comparing Mac update data is hard
Update coverage claims are hard to verify because every tool sees a different slice of the same Mac: a Homebrew-only view counts casks, a Sparkle-focused menu app counts appcast feeds, and the App Store counts only its own receipts. None is wrong; they measure different populations, so coverage numbers from different tools cannot be compared directly.
This report has the same limitation in reverse: it counts what beta users' Macs contain that established channels had not claimed. A fair comparison starts from the update source: not whether one tool can update everything, but whether it identifies where each app updates from and picks the safest path.
What fragmentation means in practice
If your library looks anything like the scan data, no single channel sees all of it: brew outdated --cask will not list App Store apps, the App Store will not list casks, Sparkle apps often announce updates only when opened, and the direct-download tail updates only when you remember it exists.
The practical fix is not one magic updater; it is knowing which channel owns each app and applying the right checks for it. The pillar guide to updating Mac apps safely covers those habits; the update tracker guide covers keeping an inventory of what updates from where.
Methodology notes
A scan report is one privacy-scoped record for one unrecognized app: its identity, version, and self-declared update channel, with no file paths, usernames, or device identifiers. Distinct apps are counted by identity, so an app seen on many Macs counts once. Channel labels are what the app or its updater declares, not manual classification.
These numbers will shift: as the catalog grows, newly recognized apps leave the unknown set, and new beta users add to it. Treat the figures as a July 2026 snapshot of the beta population, not a census of all Macs.
Where macCurrent fits
macCurrent is built around source-aware update review: it shows App Store, Homebrew, Sparkle, vendor, and direct-download paths together, separating updates that look safe from ones that need review or a handoff. It backs up apps before direct replacements and keeps per-app history. The beta is free through July 31, 2026. Install macCurrent to see the update map of your own Mac.
Frequently asked questions
Why are Mac app updates so fragmented?
macOS has several legitimate distribution models. Apple controls App Store updates, Homebrew manages its own packages, many indie apps use Sparkle, and large vendors often ship their own update services.
Can one tool safely update every Mac app?
No tool should blindly update every app. A safer tool should detect the source, verify identity and signing where possible, back up direct replacements when appropriate, and hand off risky paths for review.
What is the safest Mac app update channel?
There is no single safest channel for every app. The safest path is the one that matches how the app was installed and can be verified before replacement.
Where does the data in this report come from?
From macCurrent beta scan data, July 2026: 7,364 privacy-scoped scan reports from beta users covering 2,036 distinct apps the curated catalog did not yet recognize. Reports contain no file paths, usernames, or device identifiers.
How often is this report updated?
The figures are a July 2026 snapshot of macCurrent beta scan data. They shift as new scan reports arrive and the curated catalog grows, because newly recognized apps leave the unknown-app set.
Can I contribute by running scans?
Yes. Running a scan in the macCurrent beta submits privacy-scoped reports for apps the catalog does not yet recognize, which helps expand coverage. Reports exclude file paths, usernames, and device identifiers.