OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Joomla and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Two security releases ship the same day, and 6.2 finally clears alpha
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
Pimcore is shipping a security advisory almost every week.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
Joomla is running three branches at once: 5.4.x as the maintenance line, 6.1.x as the current series, and 6.2.0 now in beta. On 18 August both maintenance branches shipped security releases hours apart — 5.4.8 with 32 merged PRs and 6.1.3 with four — each carrying the same 'install as soon as possible' banner. The release bodies remain download tables and SHA-256 checksums with the merged-PR list at the very end, so the actual change set is only readable from the tail.
The paired-branch pattern that defined the last month has now completed a full cycle: rc1 on 11 August, rc2 on 15 August, finals on 18 August, both branches in lockstep. The fix content is defensive rather than additive — path-traversal checks in com_templates, an ACL check before exposing the user edit link, division-by-zero guards in ListModel and subforms, Smart Search memory limits. Meanwhile 6.2.0 moved from Alpha 3 to Beta 1 after four static weeks, pulling in 19 PRs that include a security flag for updates, secure article preview without frontend login, and a language fallback chain for the AI subsystem.
Expect 6.2.0 to run a second beta before a release candidate, and the 5.4.x/6.1.x pair to resume their coupled patch cadence with the next rc pair a few weeks out.
Pimcore releases on a weekly-to-fortnightly patch cadence across two supported lines - 2026.2.x and the older 12.3.x - and the defining feature of the last two months is the volume of security work. Nearly every release carries at least one GHSA: WebDAV rename permissions, ImageGallery hotspot unserialize, Classificationstore field-name validation, blind SSRF via email test-send, Custom Report field allowlisting. Around it sits ordinary bug fixing in workflows, thumbnails, and data object handling.
The advisories are not scattered; they cluster on the surfaces where Pimcore accepts structured input from an authenticated user - custom reports, classification stores, WebDAV, grid configuration. The fixes follow a consistent method of allowlisting fields, enforcing permissions at the operation rather than the screen, and refusing to echo raw database errors. Read together, this is a deliberate audit of the admin surface rather than a run of unrelated reports, and it is being done in public one patch at a time.
The audit pattern points at the remaining input-accepting admin surfaces - imports, grid and filter parsers, WebDAV operations beyond MOVE - so expect more advisories of the same shape before the cadence slows.
Other Mkt Auto products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Joomla or Pimcore.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Buttondown ships almost daily, and most of it is someone else's bug report closed.
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
Mailtrap is assembling a full email operations platform, one category step at a time
See all Joomla alternatives → · See all Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — cms — within Mkt Auto. Joomla and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Joomla and Pimcore are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Joomla alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Joomla alternatives" section above for the current picks, or visit /alternatives/joomla for the full list with editorial commentary on each.
Top Pimcore alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pimcore alternatives" section above for the current picks, or visit /alternatives/pimcore for the full list with editorial commentary on each.