bootStateSpace
A parametric bootstrap for state-space models, shipped and then left alone.
A side-by-side editorial comparison of bbk and churon — release velocity, themes, recent moves, and the top alternatives to consider.
One R interface is absorbing the world's central bank data portals, one API at a time.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
The expansion is steady and the integration work is what makes it more than a list of wrappers: arguments introduced for one provider get pushed to the others, dimension introspection is being generalised across dataflows, and the bug fixes in recent releases are almost all about the same class of problem — series with missing observations, unsupported frequency codes, or date/value misalignment breaking a parser written for a tidier feed. The maintainer ships the same infrastructure across their packages in lockstep; bbk 0.9.0 and the sibling treasury package's 0.5.0 landed identical opt-in caching within minutes of each other. Geography is the visible frontier, but consistency across an increasingly ragged set of upstream APIs is the actual work.
Expect more national central banks to be added on the same template, and the newer providers to be retrofitted with the dimension and updated_after functions the older ones already have.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.
Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.
Other Analytics 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 bbk or churon.
A parametric bootstrap for state-space models, shipped and then left alone.
A Brazilian housing-data palette package went from internal tooling to public 1.0 in five days.
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.
A palette generator became a palette platform — and changed the metric behind every color it picks.
An extreme-value toolkit reorganised its whole API into prefixed families and tripled its estimator count.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bbk and churon 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. bbk and churon 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 Analytics products to evaluate alongside.
Top bbk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbk alternatives" section above for the current picks, or visit /alternatives/bbk for the full list with editorial commentary on each.
Top churon alternatives in Analytics are ranked by recent ship velocity. Browse the "churon alternatives" section above for the current picks, or visit /alternatives/churon for the full list with editorial commentary on each.