saperlipopette
saperlipopette turned Git disasters into practice exercises, then passed peer review
A side-by-side editorial comparison of kwb.pkgbuild and rextendr — release velocity, themes, recent moves, and the top alternatives to consider.
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
kwb.pkgbuild automates R package setup at Kompetenzzentrum Wasser Berlin to a house style, and its main deliverable is the GitHub Actions templates it installs into new packages. Between October 2022 and May 2026 there were no releases. During that gap the templates aged past the point of working on current GitHub-hosted runners.
rextendr put Rust-backed R packages in the browser, then tore itself down for a 1.0.0 rebuild
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
kwb.pkgbuild automates R package setup at Kompetenzzentrum Wasser Berlin to a house style, and its main deliverable is the GitHub Actions templates it installs into new packages. Between October 2022 and May 2026 there were no releases. During that gap the templates aged past the point of working on current GitHub-hosted runners.
0.3.0 is a catch-up release rather than a direction change: action versions bumped to checkout@v5, upload-artifact@v4 and codecov-action@v5 to clear the Node.js 20 deprecation, deprecated r-lib/actions@master references replaced with @v2, the retired ubuntu-20.04 runner swapped for ubuntu-latest, and the archived r-hub/sysreqs step replaced with setup-r-dependencies@v2, which also brings dependency caching. One fix stands out: a stale conditional comparing runner.os to the string 'Linux (no, try without!)' had been silently disabling the Linux system-dependency step.
For a package whose product is CI configuration, releases will keep tracking GitHub Actions deprecations — the notes already cite the Node.js 20 removal date. The four-year gap suggests updates arrive when something breaks rather than on a schedule.
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
Two threads run in parallel. The first is reach: 0.4.0 added WebR support out of the box for all extendr packages by enabling the wasm32-unknown-emscripten target, and 0.4.2 followed with the panic and link-time-optimization settings needed to make those builds actually work. The second is CRAN compliance — use_cran_defaults(), vendor_pkgs(), automatic SystemRequirements fields, and configure scripts, all aimed at getting Rust-powered packages accepted on CRAN. The rebuild announced in 0.4-final is a third thread whose shape the entries do not reveal.
The stated destination is 1.0.0 built on the new Makevars-linked build process, so that release is the next milestone. What the revamp changes for existing extendr packages is not described in any entry here.
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 kwb.pkgbuild or rextendr.
saperlipopette turned Git disasters into practice exercises, then passed peer review
rdocdump grew from a CRAN doc dumper into a resolver that pulls packages from anywhere
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
osrm.backend stopped trusting upstream binaries and started shipping its own
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
See all kwb.pkgbuild alternatives → · See all rextendr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Infra & APIs. kwb.pkgbuild and rextendr 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. kwb.pkgbuild and rextendr 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 kwb.pkgbuild alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kwb.pkgbuild alternatives" section above for the current picks, or visit /alternatives/kwb-pkgbuild for the full list with editorial commentary on each.
Top rextendr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rextendr alternatives" section above for the current picks, or visit /alternatives/rextendr for the full list with editorial commentary on each.