PAGES
← all tools
◆ Patch Management

AutoPkg

v3.0.0 open-source

Free plan: not checked yet · Open source: yes

Starting price: not checked yet

AutoPkg is an automation framework for macOS software packaging and distribution, preparing third-party software for mass deployment to managed clients.

What you can do now

Checking 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.

How AutoPkg helps

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

all 16 features, with the evidence for each →

Languages

Not documented

Features

16 capabilities

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.

Compare with peers →

What AutoPkg offers you

  • Command-line interface4
  • CI/CD pipeline integration1
  • JSON data export1

All capabilities 16 capabilities
Audit vulnerability checks Detects hard-coded credentials, path traversal markers, insecure URLs, weak checksum algorithms, and missing verifiers. 3 releases · first seen Sep 2026
Cache management Provides 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 handling Unifies and persists download metadata (ETag, Last-Modified, file size) using sidecar files for improved reliability. 2 releases · first seen Sep 2026
CI gating Returns 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 verification Requires explicit requirement strings and authority names for verification, defaulting to strict mode for app bundles. 2 releases · first seen Sep 2026
Path confinement Confines 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 caching Caches 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 validation Enforces strict type checking for boolean inputs and treats typoed keys in configuration as errors. 2 releases · first seen Sep 2026
Artifact caching Automatically copies external packages into the recipe's download folder for use within the cache environment. 1 release · first seen Sep 2026
Audit check discovery Prints available audit checks and their severities for review. 1 release · first seen Sep 2026
Audit filtering Allows 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 formatting Provides JSON output format for machine-readable audit findings with severity ordering. 1 release · first seen Sep 2026

Also counts toward: JSON data export

Hash computation Computes MD5, SHA1, and SHA256 hashes of downloaded files on-demand for use by subsequent processors. 1 release · first seen Sep 2026
Processor resolution Validates fully-qualified processor references and fails if the target recipe or processor file is not found. 1 release · first seen Sep 2026
Recipe trust integrity Includes preinstall and postinstall script content in recipe override trust verification to detect unauthorized changes. 1 release · first seen Sep 2026
Security deprecation notifications Warns 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.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median 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.

Score cards are part of every paid plan.

See plans →

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.

Checking release-note history…

Explore the full chart →

Releases

Show

26 entries

  1. September 20261
  2. February 20261
  3. August 20251
  4. May 20251
  5. December 20221
  6. August 20221
  7. March 20211
  8. August 20201
  9. May 20201
  10. February 20201
  11. November 20191
  12. September 20191
  13. May 20191
  14. March 20181
  15. September 20171
  16. April 20171
  17. November 20161
  18. March 20161
  19. September 20151
  20. July 20151
  21. December 20141
  22. August 20141
  23. July 20141
  24. May 20141
  25. January 20141
  26. September 20131
    Show

    26 entries

    Project health

    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.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 67% of issues opened, last 12 months
    5. Median time to close 305 days first maintainer reply 11 days
    6. Open backlog 54 of 596 issues ever filed
    1. Issues opened / month 2 · 0 communitymaintainers
    2. Open backlog 54
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.