tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
sofa vs webmockr
A side-by-side editorial comparison of sofa and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropensci
sofa vs webmockr: at a glance
What is sofa?
A CouchDB client for R whose recent work is all test infrastructure, not new routes.
sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.
What is webmockr?
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.
sofa vs webmockr: editorial side-by-side
sofa
2.5ANALYTICS
A CouchDB client for R whose recent work is all test infrastructure, not new routes.
◆ Current state
sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.
◆ Where it's heading
This is a rOpenSci package being brought back to a maintainable state rather than extended. The 0.4.1 decision to mock the server is the consequential one — it decouples CI from a live CouchDB, which is what made the cross-platform GitHub Actions workflow and full coverage possible at all. Two genuine bugs surfaced in that process, in db_replicate() URL construction against non-Cloudant servers and db_alldocs(disk=) not returning the documented file path, suggesting the untested paths had drifted.
◆ Prediction
With the test harness now self-contained, the next plausible move is catching up on CouchDB routes added since v3 rather than further infrastructure work, though nothing in these entries commits to it.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to sofa and webmockr
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 sofa or webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all sofa alternatives → · See all webmockr alternatives →
Recent activity from sofa and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agosofaCRAN check notes and metadata corrections
- 2mo agosofaTests moved to a mocked CouchDB, coverage to 100%
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
- 6y agosofaCouchDB v3 support, doc_upsert() and bulk get
- 8y agosofaMango index management and batched design search
- 9y agosofasofa v0.2.0
Frequently asked questions
What is the difference between sofa and webmockr?
Both compete on the same themes — ropensci — within Analytics. sofa is currently shipping more aggressively (velocity 2.5 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.
Is sofa better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sofa is currently shipping more aggressively (velocity 2.5 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.
What are the best alternatives to sofa?
Top sofa alternatives in Analytics are ranked by recent ship velocity. Browse the "sofa alternatives" section above for the current picks, or visit /alternatives/sofa for the full list with editorial commentary on each.
What are the best alternatives to webmockr?
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.