mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
Countly vs timetk
A side-by-side editorial comparison of Countly and timetk — release velocity, themes, recent moves, and the top alternatives to consider.
Countly vs timetk: at a glance
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.
What is timetk?
timetk swallowed anomalize whole, then went quiet for two years
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
Countly vs timetk: editorial side-by-side
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.
timetk
0.0ANALYTICS
timetk swallowed anomalize whole, then went quiet for two years
◆ Current state
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
◆ Where it's heading
The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.
◆ Prediction
The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.
Alternatives to Countly and timetk
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 Countly or timetk.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
tidyposterior
A finished Bayesian model-comparison package in pure maintenance mode
See all Countly alternatives → · See all timetk alternatives →
Recent activity from Countly and timetk
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
- 10d agoCountlyFixes for event keys containing special characters
- 10d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
- 21d agoCountlyStar-rating logo path and data-manager transformation fixes
- 22d agoCountlyLTS backport: data-manager transformation fix
- 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
- 11mo agotimetktimetk 2.9.1 makes date parsing consistent across time classes
- 2y agotimetktimetk 2.9.0 absorbs the anomalize package ⚡
- 4y agotimetktimetk 2.8.1 exposes trelliscope plotting parameters
- 4y agotimetktimetk 2.8.0 adds trelliscopejs support for many-series plots
- 4y agotimetktimetk 2.7.0 adds tk_tsfeatures() for grouped feature matrices
- 4y agotimetktimetk 2.6.2 adds .week_start and facet direction controls
Frequently asked questions
What is the difference between Countly and timetk?
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 Countly better than timetk?
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 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.
What are the best alternatives to timetk?
Top timetk alternatives in Analytics are ranked by recent ship velocity. Browse the "timetk alternatives" section above for the current picks, or visit /alternatives/timetk for the full list with editorial commentary on each.