tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of sass and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
This is a stable binding to a C++ library that is itself no longer moving, so the package's work is defined by the compilers and CRAN policies around it rather than by Sass features. Nothing in these entries suggests active development; the maintenance is competent and prompt, but it is maintenance.
The next release will most likely be triggered by a new compiler warning class or an R CMD check requirement rather than by anything in the Sass language. The entries give no signal of planned feature work.
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
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 sass or webmockr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all sass alternatives → · See all webmockr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. sass and webmockr 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. sass and webmockr 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 sass alternatives in Analytics are ranked by recent ship velocity. Browse the "sass alternatives" section above for the current picks, or visit /alternatives/sass for the full list with editorial commentary on each.
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.