In a filing, WP Engine asks a court in Northern California to issue a preliminary injunction and restore its access to the WordPress.org open source repository
In recent weeks, Mullenweg has backed up demands that WP Engine … X: Ivan Mehta / @indianidle : Automattic's response: “Automattic vehemently denies WP Engine's allegations—which are gross mischaracterizations of reality—and reserves all of our rights. Automattic is confident in our legal position and will vigorously litigate against this baseless filing, as well as Ivan Mehta / @indianidle : WP Engine filed an injunction today to get its access restored to the https://wordpress.org/ repository. In a declaration, WP Engine CEO Heather Brunner said, “Until very recently, I had been under the impression that https://wordpress.org/ was associated with or owned by the Forums: r/technology : WP Engine asks court to stop Matt Mullenweg from blocking access to WordPress resources
Context & Ripple Effects
The access fight escalated from reciprocal trademark cease-and-desist letters into WP Engine's broader California lawsuit against Automattic and Matt Mullenweg. Mullenweg had characterized the conflict as a long-running effort to reach a licensing deal with WP Engine, while WP Engine framed the conduct as abuse of control over WordPress resources.
This injunction request makes repository access the immediate operational issue in a dispute that also spans trademarks and licensing. The later court order barring continued access restrictions underscores why access to shared project infrastructure became central to the case.
First-order effects
- WP Engine asks the court to restore its WordPress.org repository access and prevent Automattic and Mullenweg from continuing to block it while the underlying litigation proceeds.
- Automattic must defend its ability to restrict a commercial WordPress host's use of project resources, alongside its denial of WP Engine's allegations.
Second-order effects
- The filing turns a private licensing and trademark dispute into a test of how reliably companies built around WordPress can depend on WordPress.org-controlled infrastructure.
- Other WordPress businesses may scrutinize their operational exposure to project-controlled repositories and plugins when commercial disputes arise.
Third-order effects
- If courts constrain unilateral restrictions on shared open-source infrastructure, project stewards may face clearer limits on using access controls as leverage in disputes with ecosystem companies.
- The case could sharpen the distinction between open-source code availability and governance over the services, trademarks, and distribution channels surrounding that code.
The trend: Open-source ecosystems are increasingly confronting whether control of shared infrastructure can be separated from commercial and trademark disputes with companies that build on the project.