tulpa
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
A side-by-side editorial comparison of Grafana Mimir and sftime — release velocity, themes, recent moves, and the top alternatives to consider.
Mimir's feed is a weekly Helm bot, with the 3.2 candidate the only real release in months
The visible cadence is an automated weekly Helm chart release opened by a bot with a two-line body, now at 6.3.0-weekly.408. The only substantive entry in the window is the 3.2.0 release candidate from early August, which carried query engine work and native histogram support.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
The visible cadence is an automated weekly Helm chart release opened by a bot with a two-line body, now at 6.3.0-weekly.408. The only substantive entry in the window is the 3.2.0 release candidate from early August, which carried query engine work and native histogram support.
Packaging and the engine move on separate clocks: the chart ships weekly regardless of whether anything changed underneath, while Mimir itself cuts a minor roughly monthly. The weekly stream tells you nothing about direction and will keep dominating the feed by volume.
The chart line moving from 6.2.0-weekly to 6.3.0-weekly points at a 6.3.0 chart release carrying Mimir 3.2 once the candidate goes final.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
Other Analytics 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 Grafana Mimir or sftime.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
Interfaces gets the permissions layer it needed, one release after launching.
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
See all Grafana Mimir alternatives → · See all sftime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Grafana Mimir is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Grafana Mimir is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Grafana Mimir alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Mimir alternatives" section above for the current picks, or visit /alternatives/grafana-mimir for the full list with editorial commentary on each.
Top sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime for the full list with editorial commentary on each.