writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
A side-by-side editorial comparison of broom and rnaturalearth — release velocity, themes, recent moves, and the top alternatives to consider.
broom's release calendar is now set by CRAN checks, not by new tidiers.
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
1.0.0 ended sp support outright, making sf the default and offering terra's SpatVector via `returnclass`, after 0.3.3 had signposted that with lifecycle badges. The two releases since move to delivery mechanics: 1.1.0 reads data directly out of the zip through the GDAL Virtual File System, starts moving unloaded downloads to GeoPackage instead of shapefile, and switches the base URL to naciscdn.org; 1.2.0 adds caching to `ne_download()` when `destdir` is persistent, swaps devtools for pak when installing the companion data packages, and handles Natural Earth's inconsistent raster zip layouts.
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
Carrying hundreds of tidier methods for model classes it does not own, broom's workload is dominated by other projects' breaking changes and CRAN's evolving checks. New tidier coverage has largely migrated to the packages that define the models, leaving broom as a compatibility surface.
Expect the cadence to stay reactive, with releases triggered by r-devel check failures and upstream API shifts rather than expanded model coverage.
1.0.0 ended sp support outright, making sf the default and offering terra's SpatVector via `returnclass`, after 0.3.3 had signposted that with lifecycle badges. The two releases since move to delivery mechanics: 1.1.0 reads data directly out of the zip through the GDAL Virtual File System, starts moving unloaded downloads to GeoPackage instead of shapefile, and switches the base URL to naciscdn.org; 1.2.0 adds caching to `ne_download()` when `destdir` is persistent, swaps devtools for pak when installing the companion data packages, and handles Natural Earth's inconsistent raster zip layouts.
With the class question settled, the work has shifted to not re-downloading and not unpacking — VFS reads, caching, and a container format that does not need a sidecar of four files. That points at the package being used in repeated or automated contexts rather than interactive one-offs. The shapefile-to-GeoPackage transition is explicitly incomplete.
Completing the GeoPackage transition for `load = FALSE` downloads is the obvious next step, since 1.1.0 described it as in progress.
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 broom or rnaturalearth.
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.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all broom alternatives → · See all rnaturalearth alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. broom and rnaturalearth 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. broom and rnaturalearth 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 broom alternatives in Analytics are ranked by recent ship velocity. Browse the "broom alternatives" section above for the current picks, or visit /alternatives/broom for the full list with editorial commentary on each.
Top rnaturalearth alternatives in Analytics are ranked by recent ship velocity. Browse the "rnaturalearth alternatives" section above for the current picks, or visit /alternatives/rnaturalearth for the full list with editorial commentary on each.