Agent skill · Audited from source
macos-auto-update
skill · fayazara/macos-app-skillsLicence not declaredAudited 20 Oct 2026 · source d0a46479b2fe
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d0a46479b2fe and observed filesystem access and no hard-coded secrets. What it does: Add Sparkle auto-update support to a native macOS app. Use this skill whenever the user wants to add auto-updates, implement Sparkle, set up an appcast feed, add "Check for Updates" to their app, or integrate automatic…
Cite
Cite this page
ModelsAtlas. “macos-auto-update (fayazara/macos-app-skills)”. Retrieved 20 Oct 2026. https://modelsatlas.com/skills/fayazara/macos-auto-update
Trust audit
Audit 0.4.1 · source read 20 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemDeclared1 observation
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 1 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass, no license.
Findings (1)
LOWInventory / provenanceinv.no_license
- Why
- no LICENSE file and no repo licence
- Fix
- add a licence
Audit 0.4.1 · source sha d0a46479b2fe · 20 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherfayazara GitHub userOwner of the repository this skill is read from
- Source folderfayazara/macos-app-skillsThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdictd0a46479b2feA new audit runs when the source changes
- Repository statusNot archivedLast push 145 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Add Sparkle auto-update support to a native macOS app. Use this skill whenever the user wants to add auto-updates, implement Sparkle, set up an appcast feed, add "Check for Updates" to their app, or integrate automatic…
---
name: macos-auto-update
description: >
Add Sparkle auto-update support to a native macOS app. Use this skill whenever the user wants to
add auto-updates, implement Sparkle, set up an appcast feed, add "Check for Updates" to their app,
or integrate automatic update checking. Also trigger when the user mentions Sparkle, appcast,
SUFeedURL, EdDSA signing, or update notifications. This covers the full setup: adding the Sparkle
SPM dependency, creating the UpdaterManager singleton, wiring it into the app delegate and UI,
configuring Info.plist, and generating the initial appcast.xml.
---
# Sparkle Auto-Update for macOS Apps
This skill adds [Sparkle](https://sparkle-project.org/) auto-update support to a native macOS app. Sparkle is the standard open-source framework for macOS app updates outside the Mac App Store.
## Overview
The implementation has 4 parts:
1. **SPM dependency** -- add the Sparkle package to the Xcode project
2. **UpdaterManager.swift** -- a singleton that wraps `SPUStandardUpdaterController`
3. **Info.plist keys** -- `SUFeedURL` and `SUPublicEDKey`
4. **UI integration** -- "Check for Updates" button in settings/menu bar
## Step 1: Add Sparkle via SPM
In Xcode: File > Add Package Dependencies > enter:
```
https://github.com/sparkle-project/Sparkle
```
Use the "Up to Next Major Version" rule with `2.0.0`. Add the `Sparkle` framework to your app target.
Or add it to `Package.swift` if your project uses one:
```swift
.package(url: "https://github.com/sparkle-project/Sparkle", from: "2.0.0")
```
## Step 2: Create UpdaterManager.swift
Copy `references/UpdaterManager.swift` into your project. This is a singleton that:
- Creates `SPUStandardUpdaterController` early (before `applicationDidFinishLaunching` returns)
- Publishes `canCheckForUpdates` for UI binding
- Exposes `automaticallyChecksForUpdates` toggle
- Skips all update logic in DEBUG builds (so you don't get update prompts during development)
- For menu-bar-only apps: temporarily switches to `.regular` activation policy before showing the update window
The key design decisions in this file:
- **`startingUpdater: false`** in the initializer, then calling `start()` explicitly in `applicationDidFinishLaunching`. This gives you control over timing.
- **DEBUG guards** on `start()` and `checkForUpdates()`. Sparkle should never run in debug builds -- it would try to update your debug app with a release build.
- **`ObservableObject` with `@Published`** (not `@Observable`) because we need the Combine `publisher(for:)` bridge from Sparkle's KVO.
## Step 3: Configure Info.plist
Add these keys to your app's `Info.plist`:
```xml
<key>SUFeedURL</key>
<string>https://raw.githubusercontent.com/OWNER/REPO/main/appcast.xml</string>
<key>SUPublicEDKey</key>
<string>YOUR_PUBLIC_EDDSA_KEY_HERE</string>
<key>SUEnableInstallerLauncherService</key>
<true/>
```
### Generating EdDSA Keys
Sparkle uses EdDSA (Ed25519) signing. Generate a keypair:
```bash
# Find generate_keys in your DerivedData after building the project with Sparkle
find ~/Library/Developer/Xcode/DerivedData -name "generate_keys" -type f 2>/dev/null | head -1
```
Run it:
```bash
/path/to/generate_keys
```
This prints the public key and stores the private key in your Keychain. Put the public key in `SUPublicEDKey` in Info.plist. The private key stays in Keychain and is used by `sign_update` during release.
## Step 4: Wire Into App
### App Delegate
```swift
final class AppDelegate: NSObject, NSApplicationDelegate {
private let updaterManager = UpdaterManager.shared
func applicationDidFinishLaunching(_ notification: Notification) {
updaterManager.start()
}
}
```
The `UpdaterManager.shared` property must be accessed early so the `SPUStandardUpdaterController` is created before the app finishes launching. Referencing it in the `AppDelegate` property ensures this.
### Settings UI (About Pane)
```swift
struct AboutSettingsPane: View {
@ObservedObject private var updaterManager = UpdaterManager.shared
var body: some View {
Form {
Section("Updates") {
Toggle(isOn: Binding(
get: { updaterManager.automaticallyChecksForUpdates },
set: { updaterManager.automaticallyChecksForUpdates = $0 }
)) {
Text("Automatically check for updates")
}
Button("Check for Updates...") {
updaterManager.checkForUpdates()
}
.disabled(!updaterManager.canCheckForUpdates)
}
}
.formStyle(.grouped)
.scrollContentBackground(.hidden)
}
}
```
### Menu Bar (optional)
```swift
Button {
updaterManager.checkForUpdates()
} label: {
Label("Check for Updates...", systemImage: "arrow.down.circle")
}
.disabled(!updaterManager.canCheckForUpdates)
```
## Step 5: Create Initial Appcast
Create an `appcast.xml` at the root of your repo. It starts empty and gets populated by your release process:
```xml
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>YourApp</title>
<description>Most recent changes for YourApp.</description>
<language>en</language>
</channel>
</rss>
```
Host this file on GitHub (raw URL) or any static file host. The URL must match `SUFeedURL` in Info.plist.
## Menu-Bar-Only Apps
If your app runs as `.accessory` (no Dock icon), Sparkle's update window won't appear unless you temporarily switch to `.regular`. The reference `UpdaterManager` handles this in `checkForUpdates()`:
```swift
func checkForUpdates() {
NSApp.setActivationPolicy(.regular)
NSApp.activate(ignoringOtherApps: true)
controller.checkForUpdates(nil)
}
```
The app reverts to `.accessory` when the update window closes (handled by your existing activation policy manager).
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit d0a4647
npx skills add fayazara/macos-app-skills
git clone https://github.com/fayazara/macos-app-skills git -C macos-app-skills checkout d0a46479b2fe
Commands as the repository documents them: shown, never run by us. Our verdict covers commit d0a46479b2fe only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Claude Code | Mentioned in its text, not tested | Skills for Claude Code · About Claude Code |
| Cursor | Mentioned in its text, not tested | Skills for Cursor · About Cursor |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
d0a46479b2fe
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/fayazara/macos-auto-update/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
obra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Add this badge to your README
[](https://modelsatlas.com/skills/fayazara/macos-auto-update/)
<a href="https://modelsatlas.com/skills/fayazara/macos-auto-update/"><img src="https://modelsatlas.com/skills/fayazara/macos-auto-update/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about macos-auto-update
What does the macos-auto-update skill do?
Is macos-auto-update safe to install?
What can macos-auto-update access on my machine?
Which assistants does macos-auto-update work with?
How current is this page?
Sources
- github.com/fayazara/macos-app-skills — the audited source at commit d0a46479b2fe and every finding aboveObserved · 20 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the macos-auto-update skill do?
- Is macos-auto-update safe to install?
- What can macos-auto-update access on my machine?