containerd
containerd opens its 2.4 beta while five older branches keep taking coordinated backports.
A side-by-side editorial comparison of Aerospike and GravityView — release velocity, themes, recent moves, and the top alternatives to consider.
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.
Unions let one View stack entries from many forms — no shared field, no code.
GravityKit ships a weekly Launch Log covering the whole add-on suite, with dedicated announcement posts reserved for the bigger items. The current one is unions in Multiple Forms 0.7.0: entries from many Gravity Forms forms stack into a single searchable View without a shared field or custom code. Around it, the suite is absorbing Gravity Forms 3.0 and WordPress 7.0 compatibility work while GravityEdit picks up rich text inline editing.
On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.
The pattern is a vendor with long-lived enterprise deployments treating branch parity as a hard requirement: every fix is labelled with the editions it affects, and Community Edition receives the same security content as Enterprise and Federal. Most of the disclosed issues sit in msgpack parsing and collection data types, which is where untrusted client input first meets the server — a concentration that suggests a focused audit of that boundary rather than scattered reports. Outside the security work, releases are small: log verbosity, lock contention on cold-start eviction, transaction object-count accuracy.
Several CVEs in this train are still marked pending assignment, so expect follow-up releases as those are published and any related parsing paths are closed out. The branch-parity discipline shown here makes it likely that whatever lands next will again ship simultaneously across all four supported lines.
GravityKit ships a weekly Launch Log covering the whole add-on suite, with dedicated announcement posts reserved for the bigger items. The current one is unions in Multiple Forms 0.7.0: entries from many Gravity Forms forms stack into a single searchable View without a shared field or custom code. Around it, the suite is absorbing Gravity Forms 3.0 and WordPress 7.0 compatibility work while GravityEdit picks up rich text inline editing.
Two threads have run steadily since GravityView 3.0 in June. The first is treating Gravity Forms entries as a queryable data layer rather than per-form lists — unions, distance sorting on radius searches, field-to-field filtering, DataTables performance on large sets. The second is the MCP surface: Block MCP and GravityKit MCP keep gaining capability, most recently theme template editing, pairing with the AI View creation that shipped in 3.0. Accessibility work — screen reader row headers, editor upgrades — runs alongside both.
The union model invites the obvious follow-ons: cross-form search, sorting, and filtering behaving consistently once entries from different forms share a View. Expect that plus continued Gravity Forms 3.0 compatibility fixes in the weekly logs.
Other DevOps 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 Aerospike or GravityView.
containerd opens its 2.4 beta while five older branches keep taking coordinated backports.
A patch cadence dominated by one theme: making server-sent events behave
Firebird maintains three release branches at once and ships the same fixes to all of them
GeoTools is migrating off dead Java imaging infrastructure that the whole GeoServer stack sits on
SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer
Psi4 is closing the gap with ORCA on the methods that decide which code a lab installs
See all Aerospike alternatives → · See all GravityView alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Aerospike and GravityView 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. Aerospike and GravityView 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 DevOps products to evaluate alongside.
Top Aerospike alternatives in DevOps are ranked by recent ship velocity. Browse the "Aerospike alternatives" section above for the current picks, or visit /alternatives/aerospike for the full list with editorial commentary on each.
Top GravityView alternatives in DevOps are ranked by recent ship velocity. Browse the "GravityView alternatives" section above for the current picks, or visit /alternatives/gravityview for the full list with editorial commentary on each.