The section your link pointed to isn't on AutoPkg's page any more, so we've brought you to the top.
AutoPkg is an automation framework for macOS software packaging and distribution, preparing third-party software for mass deployment to managed clients.
Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
AutoPkg is an open-source automation framework for macOS software packaging and distribution, and it runs as a command-line tool intended for patch-management and third-party-patching practitioners. The tool requires no payment, and users define required deployment steps in YAML or plist Recipe formats. Its documentation positions it alongside Munki, and it has seen 415 commits in the past year with 79 contributors.
AutoPkg is an automation framework for macOS software packaging and distribution, preparing third-party software for mass deployment to managed clients.
Which third-party applications need preparing for deployment?
runs shared recipes that download updates, unpack archives, apply site-specific configuration and versioning, repair installer scripts, and create packages or disk images for distribution systems
How can I repeat the deployment preparation my applications require?
executes the ordered steps defined in each recipe instead of relying on manually repeated application-specific tasks
What package metadata does my managed-software system receive?
creates distribution artifacts and customizes their metadata with site-specific data, post-install scripts, version information, and minimum operating-system details where the recipe supplies it
Which recipes contain deployment or security problems before I run them?
audits recipes for issues such as missing code-signature verification, unsafe paths, insecure URLs, weak checksums, embedded credentials, and untrusted installer modifications, reporting findings by severity
Can I verify that downloaded software is the expected file?
records download change metadata and can calculate file hashes for later processing, but the available material does not establish that hashes are independently checked against a trusted expected value
Which recipe or package changes require me to review trust?
verifies recipe trust information, including package preinstall and postinstall script changes, and warns when code-signature verification is disabled or required signer constraints are absent
Built from AutoPkg's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+Audit vulnerability checksNot checked yet · Date unknownDetects hard-coded credentials, path traversal markers, insecure URLs, weak checksum algorithms, and missing verifiers.3 releases · first seen Sep 2026▸
+Cache managementNot checked yet · Date unknownProvides commands to clear cached files for specific recipes or all recipes, with preview and verbosity options.1 release · 1 other source · first seen Sep 2026▸
Also counts toward: Command-line interface
+Cache metadata handlingNot checked yet · Date unknownUnifies and persists download metadata (ETag, Last-Modified, file size) using sidecar files for improved reliability.2 releases · first seen Sep 2026▸
+CI gatingNot checked yet · Date unknownReturns specific exit codes based on audit finding severities to support continuous integration pipelines.1 release · 1 other source · first seen Sep 2026▸
Also counts toward: CI/CD pipeline integration, Command-line interface
+Code signature verificationNot checked yet · Date unknownRequires explicit requirement strings and authority names for verification, defaulting to strict mode for app bundles.2 releases · first seen Sep 2026▸
+Path confinementNot checked yet · Date unknownConfines file paths and cache directories to intended locations, rejecting path traversal attempts or outputs outside allowed bounds.2 releases · first seen Sep 2026▸
+Recipe resolution cachingNot checked yet · Date unknownCaches recipe and override indices to disk, significantly speeding up recipe identification on systems with many repositories.1 release · 1 other source · first seen Sep 2026▸
Also counts toward: Command-line interface
+Strict validationNot checked yet · Date unknownEnforces strict type checking for boolean inputs and treats typoed keys in configuration as errors.2 releases · first seen Sep 2026▸
+Artifact cachingNot checked yet · Date unknownAutomatically copies external packages into the recipe's download folder for use within the cache environment.1 release · first seen Sep 2026▸
+Audit check discoveryNot checked yet · Date unknownPrints available audit checks and their severities for review.1 release · first seen Sep 2026▸
+Audit filteringNot checked yet · Date unknownAllows selecting specific checks to run or skip via command-line flags.1 release · first seen Sep 2026▸
Also counts toward: Command-line interface
+Audit output formattingNot checked yet · Date unknownProvides JSON output format for machine-readable audit findings with severity ordering.1 release · first seen Sep 2026▸
Also counts toward: JSON data export
+Hash computationNot checked yet · Date unknownComputes MD5, SHA1, and SHA256 hashes of downloaded files on-demand for use by subsequent processors.1 release · first seen Sep 2026▸
+Processor resolutionNot checked yet · Date unknownValidates fully-qualified processor references and fails if the target recipe or processor file is not found.1 release · first seen Sep 2026▸
+Recipe trust integrityNot checked yet · Date unknownIncludes preinstall and postinstall script content in recipe override trust verification to detect unauthorized changes.1 release · first seen Sep 2026▸
+Security deprecation notificationsNot checked yet · Date unknownWarns users when code signature verification is disabled via configuration or environment variables.1 release · first seen Sep 2026▸
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for AutoPkg, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail AutoPkg puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Issue, contributor and maintainer activity in autopkg/autopkg, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed67%of issues opened, last 12 months
Median time to close305 daysfirst maintainer reply 11 days
Open backlog54of 596 issues ever filed
Issues opened / month2 · 0communitymaintainers
Open backlog54
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
other 100%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.