cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
Comparison · Analytics
common vs hubAdmin
A side-by-side editorial comparison of common and hubAdmin — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
common vs hubAdmin: at a glance
What is common?
A base-R utility belt that grows one small function at a time, on no particular schedule
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
What is hubAdmin?
The config-authoring half of hubverse, pinned to whatever the schema is doing this quarter
hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.
common vs hubAdmin: editorial side-by-side
common
0.0ANALYTICS
A base-R utility belt that grows one small function at a time, on no particular schedule
◆ Current state
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
◆ Where it's heading
The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.
◆ Prediction
Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.
hubAdmin
0.0ANALYTICS
The config-authoring half of hubverse, pinned to whatever the schema is doing this quarter
◆ Current state
hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.
◆ Where it's heading
Every release here is legible as schema-following. New schema properties become new arguments, new schema constraints become new validate_config() checks, and the package version is essentially a marker for which schema generation it can author. The one thread that is genuinely its own is ergonomics: session-level options for schema version and branch, support for in-development schema branches, and a steadily stricter validator that now catches duplicate properties and mismatched target keys before a hub goes live.
◆ Prediction
With v6.0.0 support only partially landed, the next releases most likely finish the additional_metadata migration across the remaining create_* functions.
Alternatives to common and hubAdmin
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 common or hubAdmin.
MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
fmtr
Rebuilding SAS's formatting layer in R, one format specification at a time
betaselectr
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
SSN2
Stream-network spatial models learning to run on data that no longer fits in memory
BiocManager
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all common alternatives → · See all hubAdmin alternatives →
Recent activity from common and hubAdmin
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agocommonFull set of relational infix operators added
- 9mo agohubAdminSchema v6.0.0 additional_metadata support lands
- 9mo agohubAdmintarget-data.json config validation added
- 1y agohubAdminTarget metadata gains optional properties for schema 5.1.0
- 1y agohubAdminValidator catches duplicate properties and mismatched target keys
- 1y agohubAdminSchema version and branch settable per session
- 1y agohubAdminOutput types follow the v4.0.0 is_required split
- 2y agocommonsource.all() fixed to cooperate with logr
- 2y agocommonsource.all() added for sourcing a directory of scripts
- 2y agocommonchanged() fixed for single-value input
- 2y agocommonchanged() identifies grouping boundaries
- 3y agocommonthis.path() dependency removed
Frequently asked questions
What is the difference between common and hubAdmin?
Both compete on the same themes — r-package — within Analytics. common and hubAdmin 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.
Is common better than hubAdmin?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. common and hubAdmin 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.
What are the best alternatives to common?
Top common alternatives in Analytics are ranked by recent ship velocity. Browse the "common alternatives" section above for the current picks, or visit /alternatives/common for the full list with editorial commentary on each.
What are the best alternatives to hubAdmin?
Top hubAdmin alternatives in Analytics are ranked by recent ship velocity. Browse the "hubAdmin alternatives" section above for the current picks, or visit /alternatives/hubadmin for the full list with editorial commentary on each.