Automatic
macCurrent can verify the update path and complete it directly or invoke a trusted updater.
Source coverage
macCurrent finds updates and installs supported updates. It checks where an update comes from before installing it. Some updates still need the App Store, Homebrew, or the developer's own updater; macCurrent shows which step to take.
Coverage, not a vanity count
Some products count every package registry, developer tool, or release website as a separate source. macCurrent focuses on installed Mac apps and Homebrew-managed tools. The goal is not the biggest number; it is a defensible answer to three questions: is an update actually available for this Mac, who published it, and who should install it?
Action classes
macCurrent can verify the update path and complete it directly or invoke a trusted updater.
macCurrent detects the update, then opens the store, vendor tool, or app that owns installation.
macCurrent identifies the likely source and explains the safest next step without guessing.
System-managed components stay outside the app-update workflow and are labeled separately.
Recognized families
Availability and action can vary by app because the installed artifact—not its display name—determines ownership.
Reads the installed receipt and the Mac App Store's update state. Apple owns signing, delivery, and installation.
Reads the appcast and requires signed update metadata before macCurrent trusts a direct archive.
Matches the exact installed cask or formula, then keeps Homebrew in control of its own upgrade path.
Detects vendor-owned helpers and routes each app family through the updater that understands its shared components.
Uses HTTPS version metadata and artifact trust when it is defensible; otherwise macCurrent keeps the action manual.
Recognizes signed Tauri updater metadata, compares versions, and opens the app so its embedded key verifies installation.
Requires HTTPS, the expected bundle identity, a trusted signing team, and forward version movement before replacement.
Apple's Software Update remains the availability authority. SOFA adds Apple security-advisory and CVE context to that offer.
Preview builds discover global packages across supported Node installations, checks public npm releases, and uses the owning npm tools to install eligible updates. Project dependencies and private registries stay with their package manager.
Preview builds check compatible extension releases. Eligible updates use a verified Microsoft VS Code or VS Code Insiders installation, preserving supported profiles and pinned-extension choices.
Checks supported IDE plug-ins and vault-specific Obsidian community plug-ins. Eligible user-installed Android Studio plug-ins can update directly; other items use their host app.
Inventories supported creative plug-ins, including AU, VST, VST3, CLAP and AAX audio formats. Update checks depend on a verified source; installation may require the vendor's updater or account.
When ownership or download trust is ambiguous, macCurrent shows the evidence it has and does not silently replace the app.
These package and extension installation features require macCurrent 1.2.0.48 or later. Screenshots show a release preparation build.
A package can belong to a particular Node installation; an extension to an editor profile; an Obsidian plug-in to a vault. macCurrent keeps these installed copies distinct. Discovery alone does not establish a verified update or installation support.
Read the npm package, VS Code extension and Mac plug-in guide for supported actions and limits.
No single verification rule fits every updater. macCurrent preserves the source's native trust boundary instead of flattening all updates into direct downloads.
| Source | Detection evidence | macCurrent action | Final authority |
|---|---|---|---|
| App Store | Store receipt and on-device update listing | Show availability and open the correct store path | Apple |
| Sparkle | Appcast, version, archive signature, and embedded public key | Verify, back up, and install when the signature chain is complete | The app publisher's signing key |
| Homebrew | Installed token, bundle match, and current cask or formula metadata | Invoke the matching Homebrew upgrade | Homebrew plus macOS code-signing checks |
| Global npm packages | Installed package, owning Node installation, public registry and selected version | Preview: use the owning npm tools for an eligible update, then verify the installed version | npm and the owning Node installation |
| VS Code extensions | Extension identity, editor compatibility, architecture, release channel and supported profile | Preview: use the verified editor for eligible updates; otherwise show guidance | The owning VS Code installation |
| Other plug-ins | Host or vault identity, installed version and an applicable verified release source | Preview: install eligible Android Studio plug-in updates; otherwise use the host or vendor updater | The host application or vendor |
| Vendor updater | Vendor helper, ticket, product code, or updater state | Invoke or open that updater | The vendor's signed update system |
| Tauri | Updater endpoint and signed release metadata | Compare the release, then open the app | The key embedded in the Tauri app |
| Direct download | Reviewed HTTPS URL, expected bundle ID, signing team, and version | Back up, validate, and replace only when every check passes | macCurrent's replacement checks and macOS Gatekeeper |
| macOS | Apple's on-device softwareupdate offer |
Show the update with SOFA security context and open Software Update | Apple Software Update |
Transparent by design
macCurrent shows the detected channel, installed identity, available version, and safest next step in one reviewable list.