rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of esquisse and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
esquisse's 1.0 turned a point-and-click addin into embeddable Shiny modules.
The visible history covers the 1.0 line only. 1.0.0 is the substantial one: modules for importing data (via datamods) and exporting plots, a `ggplot_output()` / `render_ggplot()` pair, manual colour palettes, aesthetic parameter selection, more export formats including pptx, and typography controls. 1.0.1 and 1.0.2 are corrective — sf object handling, package-sourced data, disabled-panel label controls, and an `output_format` argument on the save modal.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
The visible history covers the 1.0 line only. 1.0.0 is the substantial one: modules for importing data (via datamods) and exporting plots, a `ggplot_output()` / `render_ggplot()` pair, manual colour palettes, aesthetic parameter selection, more export formats including pptx, and typography controls. 1.0.1 and 1.0.2 are corrective — sf object handling, package-sourced data, disabled-panel label controls, and an `output_format` argument on the save modal.
The arc runs from a self-contained RStudio addin toward a component library other people build with: once plot rendering and export exist as Shiny modules, esquisse's ggplot builder can be dropped inside someone else's app rather than only launched beside RStudio. The two follow-up releases are consolidation on that surface rather than expansion of it.
Further work most likely lands on the module API and export coverage, since that is where 1.0.0 put the new surface and where 1.0.2 already returned. The entries do not indicate anything about cadence beyond this line.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
The feature era ended before this window opened. Deploying to SageMaker, generating Docker files, storing renv lockfiles in model metadata and supporting keras, luz and recipes all landed in 0.2.1 and 0.2.2; nothing since has extended what vetiver does. What it does now is track the rest of tidymodels — when recipes gains a prototype API or probably becomes something a workflow can contain, vetiver adds a line. That is a package holding its position rather than advancing it.
The entries do not support a confident prediction of new capability. On this pattern the next release tracks another tidymodels change, most likely the postprocessing stage that workflows added in 1.3.0.
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 esquisse or vetiver.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all esquisse alternatives → · See all vetiver alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. esquisse and vetiver are shipping at a similar cadence (velocity 0.0 vs 0.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. esquisse and vetiver are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top esquisse alternatives in Analytics are ranked by recent ship velocity. Browse the "esquisse alternatives" section above for the current picks, or visit /alternatives/esquisse for the full list with editorial commentary on each.
Top vetiver alternatives in Analytics are ranked by recent ship velocity. Browse the "vetiver alternatives" section above for the current picks, or visit /alternatives/vetiver-r for the full list with editorial commentary on each.