beekeeper
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A side-by-side editorial comparison of GravityKit and taxifydb — release velocity, themes, recent moves, and the top alternatives to consider.
GravityKit ships a weekly Launch Log, and the interesting work is buried inside it
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
taxifydb packages taxonomic backbone databases for R, publishing prebuilt registers alongside the underlying data. The 0.1.21 release is a self-audit: the coverage checker was walking a hand-kept BACKENDS vector, so a backbone wired into the build but never added to that list was audited by nothing and reported clean, which had been the state of one backbone since it was added. The check now parses the real registration source, and refuses to run rather than audit a guessed set.
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
Two threads persist. One is making Views handle data they previously could not — unions stacking entries from many forms without a shared field or custom code, field-to-field filtering, distance sorting, 3D map viewport loading. The other is compatibility maintenance against a moving platform, with Gravity Forms 3.0 fixes appearing in four consecutive Launch Logs. The MCP work on Block MCP and GravityKit MCP has gone quiet since June, which makes the AI thread the least predictable part of the suite.
Expect the export and data-source work to keep widening now that Google Sheets is wired in, and the Gravity Forms 3.0 fix stream to taper as the compatibility surface is worked through. Whether the MCP add-ons get further investment is not readable from these entries.
taxifydb packages taxonomic backbone databases for R, publishing prebuilt registers alongside the underlying data. The 0.1.21 release is a self-audit: the coverage checker was walking a hand-kept BACKENDS vector, so a backbone wired into the build but never added to that list was audited by nothing and reported clean, which had been the state of one backbone since it was added. The check now parses the real registration source, and refuses to run rather than audit a guessed set.
The visible work is about closing gaps between what the build actually contains and what the checks believe it contains. Alongside the coverage fix, register artifacts are now compared against the backbones recorded in their own metadata sidecar, adding drift states the weekly workflow can open issues on. A curl bug in the same release is the same theme at a different level: setting an Authorization header replaced the header set rather than adding to it, silently dropping the Accept header that requests the asset bytes.
Expect the drift detection to keep expanding into the parts of the build that currently have no signal, since each release so far has found another place where a check was passing without looking at anything.
Other Infra & APIs 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 GravityKit or taxifydb.
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A canvas grid wrapper aiming at the row counts where R's HTML table widgets stop being usable.
doctest is leaving CRAN: 0.4.1 is the last release through R's default channel.
An R binding whose releases are mostly the upstream JS graph engine arriving, plus port ergonomics.
Antrea turned on gossip encryption by default and made users read the upgrade guide first.
Post-1.0 Strimzi tracks Kafka releases and hardens its own defaults
See all GravityKit alternatives → · See all taxifydb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GravityKit and taxifydb 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. GravityKit and taxifydb 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 Infra & APIs products to evaluate alongside.
Top GravityKit alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GravityKit alternatives" section above for the current picks, or visit /alternatives/gravitykit for the full list with editorial commentary on each.
Top taxifydb alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "taxifydb alternatives" section above for the current picks, or visit /alternatives/taxifydb for the full list with editorial commentary on each.