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