compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of hubUtils and logr — release velocity, themes, recent moves, and the top alternatives to consider.
The hubverse's shared plumbing, tracking schema versions and converting output types.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
A SAS-style logging package for R, shipping small and slowly by design.
logr produces SAS-style log files for R scripts, and is one component of the r-sassy suite aimed at analysts migrating clinical and pharmaceutical workflows off SAS. Release notes are terse — often a single line — and the cadence has thinned considerably, with one release in 2026 following a long gap. The functionality visible across this window is essentially complete: handlers, suspend and resume, explicit log_info/log_error/log_warning entries, and console output.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
The through-line is that this package absorbs whatever the schema is doing — v5, then v6 with target-data configuration, each arriving with matching accessors and example hubs so the sibling packages can be tested against something real. convert_output_type() is the one piece of genuine computation here, and it has now been optimised by roughly an order of magnitude, suggesting it is being used at scales the original implementation did not anticipate. Everything else is accessors and fixtures.
Expect the next substantive release to track the next hubverse schema version, with any independent work concentrated on convert_output_type(), the only performance-sensitive function in the package.
logr produces SAS-style log files for R scripts, and is one component of the r-sassy suite aimed at analysts migrating clinical and pharmaceutical workflows off SAS. Release notes are terse — often a single line — and the cadence has thinned considerably, with one release in 2026 following a long gap. The functionality visible across this window is essentially complete: handlers, suspend and resume, explicit log_info/log_error/log_warning entries, and console output.
The arc runs from correctness work on warning and error capture toward giving users control over where log output goes and how it is formatted. Recent releases are refinements of message content rather than new logging concepts, which is what a package settling into maintenance looks like. Nothing in these entries suggests an expansion of scope beyond the SAS-log-emulation brief.
Expect continued low-volume maintenance releases refining message detail and integration with the rest of the r-sassy suite, rather than new logging capability.
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 hubUtils or logr.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
See all hubUtils alternatives → · See all logr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. logr 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. logr 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 Analytics products to evaluate alongside.
Top hubUtils alternatives in Analytics are ranked by recent ship velocity. Browse the "hubUtils alternatives" section above for the current picks, or visit /alternatives/hubutils for the full list with editorial commentary on each.
Top logr alternatives in Analytics are ranked by recent ship velocity. Browse the "logr alternatives" section above for the current picks, or visit /alternatives/logr for the full list with editorial commentary on each.