Short answer: among the 404 public Sylius plugins that are still active, 59.4% have a stable release compatible with Sylius 2. Weighted by monthly downloads, that rises to 83%, which still leaves 17% of installs on plugins that are not ready under their current name.
Sylius 1.14 security support ends on December 31, 2026. A shop can only upgrade once every plugin it uses has a compatible release, so I classified every package of type sylius-plugin on Packagist (802 of them, data from November 14, 2026) from the version constraints of each release. The full report, the dataset and the scripts are on Zenodo: https://doi.org/10.5281/zenodo.24224419
Method in one paragraph
Only constraints on packages that follow Sylius numbering count (sylius/sylius and the 41 sub-packages it replaces). A release is compatible if its constraints accept at least one of the 53 stable Sylius 2 releases, if it was published after Sylius 2.0.0 (November 12, 2024), and if at least one constraint names Sylius 2 explicitly. That last rule matters: an open-ended >=1.9 accepts Sylius 2 by accident. My first version of the study missed it and counted three plugins as compatible when they are not; version 1.1 fixes it.
Results
| Category | All (782) | Active (404) | Share of monthly downloads |
|---|---|---|---|
| Stable Sylius 2 release | 247 (31.6%) | 240 (59.4%) | 83.0% |
| Pre-release only | 13 | 12 | 4.4% |
| Development branch only | 32 | 11 | 1.6% |
| Replaced by another package | 5 | 3 | 3.6% |
| Deprecated, no successor | 3 | 1 | 1.2% |
| Sylius 1 only | 482 (61.6%) | 137 | 6.2% |
338 of the "Sylius 1 only" plugins have had no release since 2024. They are not coming.
Three things worth knowing
Renamed packages. BitBag's CMS and Wishlist plugins moved to the Sylius organisation (sylius/cms-plugin, sylius/wishlist-plugin). The FLUX-SE Payum Stripe plugin points to the official Stripe plugin, and Mollie did the same. Upgrading means switching packages, not bumping a constraint.
No successor. sylius/admin-order-creation-plugin (6,000+ downloads a month) is deprecated by the Sylius team with no open-source replacement.
Adoption is accelerating. 65 plugins shipped their first Sylius 2 compatible release between October 1 and November 14, 2026, more than in any full quarter before.
Check your own project
Sylius Upgrade Analyzer (MIT, which I maintain) checks every plugin in your composer.json against the target version, along with the rest of the breaking changes. The Docker image runs whatever PHP version your project is on:
docker run --rm -v "$PWD:/project" ghcr.io/pierrearthurdemengel/sylius-upgrade-analyzer Disclosure: I do Sylius 1 to 2 migrations for a living. If you want a second pair of eyes on your upgrade: https://creation-site-pro.fr/en/sylius-2-upgrade?utm_source=devto&utm_campaign=plugin-study
