Maxx the Craftsman Marmot

your software, tended.

FIXXR is a macOS endpoint lifecycle intelligence platform. It answers four questions about every app on your Mac: how it got here, what it touches, how it updates, and how to remove it completely. This is the story of why it exists, what it stands on, and how it earns your trust.


Nobody watches
the workshop.

Somewhere between 60 and 70 percent of the applications on a typical Mac update outside the App Store. There is no unified way to know what is installed, whether it is current, where it came from, or how to remove it cleanly. The tools that tried to solve this are gone.

  • ~65%

    Apps update outside the App Store

    Sparkle feeds, vendor websites, embedded auto-updaters, Homebrew Cask. Each with its own mechanism, none with a shared view.

  • 0

    Unified audit trail

    No native macOS tool tells you when an app updated, from where, or whether the signing identity changed between versions.

  • 238

    Apps lost their update path overnight

    When MacUpdater's backend went dark in January 2026, hundreds of apps lost their only managed update channel.

The landscape in 2026

The space is fragmented. Each tool covered a slice. None covered the full lifecycle.

  • Jan 2026 MacUpdater backend discontinued. Detection-only; no provenance, no removal.
  • Ongoing Homebrew Cask covers ~4,800 apps. Excellent for what it knows. Silent on the rest.
  • Ongoing Updatest detects outdated apps via the App Store. No third-party coverage.
  • Ongoing UninstallPKG reads PKG receipts for clean removal. No update or provenance story.
  • 2026 FIXXR attempts to unify: scan, verify, update, record, and remove. One protocol across all mechanisms.

Four questions about
every application.

FIXXR models each app as a node in a lifecycle graph. The graph answers the questions that macOS does not surface natively, and that no single existing tool covers end to end.

01
🔎

How did it get here?

Provenance tracking. Where was the binary downloaded from? Which CDN? Was it installed via Homebrew, drag-and-drop, or a PKG installer? Is the signing identity consistent with what was there before?

02
📁

What does it touch?

Filesystem footprint mapping. Which directories does it own? What launch agents, preference panes, kernel extensions, or helper tools did it install beyond the .app bundle?

COMING SOON
03
🔄

How does it update?

Orchestrates Homebrew Cask, Sparkle, the Mac App Store, and native auto-updaters. Maxx routes each app to the right mechanism automatically, with TeamID verification before every install.

04
🗑

How do you remove it completely?

Clean Remove reads PKG receipts, discovers scattered files, and removes everything the app left behind. Not just the .app bundle -- the launch agents, the caches, the preference files.


Nothing here was built
from scratch.

FIXXR exists because decades of open-source and platform work came before it. These are the projects and standards that make the lifecycle graph possible. Respect where it is due.

Sparkle

The update framework that thousands of macOS apps use to ship new versions. FIXXR reads Sparkle's appcast feeds to discover what is available.

sparkle-project.org
🍺

Homebrew

The missing package manager for macOS. FIXXR delegates to Homebrew Cask for apps it knows, and cross-references its catalog for provenance data.

brew.sh
🗃

SQLite

The local database engine. Every provenance record, every audit trail event, every app observation is stored in WAL-mode SQLite on your machine.

sqlite.org
🐍

Python

FIXXR's CLI is pure Python standard library. No pip, no venv, no dependency chain. Runs on the Python 3 that ships with Xcode Command Line Tools.

python.org
🛠

SwiftUI

The menu bar dashboard that gives Maxx a face. Native macOS interface, built with SwiftUI and AppKit, signed with a Developer ID certificate.

developer.apple.com/swiftui

Cloudflare

Workers host the community catalog API. D1 stores the shared dataset. Pages serves this website. Edge-first infrastructure, no origin servers.

cloudflare.com
🔒

Apple Notarization

Apple scans every FIXXR release for malware before it reaches your Mac. Notarization plus Developer ID signing is the baseline trust gate.

developer.apple.com

Sigstore

Keyless code signing for the supply chain. FIXXR uses Sigstore-compatible attestations to prove build provenance without managing long-lived keys.

sigstore.dev
🛑

OSV.dev

Open Source Vulnerability database. Maxx queries OSV.dev to check every installed app version against known CVEs, cached locally to avoid noise.

osv.dev
📜

Objective Development IAP

Their Internet Access Policy model inspired FIXXR's privacy approach: declare exactly what data you collect, and be auditable against that declaration.

obdev.at/iap

How FIXXR
earns your trust.

Trust is not a toggle. It is a chain of verifiable claims, each independently auditable. Here is the full chain, from your machine to the community catalog and back.

01

Local-first data

Everything FIXXR knows lives in a SQLite database on your machine at ~/.fixxr/fixxr.db. Your full inventory, all provenance events, all audit logs. Nothing is stored remotely unless you explicitly opt in.

LOCAL ONLY
02

Privacy filter: 8 PUBLISH_FIELDS

If you opt in to the community catalog, only 8 fields ever leave your machine: bundle_id, app_name, latest_version, download_url, sha256, feed_url, homepage_url, update_mechanism. Enforced at the adapter layer in code, not policy.

OPT-IN ONLY
03

Apple Developer ID signing

Every FIXXR release is signed with an Apple Developer ID certificate. macOS Gatekeeper verifies the signature before the app is allowed to run. The TeamID is consistent across all releases.

VERIFIABLE
04

Apple Notarization

Before distribution, every build is submitted to Apple's notarization service, which scans for malware and verifies the Developer ID. The notarization ticket is stapled to the DMG.

APPLE VERIFIED
05

GitHub Attestations

CI builds produce cryptographic attestations via GitHub's artifact attestation feature. You can verify that the binary you downloaded was produced by the CI pipeline in the public repository, not by a compromised developer machine.

VERIFIABLE
06

SBOM (Software Bill of Materials)

Each release ships with a machine-readable inventory of every dependency. Since the Python CLI uses only stdlib, the SBOM is short. But it exists, and you can audit it.

PUBLISHED
07

SECURITY.md and responsible disclosure

The repository includes a SECURITY.md with clear instructions for reporting vulnerabilities. Response commitment, scope, and a PGP key for encrypted disclosure.

PUBLISHED

No telemetry. No ads.
No subscription.

FIXXR is a community utility, not a business. The value is the shared catalog. If the project grows, it becomes a Verein -- a Swiss non-profit association -- governed by its members, not by investors.

🚫

No telemetry

No analytics. No tracking pixels. No crash reporters phoning home. Your usage patterns stay on your machine.

🚫

No ads or tracking

No advertising. No affiliate links. No user profiling. The software does not monetize your attention or data.

🚫

No subscription

No premium tier. No time-limited trial. No feature gates. Every capability is available to every user.

The Verein model. If FIXXR grows beyond a single maintainer, governance moves to a Verein -- a Swiss non-profit association. Open membership, transparent accounts, democratic decision-making. The protocol and the catalog belong to the community. The software stays MIT-licensed. Infrastructure costs are funded by voluntary membership dues, not by extracting value from users.

The workshop charges no admission. The tools are free. The catalog is shared. If you tend the library, the library tends you back.


The craftsman
in the workshop.

Maxx the Craftsman Marmot, tending the software workshop
Maxx is a marmot who keeps your software workshop tidy. He scans the neighborhood, checks the locks, and keeps everything current. He never phones home without asking. He never installs without explaining. He is a craftsman, not a salesman.

He reads every Sparkle feed, cross-references every TeamID, and records every provenance event in a local ledger you own. When something looks wrong -- a signing identity that changed, a CDN that drifted, a hash that does not match consensus -- he stops and asks. The workshop runs on trust, and trust runs on transparency.
Download FIXXR View on GitHub