Retool
Retool is retiring standalone Assist while folding the same capability into the app builder.
A side-by-side editorial comparison of contagionchannels and profoc — release velocity, themes, recent moves, and the top alternatives to consider.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.
A forecast combination package that spun its profiler out into its own project
profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.
contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.
There is no product trajectory to read here yet, only a submission one, and it is unusually well documented — each entry names the reviewer or check that prompted it and quotes the feedback verbatim. That transparency is the one signal available: the maintainer treats review rounds as releases worth publishing rather than squashing. Any judgement about direction will have to wait for a release that changes the package rather than its metadata.
With CRAN acceptance secured, the next release should be the first to carry actual methodological content; until one appears, there is not enough in these entries to say where the package is heading.
profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.
The direction is toward a reusable C++ core with thin language bindings. The timing code that lived inside profoc was extracted into the standalone rcpptimer package in 1.3.2, deliberately so other R packages and Python projects could use it through cpptimer and cppytimer, and the clock header was reworked in 1.3.1 to maximise the code shared between the R and Python versions. Method work sits earlier in the history - periodic splines and penalties in 1.2.0, the penalty() function in 1.1.0 - while the recent cadence, a single release in the last sixteen months, points at a package the maintainer considers finished.
The repeated references to future Python use suggest the next significant work happens outside this package, in the shared C++ components, rather than in profoc's R surface.
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 contagionchannels or profoc.
Retool is retiring standalone Assist while folding the same capability into the app builder.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all contagionchannels alternatives → · See all profoc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. contagionchannels and profoc 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. contagionchannels and profoc 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 contagionchannels alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "contagionchannels alternatives" section above for the current picks, or visit /alternatives/contagionchannels for the full list with editorial commentary on each.
Top profoc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "profoc alternatives" section above for the current picks, or visit /alternatives/profoc for the full list with editorial commentary on each.