How sparkle-project/sparkle works
Project type and purpose
• Sparkle 2 is a modular, secure macOS update framework that you embed into a host application.
• It exposes a Core Framework (Objective-C/Swift) plus several XPC helper services (Downloader, InstallerConnection, InstallerLauncher, InstallerStatus, Autoupdate Agent), plus command-line tools for building appcasts and deltas.
File structure
• Top-level “Sparkle” directory: the framework’s public/internal API and UI code.
• “Autoupdate”, “Downloader”, “InstallerConnection”, “InstallerLauncher”, “InstallerStatus”: each is a standalone XPC helper/service built as a small command-line tool or daemon for privileged operations (patch unarchiving, download with sandbox entitlements, invoking installers, reporting status).
• “BinaryDelta”, “generate_appcast”, “generate_keys”, “sign_update”, “sparkle-cli”: off-line tools for creating deltas/signatures/appcast feeds or providing a CLI interface.
• “TestApplication”/“TestAppHelper”: a sample host app + helper to exercise the framework.
• “Configurations”, “Documentation”, “Resources”, CI workflows, and tests.
README for additional insights
• Sparkle is embedded in the host app but uses XPC to isolate downloads, code-signing verification, and installation steps.
• Uses RSS-based appcasts served from an HTTPS server.
• Supports delta updates, signature verification (EdDSA + Apple Code Signing), sandboxing, custom UIs, phased rollouts, and multiple update drivers (automatic, user-initiated, probing).