sparkle-project/sparkle

A software update framework for macOS

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 6th, 2026
Created on August 11th, 2009
Open Issues & Pull Requests: 21 (+0)
GitHub issues: Enabled
Number of forks: 1,134
Total Stargazers: 9,669 (+0)
Total Subscribers: 155 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.1 hours
Mean response time: 153.5 days
90th percentile: 38.5 days
Tracked items: 58

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 15% of issues opened in the past year have been closed. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,982 days
Stale 30+ days: 8
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • 1.x (3)

Most active issues this week

Detailed Description

Sparkle is a software update framework for macOS that handles secure and reliable application updates with minimal developer effort.

The framework solves the problem of distributing updates to macOS applications by providing a complete update system that requires no code changes to the host application and only static files on a web server. It uses RSS-based appcasts for release information and verifies updates through EdDSA signatures and Apple Code Signing. The approach supports delta updates that patch only changed files, atomic-safe installations, and automatic permission handling with authentication prompts when needed.

Developers maintaining native macOS applications should choose this tool if they need a straightforward update mechanism without building custom infrastructure. It suits applications, package installers, preference panes, and plug-ins, and in version 2 it extends to updating external bundles and sandboxed applications. The framework offers customizable user interfaces and supports beta channels, phased rollouts, and critical update marking. It requires an HTTPS server for serving updates and macOS 12.0 or later at runtime.

The project maintains active continuous integration with automated testing on recent commits. Development follows a documented roadmap tracked through milestones, and the team publishes detailed internal design documentation alongside the codebase. The project distributes nightly builds from successful workflow runs in addition to formal releases, allowing developers to test unreleased changes.