SuperSaver is a Swift package and macOS demo workspace for building, installing, activating, diagnosing, restoring, and researching macOS screen saver, wallpaper, and lock-screen runtime routes.
The repository intentionally includes supported, private, unsupported, SIP-enabled, and SIP-disabled research surfaces behind additive SwiftPM package traits. It excludes legacy product branding and unrelated media or now-playing product features.
This is public research infrastructure, not a supported product release. Private framework, protected-process, and SIP-disabled lanes are documented and gated so future work can reproduce the evidence without pretending those routes are stable public APIs.
Open SuperSaver.xcworkspace to work with the package and demo app together.
Apps/SuperSaverDemo SwiftUI macOS showcase and operator console
Packages/SuperSaver Reusable package, modules, CLI, tests, and experiments
Research Portable findings, traces, maps, and compatibility data
docs Plans and architecture documentation
The complete implementation contract is in
docs/SUPERSAVER_IMPLEMENTATION_PLAN.md.
Remaining work is tracked in ROADMAP.md.
If this research helps your own macOS wallpaper, screen-saver, lock-screen, or
private-framework investigations, GitHub Sponsors and Ko-fi support are wired
through .github/FUNDING.yml.
Run the root validation entry point:
Scripts/validate-all.shValidation is read-only with respect to live wallpaper, authorization, and protected-process state. Privileged installation, live lock-screen work, and protected-process mutation require explicit checkpoints.
The baseline covers the package trait matrix, XcodeGen regeneration, workspace scheme discovery, Debug app test-bundle compilation, Release package artifacts, and non-launching Debug/Release builds for the demo helper, provider extension, SecurityAgent plug-in, and installer targets.
After an explicit live-testing checkpoint, run the demo unit tests with:
Scripts/validate-live-demo-tests.shThis may launch the app test host and collect module-backed read-only demo details for every launch-safe capability action, but it does not install helpers, mutate authorization policy, present the lock screen, or attach to protected processes.