WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
estimatr vs FoReco
A side-by-side editorial comparison of estimatr and FoReco — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
estimatr vs FoReco: at a glance
What is estimatr?
Fast design-based estimators for experiments, coasting on CRAN patches.
estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.
What is FoReco?
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.
estimatr vs FoReco: editorial side-by-side
estimatr
0.0INFRA · APIS
Fast design-based estimators for experiments, coasting on CRAN patches.
◆ Current state
estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.
◆ Where it's heading
Direction cannot be read from this feed. The release notes are unedited merge-commit messages, so the only signal is cadence — roughly annual, each release framed as a CRAN patch rather than as feature work. That pattern is consistent with a package whose estimators are considered finished and which now moves only when CRAN policy requires it.
◆ Prediction
On the evidence here the next release is another CRAN compliance patch, but the notes are too thin to support a confident read of what the maintainers are actually working on.
FoReco
0.0INFRA · APIS
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
◆ Current state
FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.
◆ Where it's heading
The package is completing a reversal it started in 1.0.0. That release simplified outputs to plain matrices and pushed metadata into attributes reachable via recoinfo(); 1.3.0 removed recoinfo() outright and put the structure back as a class with components(), summary(), and plot() methods. The direction is toward being infrastructure rather than a function library — the class is exported through new_foreco_class() and a sibling package has already adopted it. Method coverage has meanwhile broadened from optimal combination into non-negative algorithms, bounded reconciliation, and Gaussian and sample-based probabilistic variants.
◆ Prediction
The soft-deprecated res2matrix() is flagged for removal, so a subsequent release should finish that cleanup; with the class now exported, expect more methods to hang off foreco objects rather than more top-level functions.
Alternatives to estimatr and FoReco
Other Infra & APIs 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 estimatr or FoReco.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all estimatr alternatives → · See all FoReco alternatives →
Recent activity from estimatr and FoReco
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoFoRecoStrict argument validation and a pruned help index
- 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object ⚡
- 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
- 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
- 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
- 1y agoestimatrCRAN version 1.0.4
- 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions
- 2y agoestimatrCRAN version 1.0.2
- 3y agoestimatrCRAN version 1.0.0
Frequently asked questions
What is the difference between estimatr and FoReco?
Both compete on the same themes — r-package — within Infra & APIs. estimatr and FoReco 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 estimatr better than FoReco?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. estimatr and FoReco 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to estimatr?
Top estimatr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "estimatr alternatives" section above for the current picks, or visit /alternatives/estimatr for the full list with editorial commentary on each.
What are the best alternatives to FoReco?
Top FoReco alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoReco alternatives" section above for the current picks, or visit /alternatives/foreco for the full list with editorial commentary on each.