servr
servr keeps growing from a static file server into a general-purpose R web server.
A side-by-side editorial comparison of git2r and RSelenium — release velocity, themes, recent moves, and the top alternatives to consider.
git2r stopped vendoring libgit2 and now expects it on the system
git2r is the R binding to libgit2. The defining recent change is packaging, not API: 0.35.0 removed the bundled libgit2 source entirely and made a system install of libgit2 1.0 or newer a hard requirement, with a macOS fallback that downloads a checksum-verified static build. 0.36.2 follows up with proxy support and clearer build-time error messages.
RSelenium's only release in eight years touched documentation and CI, nothing else.
1.7.10, published February 2026, contains documentation updates, a move from Travis CI to GitHub Actions, and CRAN note fixes — no functional change at all, and it is the first release since September 2018. The releases before it are equally quiet: a dummy argument in `executeScript`, `phantom()` made defunct, and credential-exposure and driver-startup fixes. The last real capability change in the window is `rsDriver()` arriving in 1.6.4, which replaced the defunct `checkForServer` and `startServer` helpers.
git2r is the R binding to libgit2. The defining recent change is packaging, not API: 0.35.0 removed the bundled libgit2 source entirely and made a system install of libgit2 1.0 or newer a hard requirement, with a macOS fallback that downloads a checksum-verified static build. 0.36.2 follows up with proxy support and clearer build-time error messages.
The package is trading install convenience for a maintainable build, and the releases since are about softening that edge — better diagnostics when the requirement is unmet, documented system dependencies, platform-specific build configuration. The API itself grows slowly and only where the underlying libgit2 exposes something new.
Expect further build-configuration and diagnostics work on the unbundled setup, with API additions arriving only as thin wrappers over libgit2 features.
1.7.10, published February 2026, contains documentation updates, a move from Travis CI to GitHub Actions, and CRAN note fixes — no functional change at all, and it is the first release since September 2018. The releases before it are equally quiet: a dummy argument in `executeScript`, `phantom()` made defunct, and credential-exposure and driver-startup fixes. The last real capability change in the window is `rsDriver()` arriving in 1.6.4, which replaced the defunct `checkForServer` and `startServer` helpers.
This is a package being kept installable rather than developed. The 2016-2018 era did the architectural work — moving process management out to wdman, recommending Docker for running a Selenium server, retiring PhantomJS — and nothing since has revisited it. That leaves RSelenium sitting on the older WebDriver arrangement while the browser-automation landscape has moved on.
Further releases, if any, are likely to be CRAN-compliance rather than feature work; the entries give no indication of active development resuming.
Other Infra & APIs 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 git2r or RSelenium.
servr keeps growing from a static file server into a general-purpose R web server.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Windmill is dismantling the paywall between itself and the data stack
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr finished its job in 2021 and has been tracking compilers ever since.
The deployment client is being rebuilt around credentials it never has to store.
See all git2r alternatives → · See all RSelenium alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. git2r and RSelenium 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. git2r and RSelenium 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 Infra & APIs products to evaluate alongside.
Top git2r alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "git2r alternatives" section above for the current picks, or visit /alternatives/git2r for the full list with editorial commentary on each.
Top RSelenium alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "RSelenium alternatives" section above for the current picks, or visit /alternatives/rselenium for the full list with editorial commentary on each.