r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of sofa and spatsoc — release velocity, themes, recent moves, and the top alternatives to consider.
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.
One maintainer, one or two new collective-motion metrics per release, for two years straight
spatsoc turns animal relocation data into spatial and social groupings — dyads, fission-fusion events, group centroids — and the recent history is a metronomic accretion of collective-motion measures on top of that base. Since late 2024 nearly every release has added one or two: polarization, direction to leader, position along the group axis, directional correlation delay, edge alignment, edge zones. Development is essentially single-handed; almost every merged PR in this window carries the same author.
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.
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.
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.
spatsoc turns animal relocation data into spatial and social groupings — dyads, fission-fusion events, group centroids — and the recent history is a metronomic accretion of collective-motion measures on top of that base. Since late 2024 nearly every release has added one or two: polarization, direction to leader, position along the group axis, directional correlation delay, edge alignment, edge zones. Development is essentially single-handed; almost every merged PR in this window carries the same author.
The December 2025 release changes register. Alongside three new calc_distance / calc_direction / calc_centroid functions and an internal assertion family, it deprecates the `projection` argument in favour of `crs` and lands a round of checks and tests explicitly staged ahead of a new spatial interface. Read together, that is a package finishing its metric catalogue and starting to rework the coordinate-handling layer underneath it to match modern R-spatial conventions — the same evolution that made it drop its startup warning back in 0.2.7.
The next release is likely the spatial-interface rework the 0.2.12 test and assertion work was staged for, with `projection` moving from deprecated to removed. Feature additions should slow while that lands.
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 spatsoc.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all sofa alternatives → · See all spatsoc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top spatsoc alternatives in Analytics are ranked by recent ship velocity. Browse the "spatsoc alternatives" section above for the current picks, or visit /alternatives/spatsoc for the full list with editorial commentary on each.