Patcher
Usage¶
The underlying commands that drive Patcher.
Pull patch data out of Jamf and write it as Excel, PDF, HTML, and JSON reports you can share. Reach for it whenever you need a shareable snapshot of fleet patch coverage.
Filter, rank, and trend patch data to surface the titles that need attention, either against a single report or across every cached dataset over time. Reach for it to answer “which titles are lagging?”
Restore Patcher’s persisted state granularly: credentials, UI configuration, cached data, or all of it. Reach for it to fix a typo’d credential, clear the cache, or start over with the setup wizard.
Compare patch state between two points in time to see what was added, removed, or changed. Reach for it to keep a paper trail of every patch-coverage shift between two specific moments.
Find apps where upstream sources disagree on what “latest” means, the strongest signal that a label has silently fallen behind. Reach for it as a low-cost canary for stuck upstream sources.
Query the stitched upstream catalog (versions, download URLs, drift, generated labels) over plain HTTP from any language. Reach for it when you need catalog data outside Python, or without standing up your own ingestion.