WPackagist vs WP Composer: Managing WordPress Plugins & Themes with Composer in 2026

In the fast-evolving WordPress ecosystem, modern developers increasingly rely on Composer — PHP’s powerful dependency manager — to handle not just libraries, but also plugins and themes. This approach ensures version control, reproducibility, automated updates, and cleaner deployments without manual ZIP downloads or FTP chaos.

Until recently, WPackagist was the undisputed go-to public mirror for WordPress.org plugins and themes. But in March 2026, WP Engine acquired it, sparking community discussions about independence, corporate control, and long-term reliability. Almost immediately, the Roots team (creators of Bedrock) launched WP Composer — a fully independent, community-funded alternative built for speed and modern workflows.

This post compares the two head-to-head, including live URLs, GitHub repos, documentation, pros/cons, basic setup examples, and migration notes — so you can decide which fits your projects best in 2026 and beyond.

What Is Composer for WordPress Plugins & Themes?

Composer lets you declare dependencies in a composer.json file and install them with one command. For WordPress, the composer/installers plugin routes plugins and themes to the correct wp-content/ subfolders. Since WordPress.org items aren’t on Packagist, dedicated mirrors provide the necessary Composer metadata.

Both WPackagist and WP Composer scan WordPress.org’s SVN repo regularly to keep packages up-to-date — making them essential for professional, Git-based WordPress development (especially Bedrock-based projects).

WPackagist: The Long-Standing Classic

Live Website: https://wpackagist.org/

Composer Repository URL: https://wpackagist.org

GitHub: https://github.com/outlandishideas/wpackagist

Documentation: Included on the homepage with examples; now maintained by WP Engine post-acquisition (hourly SVN scans continue).

Basic How-To

Add to your composer.json:

{
    "repositories": [
        {
            "name": "wpackagist",
            "type": "composer",
            "url": "https://wpackagist.org",
            "only": ["wpackagist-plugin/*", "wpackagist-theme/*"]
        }
    ],
    "require": {
        "composer/installers": "^2.2",
        "wpackagist-plugin/akismet": "dev-trunk",
        "wpackagist-plugin/advanced-custom-fields": ">=6.7.1",
        "wpackagist-theme/frost": "*"
    },
    "extra": {
        "installer-paths": {
            "wp-content/plugins/{$name}/": ["type:wordpress-plugin"],
            "wp-content/themes/{$name}/": ["type:wordpress-theme"]
        }
    }
}

Run composer update (or composer install).

Pros

• Over a decade of reliability — covers almost every plugin/theme on WordPress.org
• Free, with hourly updates backed by WP Engine infrastructure
• Massive existing adoption in legacy and current projects

Cons

• Now owned by WP Engine (private-equity backed), raising independence concerns for some
• Slower dependency resolution on Composer v2 due to older metadata format
• Longer package prefixes (wpackagist-plugin/)

WP Composer: The Modern Community Alternative

Live Website: https://wp-composer.com/

Composer Repository URL: https://repo.wp-composer.com

GitHub: https://github.com/roots/wp-composer

Documentation: Comprehensive guides + migration script on the site; community-funded via GitHub Sponsors.

Basic How-To

Add to your composer.json (ideal for new or Bedrock projects):

{
    "repositories": [
        {
            "name": "wp-composer",
            "type": "composer",
            "url": "https://repo.wp-composer.com",
            "only": ["wp-plugin/*", "wp-theme/*"]
        }
    ],
    "require": {
        "composer/installers": "^2.2",
        "wp-plugin/woocommerce": "^10.0",
        "wp-theme/twentytwentyfive": "^1.0"
    },
    "extra": {
        "installer-paths": {
            "wp-content/plugins/{$name}/": ["type:wordpress-plugin"],
            "wp-content/themes/{$name}/": ["type:wordpress-theme"]
        }
    }
}

Run composer update. Also supports roots/wordpress for core.

Pros

• Fully independent and community-funded — no corporate ownership
• Significantly faster (up to 17×) dependency resolution thanks to modern Composer v2 metadata
• Cleaner, shorter package names (wp-plugin/ & wp-theme/)
• Seamless Bedrock integration + official one-click migration from WPackagist
• Actively developed by the Roots team

Cons

• Very new (launched March 2026) — adoption still growing
• Relies on ongoing community sponsorship for sustainability

Head-to-Head Comparison

Our Recommendation: For new projects, go with WP Composer for better speed, cleaner naming, and full independence. Existing WPackagist setups can migrate quickly using the Roots-provided script.

Are There Other Options?

No other public mirrors match the scale and automatic coverage of WPackagist or WP Composer for free WordPress.org plugins/themes.

For premium, private, or custom plugins/themes, common approaches include:

• VCS repositories: Point Composer directly to private GitHub, Bitbucket, or GitLab repos containing a valid composer.json (great for custom or purchased items with tokens for private access).
• Self-hosted repositories: Use tools like Satis (static Composer repo generator) or the SatisPress plugin to create your own dynamic/private mirror from installed plugins/themes.
• Official vendor support: Some premium plugins (e.g., ACF Pro, Gravity Forms) offer dedicated Composer repositories via authentication tokens — add them as additional repositories in composer.json.

These options complement — rather than replace — the two main public mirrors.

Ready to Level Up Your WordPress Workflow?

Whether you stick with WPackagist’s proven track record or switch to WP Composer’s modern, independent edge, using Composer for plugins and themes brings professional-grade consistency and security to WordPress projects.

Need assistance migrating repositories, optimizing a Bedrock setup, building high-performance custom plugins, or developing a full bespoke WordPress site? Our team has been mastering these workflows since 2011.