RSelenium
RSelenium's only release in eight years touched documentation and CI, nothing else.
A side-by-side editorial comparison of renv and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.
renv 1.2 made installs parallel, its biggest performance change in years.
renv provides project-local dependency management for R. The 1.2.0 release rebuilt installation to download and compile concurrently, and the 1.2.x line since has been resolving the correctness problems parallelism exposed — binaries installing ahead of their dependencies, transitive upgrades that were never needed, lockfile paths shifting with the working directory.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
renv provides project-local dependency management for R. The 1.2.0 release rebuilt installation to download and compile concurrently, and the 1.2.x line since has been resolving the correctness problems parallelism exposed — binaries installing ahead of their dependencies, transitive upgrades that were never needed, lockfile paths shifting with the working directory.
Work is consolidating around two things: making the parallel installer correct under real dependency graphs, and broadening remote support so private and self-hosted sources resolve properly. The most recent release translates self-hosted GitLab remotes into the syntax pkgdepends actually understands.
Expect continued fixes to install ordering and remote resolution rather than another performance overhaul, since the parallel path is new enough to keep surfacing ordering bugs.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
Rhino is converging on scaffolding as its main surface — the framework's value is increasingly in what it generates for you rather than what it does at runtime, and 1.12 extends that generation to instructions meant for AI coding agents rather than humans. The maintainer change and the CI/coverage work in the same release read as consolidation after a long gap: 1.11 shipped in April 2025, 1.12 not until June 2026.
More `use_*` scaffolding functions are the obvious next increment, since two arrived in a single release. Whether the AGENTS.md instructions grow into deeper agent tooling is not something these entries settle.
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 renv or Rhino.
RSelenium's only release in eight years touched documentation and CI, nothing else.
servr keeps growing from a static file server into a general-purpose R web server.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. renv 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. renv 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 Infra & APIs products to evaluate alongside.
Top renv alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "renv alternatives" section above for the current picks, or visit /alternatives/renv for the full list with editorial commentary on each.
Top Rhino alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rhino alternatives" section above for the current picks, or visit /alternatives/rhino-r for the full list with editorial commentary on each.