kwb.pkgbuild
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
Comparison · Infra & APIs
Cronicle vs rextendr
A side-by-side editorial comparison of Cronicle and rextendr — release velocity, themes, recent moves, and the top alternatives to consider.
Cronicle vs rextendr: at a glance
What is Cronicle?
Security patching gives way to a hard Node.js 22 floor for every self-hosted install.
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines. Version 0.9.129 changes register: it raises the supported runtime rather than patching another dependency.
What is rextendr?
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.
Cronicle vs rextendr: editorial side-by-side
Cronicle
5.0INFRA · APIS
Security patching gives way to a hard Node.js 22 floor for every self-hosted install.
◆ Current state
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines. Version 0.9.129 changes register: it raises the supported runtime rather than patching another dependency.
◆ Where it's heading
The pattern in 0.9.124 and 0.9.125 is not incidental fixes but a systematic pass over where the server trusted client input — parameters, filters, targets, and log access were each independently tightened, and password hashing moved from the unmaintained bcrypt-node to bcryptjs in 0.9.123. The Node.js 22 requirement is the same instinct applied to the platform: patching transitive dependencies one at a time only holds if the runtime underneath is still receiving fixes. Feature work remains essentially absent from this window. For a scheduler that executes arbitrary commands across a cluster, that allocation is defensible.
◆ Prediction
A declared runtime floor usually precedes code that depends on it, so expect the next releases to stop working around older Node versions. The hardening sweep should continue through the remaining API surface before feature work resumes.
rextendr
0.0INFRA · APIS
rextendr put Rust-backed R packages in the browser, then tore itself down for a 1.0.0 rebuild
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Cronicle and rextendr
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 Cronicle or rextendr.
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
osrm.backend
osrm.backend stopped trusting upstream binaries and started shipping its own
taxifydb
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
See all Cronicle alternatives → · See all rextendr alternatives →
Recent activity from Cronicle and rextendr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h agoCronicleNode.js v22 becomes the official runtime requirement
- 2d agoCroniclenanoid vulnerability bump, pixl-server-user to v2
- 3d agoCroniclesanitize-html and nanoid vulnerability fixes
- 10d agoCronicleFreeBSD compatibility for process monitoring
- 16d agoCronicleCluster auth clock validation restored, five authorization gaps closed
- 29d agoCronicleEvent and job parameters restricted to plugin-defined ones
- 3mo agorextendrNew Makevars-linked build process ahead of 1.0.0
- 9mo agorextendrFinal development tag before the rewrite; template and SystemRequirements changes
- 11mo agorextendrextendr-api version pinning and WebR-compatible build profile
- 1y agorextendrFix tests executed on CRAN
- 1y agorextendrWebR support out of the box for all extendr packages ⚡
- 3y agorextendrPackage templates updated for Rust 1.70
Frequently asked questions
What is the difference between Cronicle and rextendr?
They serve adjacent needs but don't currently overlap on shipped themes. Cronicle is currently shipping more aggressively (velocity 5.0 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.
Is Cronicle better than rextendr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cronicle is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to Cronicle?
Top Cronicle alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cronicle alternatives" section above for the current picks, or visit /alternatives/cronicle for the full list with editorial commentary on each.
What are the best alternatives to rextendr?
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.