Some links on this page are affiliate links. We may earn a commission when you click through and make a purchase, at no additional cost to you.
When WP Engine announced its acquisition of WPackagist on March 12, the WordPress developer community braced for impact. As a critical piece of open source infrastructure, the move raised concerns about corporate control over tools essential to the ecosystem. However, just four days later, a community-driven alternative, WP Packages, launched as a fully independent Composer repository for WordPress plugins and themes. Built by Ben Word and the Roots team, WP Packages is already proving that open source innovation thrives when it operates in the open.
Key Takeaways
- WP Packages replaces WPackagist as a fully open source Composer repository for WordPress plugins and themes.
- It features faster dependency resolution, better metadata, and shorter sync cycles.
- Migrating from WPackagist to WP Packages can be done in minutes using simple commands or a script.
- The project is publicly hosted on GitHub and funded through community sponsorships.
- WP Packages prioritizes transparency by making its code and deployment process public.
What Is WP Packages?
WP Packages, formerly known as WP Composer, provides WordPress developers with a modern Composer repository for installing and updating plugins and themes. Composer, PHP’s dependency manager, is widely used in professional WordPress workflows to manage project dependencies efficiently. WP Packages builds on and improves the functionality of WPackagist, which served the ecosystem for over a decade but struggled in its later years due to deferred maintenance and limited updates.
Ben Word, the developer behind Roots (known for Bedrock, Sage, and Trellis), had already started building WP Packages months before WP Engine’s acquisition of WPackagist. The acquisition accelerated the timeline, and WP Packages launched on March 16 with a clear commitment to transparency and community control. Every plugin and theme from the WordPress.org directory is available through WP Packages.
Why WP Packages Is Better
WP Packages doesn’t just replace WPackagist—it improves on it in meaningful ways. The repository supports Composer v2’s metadata-url protocol, which significantly reduces dependency resolution times compared to WPackagist’s outdated provider-includes approach. In practice, resolving dependencies for 10 plugins takes just 0.7 seconds with WP Packages versus 12.3 seconds on WPackagist.
Additional enhancements include:
- CDN caching with public cache headers for faster delivery.
- Immutable, content-addressed per-package files.
- Cleaner package naming conventions (e.g.,
wp-plugin/andwp-theme/). - Comprehensive metadata, including author names, descriptions, and homepage URLs.
- Sync cycles every five minutes, drastically faster than WPackagist’s 90-minute updates.
How to Migrate
Switching from WPackagist to WP Packages is straightforward. Developers can migrate manually with a few terminal commands:
- Remove existing WPackagist packages:
composer remove wpackagist-theme/twentytwentyfive - Remove the WPackagist repository and add WP Packages:
composer config --unset repositories.wpackagist && composer config repositories.wp-composer composer https://repo.wp-packages.org - Require packages with the new naming convention:
composer require wp-theme/twentytwentyfive
Alternatively, developers can use a migration script provided by Roots:
curl -sO https://raw.githubusercontent.com/roots/wp-packages/main/scripts/migrate-from-wpackagist.sh && bash migrate-from-wpackagist.shProjects using Bedrock are already configured to use WP Packages by default, and Roots offers additional tools like the WP Packages Changelog Action for GitHub workflows to track dependency updates.
What This Means for WordPress Users
WP Packages represents a significant win for the WordPress community. Developers now have access to a faster, more transparent, and community-controlled Composer repository. This shift mitigates the risks associated with corporate ownership of critical infrastructure, ensuring the ecosystem remains open and adaptable.
For agencies and developers relying heavily on Composer workflows, migrating to WP Packages is a no-brainer. The improved performance alone—17x faster cold resolves—is worth the effort. Additionally, the project’s public codebase and deployment configuration empower users to understand and even fork the repository if needed.
WP Packages signals a broader trend in WordPress: community-driven tools are not just viable alternatives to corporate solutions; they are often superior. As more businesses and sponsors like Kinsta and WordPress.com invest in open source projects, we can expect similar initiatives to emerge.
Frequently Asked Questions
What is WP Packages?
WP Packages is an open source Composer repository for WordPress plugins and themes, providing faster updates and better metadata compared to WPackagist.
How do I migrate to WP Packages?
Migration involves removing WPackagist repositories, adding WP Packages, and updating package naming conventions. A script is available to automate the process.
Is WP Packages free to use?
Yes, WP Packages is completely free and open source. It is funded through community sponsorships and is hosted publicly on GitHub.
Does WP Packages include all WordPress.org plugins and themes?
Yes, WP Packages mirrors the entire WordPress.org directory, ensuring all free plugins and themes are available.
Who sponsors WP Packages?
Current sponsors include Carrot, Kinsta, WordPress.com, and Itineris, among others.
