leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
Comparison · Analytics
broom vs Countly
A side-by-side editorial comparison of broom and Countly — release velocity, themes, recent moves, and the top alternatives to consider.
broom vs Countly: at a glance
What is broom?
broom's release calendar is now set by CRAN checks, not by new tidiers.
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
What is Countly?
Countly's LTS line is spending its releases on hardening the surfaces customers extend.
The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.
broom vs Countly: editorial side-by-side
broom
0.0ANALYTICS
broom's release calendar is now set by CRAN checks, not by new tidiers.
◆ Current state
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
◆ Where it's heading
Carrying hundreds of tidier methods for model classes it does not own, broom's workload is dominated by other projects' breaking changes and CRAN's evolving checks. New tidier coverage has largely migrated to the packages that define the models, leaving broom as a compatibility surface.
◆ Prediction
Expect the cadence to stay reactive, with releases triggered by r-devel check failures and upstream API shifts rather than expanded model coverage.
Countly
5.0ANALYTICS
Countly's LTS line is spending its releases on hardening the surfaces customers extend.
◆ Current state
The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.
◆ Where it's heading
The pattern across these releases is closing the gaps where a customer-supplied artefact — custom hook code, a copied widget, a projection on a request — could reach further than intended. That work is now touching the runtime itself, and the isolated-vm swap is a breaking change: custom code relying on setTimeout, setInterval or async completion fails with a logged error instead of running. The journey engine is the only place shipping genuinely new capability, and it is enterprise-only.
◆ Prediction
Expect follow-up releases to soften the custom-code migration, since the isolated-vm switch silently breaks any hook that awaited a timer, and further ab-testing work now that pystan has been replaced with compiled Stan executables.
Alternatives to broom and Countly
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 broom or Countly.
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
bigrquery
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
sparklyr
sparklyr now spends its releases absorbing dbplyr changes and feeding pysparklyr
Seurat
Seurat's centre of gravity has moved from single cells to spatial data and on-disk matrices
insight
insight quietly widens the set of model objects the easystats ecosystem can read
See all broom alternatives → · See all Countly alternatives →
Recent activity from broom and Countly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
- 9d agoCountlyFixes for event keys containing special characters
- 9d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
- 20d agoCountlyStar-rating logo path and data-manager transformation fixes
- 21d agoCountlyLTS backport: data-manager transformation fix
- 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
- 3mo agobroombroom 1.0.13 relocates a test fixture to clear an r-devel warning
- 3mo agobroombroom 1.0.12 tracks renamed summary() output fields
- 8mo agobroombroom 1.0.11 transfers maintainership to Emil Hvitfeldt
- 11mo agobroombroom 1.0.10 clears an r-devel namespacing warning
- 1y agobroombroom 1.0.9 requires R 4.1 and repairs epiR compatibility
- 1y agobroombroom 1.0.8 fixes cluster-robust intervals, drops orcutt tidiers
Frequently asked questions
What is the difference between broom and Countly?
They serve adjacent needs but don't currently overlap on shipped themes. Countly is currently shipping more aggressively (velocity 5.0 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.
Is broom better than Countly?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to broom?
Top broom alternatives in Analytics are ranked by recent ship velocity. Browse the "broom alternatives" section above for the current picks, or visit /alternatives/broom for the full list with editorial commentary on each.
What are the best alternatives to Countly?
Top Countly alternatives in Analytics are ranked by recent ship velocity. Browse the "Countly alternatives" section above for the current picks, or visit /alternatives/countly for the full list with editorial commentary on each.