Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of cIRT and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
A choice-based IRT model published once in 2019 and kept compiling ever since
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
The package's whole functional history fits in a two-day window in January 2019, when the CRAN release and its immediate follow-ups were tagged in one batch, followed a day later by a release enabling C++11 and OpenMP and fixing the choice generation procedure. Since then the releases track other people's deprecations: Armadillo dropping conversions, RcppArmadillo requiring a different Makevars, R raising its floor. The 2025 release is entirely of that kind, down to swapping the README to Quarto.
The dependency floors were just raised to current Rcpp and RcppArmadillo, so the next release is most likely the one after Armadillo deprecates something else.
Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.
The two ends of this project are pulling apart cleanly. Old branches are being prepared for retirement — a deprecation warning fanned across eight of them, Python 3.8 testing dropped from 1.4 through 1.6 — while Fusion accumulates the adapter breadth it needs to be a credible replacement. beta.1 proved the engine could bind without a catalog; beta.2 is the unglamorous follow-through of making a specific warehouse work properly.
Expect further beta releases filling in per-adapter gaps rather than new engine capability, and formal end-of-life notices for the branches that just took the deprecation warning.
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 cIRT or dbt Core.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
See all cIRT alternatives → · See all dbt Core alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 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. dbt Core is currently shipping more aggressively (velocity 6.3 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 cIRT alternatives in Analytics are ranked by recent ship velocity. Browse the "cIRT alternatives" section above for the current picks, or visit /alternatives/cirt for the full list with editorial commentary on each.
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.