tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of BaseSet and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
A tidy interface for set algebra that reached 1.0 and has been quiet since.
BaseSet gives R a tidy-style TidySet object for set operations, including fuzzy sets. The 1.0.0 release in early 2025 rounded out the object's ergonomics — subsetting by sets and elements, dimnames() and names(), an all argument on the name and count helpers — and dropped magrittr by raising the R dependency to 4.1. There has been no release in the eighteen months since.
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.
BaseSet gives R a tidy-style TidySet object for set operations, including fuzzy sets. The 1.0.0 release in early 2025 rounded out the object's ergonomics — subsetting by sets and elements, dimnames() and names(), an all argument on the name and count helpers — and dropped magrittr by raising the R dependency to 4.1. There has been no release in the eighteen months since.
Development followed a clear arc from correctness to usability: early releases were CRAN and packaging compliance, 0.9.0 built out extractors and setters so TidySets behave like native R objects, and 1.0.0 finished the naming and subsetting surface. Reaching 1.0 reads as a deliberate stopping point rather than a staging post, and the cadence since supports that.
The package looks feature-complete and maintenance-only; the most likely next release is a CRAN compliance or dependency fix rather than new set operations.
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 BaseSet 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 BaseSet alternatives → · See all webmockr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. BaseSet 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. BaseSet 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 BaseSet alternatives in Analytics are ranked by recent ship velocity. Browse the "BaseSet alternatives" section above for the current picks, or visit /alternatives/baseset 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.