rextendr
rextendr put Rust-backed R packages in the browser, then tore itself down for a 1.0.0 rebuild
Comparison · Infra & APIs
kwb.pkgbuild vs osrm.backend
A side-by-side editorial comparison of kwb.pkgbuild and osrm.backend — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r
kwb.pkgbuild vs osrm.backend: at a glance
What is kwb.pkgbuild?
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.
What is osrm.backend?
osrm.backend stopped trusting upstream binaries and started shipping its own
osrm.backend installs and manages OSRM routing servers from R. Through 0.3.x it fetched official upstream binaries and patched around their runtime dependencies. 0.4.0 in July 2026 changed the supply chain: the package now ships self-built, immutable OSRM binaries for macOS (Intel and Apple Silicon), Linux (x86_64 and arm64) and Windows, built by the maintainer and bundled with runtime libraries like Intel TBB.
kwb.pkgbuild vs osrm.backend: editorial side-by-side
kwb.pkgbuild
0.0INFRA · APIS
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
osrm.backend
0.0INFRA · APIS
osrm.backend stopped trusting upstream binaries and started shipping its own
◆ Current state
osrm.backend installs and manages OSRM routing servers from R. Through 0.3.x it fetched official upstream binaries and patched around their runtime dependencies. 0.4.0 in July 2026 changed the supply chain: the package now ships self-built, immutable OSRM binaries for macOS (Intel and Apple Silicon), Linux (x86_64 and arm64) and Windows, built by the maintainer and bundled with runtime libraries like Intel TBB.
◆ Where it's heading
The package is moving from wrapper toward distribution channel. The maintainer-built binaries are the default provider, with the official ones retained behind osrm_binaries_provider = 'official'. Integrity verification switched to GitHub release asset digests with checksums.txt as fallback, so new binary builds no longer require a package update to be trusted. Earlier releases show the same instinct — 0.3.0 added an osrm_gui() Shiny explorer and a server registry rather than leaving those to users.
◆ Prediction
With the build matrix and verification path in place, the next work is likely validating newer upstream OSRM versions against the existing binary pipeline rather than changing the installation model. Whether the maintainer can sustain a five-platform build matrix is the open question the entries do not answer.
Alternatives to kwb.pkgbuild and osrm.backend
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 osrm.backend.
saperlipopette
saperlipopette turned Git disasters into practice exercises, then passed peer review
rdocdump
rdocdump grew from a CRAN doc dumper into a resolver that pulls packages from anywhere
nominatimlite
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
taxifydb
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
beekeeper
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
See all kwb.pkgbuild alternatives → · See all osrm.backend alternatives →
Recent activity from kwb.pkgbuild and osrm.backend
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosrm.backendSelf-built OSRM binaries for five platforms replace upstream as default ⚡
- 3mo agokwb.pkgbuildGitHub Actions templates rebuilt for current runners
- 3mo agoosrm.backendWindows install fixes for OSRM v26+ binaries
- 3mo agoosrm.backendosrm_gui() Shiny app and a server registry with print methods
- 6mo agoosrm.backendServer logging moves to temp files to avoid deadlocks
- 8mo agoosrm.backendTest suite fixes for CRAN warnings
- 3y agokwb.pkgbuildRepair CI workflows broken by upstream branch removal
- 4y agokwb.pkgbuildWindows becomes default OS for pkgdown and coverage workflows
- 4y agokwb.pkgbuildBugfix release
- 4y agokwb.pkgbuildRelease with no documented changes
- 4y agokwb.pkgbuildFix R CMD check workflow by adding GITHUB_PAT
Frequently asked questions
What is the difference between kwb.pkgbuild and osrm.backend?
Both compete on the same themes — r — within Infra & APIs. kwb.pkgbuild and osrm.backend 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.
Is kwb.pkgbuild better than osrm.backend?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kwb.pkgbuild and osrm.backend 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.
What are the best alternatives to kwb.pkgbuild?
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.
What are the best alternatives to osrm.backend?
Top osrm.backend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "osrm.backend alternatives" section above for the current picks, or visit /alternatives/osrm-backend for the full list with editorial commentary on each.