cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of BiocManager and hubExamples — release velocity, themes, recent moves, and the top alternatives to consider.
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
BiocManager is the entry point for installing Bioconductor packages and keeping an installation consistent with a Bioconductor release. It resolves which Bioconductor version pairs with the running R version, points at the right repositories, and handles the version-map logic behind that. The package version has sat at 1.30.x for years, with patch numbers carrying every change.
Example data for the hubverse, moving whenever the standards it demonstrates move.
hubExamples ships the reference datasets that hubverse vignettes and downstream packages use to demonstrate forecast and target data. Its releases track the hubverse specification rather than any independent roadmap: 1.0.0 exists because the target time series standard changed, and 0.1.0 because the oracle output terminology did. The current release, 1.0.1, is a single fix for column deserialisation on systems without arrow.
BiocManager is the entry point for installing Bioconductor packages and keeping an installation consistent with a Bioconductor release. It resolves which Bioconductor version pairs with the running R version, points at the right repositories, and handles the version-map logic behind that. The package version has sat at 1.30.x for years, with patch numbers carrying every change.
The consistent direction is making the installer's behaviour controllable without interactive prompts. Successive releases have added environment variables for site repositories, repository checks, the Bioconductor name used in binary URL resolution, and a deliberate override for running against an unsupported R version. That is a package being shaped by continuous integration and container use, where nothing can be answered at a prompt. Alongside it runs a slow cleanup of legacy surface, with the biocLite era finally removed in 2025.
The escape-hatch pattern is well established, so further environment-variable controls and continued pruning of legacy install paths are the most likely next moves.
hubExamples ships the reference datasets that hubverse vignettes and downstream packages use to demonstrate forecast and target data. Its releases track the hubverse specification rather than any independent roadmap: 1.0.0 exists because the target time series standard changed, and 0.1.0 because the oracle output terminology did. The current release, 1.0.1, is a single fix for column deserialisation on systems without arrow.
This is a downstream member of the hubverse package family, alongside hubUtils, hubData and hubValidations, and it moves when they define something new. The pattern across all four entries is the same: a standard changes upstream, hubExamples updates its data objects and vignettes to match. Sibling package hubAdmin has not shipped since November 2025, so the cohort is not currently in a coordinated wave.
The next release will most likely follow the next hubverse data-standard revision rather than lead it.
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 BiocManager or hubExamples.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Rebuilding SAS's formatting layer in R, one format specification at a time
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
See all BiocManager alternatives → · See all hubExamples alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. BiocManager and hubExamples 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. BiocManager and hubExamples 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 BiocManager alternatives in Analytics are ranked by recent ship velocity. Browse the "BiocManager alternatives" section above for the current picks, or visit /alternatives/biocmanager for the full list with editorial commentary on each.
Top hubExamples alternatives in Analytics are ranked by recent ship velocity. Browse the "hubExamples alternatives" section above for the current picks, or visit /alternatives/hubexamples for the full list with editorial commentary on each.