WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
FoRecoML vs lintr
A side-by-side editorial comparison of FoRecoML and lintr — release velocity, themes, recent moves, and the top alternatives to consider.
FoRecoML vs lintr: at a glance
What is FoRecoML?
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.
What is lintr?
lintr makes the native pipe the default rule and clears out a decade of deprecations
lintr is the static analysis standard for R packages, and its 3.3.0 release does two things at once: it changes pipe_consistency_linter() to require the native pipe, following the Tidyverse Style Guide, and it completes a long deprecation program — six linters fully deprecated, several arguments defunct, and a batch of functions removed outright. The 3.1.x line before it was accuracy work and a maintainer handoff to Michael Chirico.
FoRecoML vs lintr: editorial side-by-side
FoRecoML
0.0INFRA · APIS
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
◆ Current state
FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.
◆ Where it's heading
This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.
◆ Prediction
With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.
lintr
0.0INFRA · APIS
lintr makes the native pipe the default rule and clears out a decade of deprecations
◆ Current state
lintr is the static analysis standard for R packages, and its 3.3.0 release does two things at once: it changes pipe_consistency_linter() to require the native pipe, following the Tidyverse Style Guide, and it completes a long deprecation program — six linters fully deprecated, several arguments defunct, and a batch of functions removed outright. The 3.1.x line before it was accuracy work and a maintainer handoff to Michael Chirico.
◆ Where it's heading
The package has been consolidating: overlapping linters renamed and merged, configuration validated up front, and an experimental R-script config offered as a possible replacement for the DCF format. Alongside that, a sustained campaign against false positives and false negatives in individual linters, which is where most contributor effort goes.
◆ Prediction
Expect the six warning-deprecated linters to be removed in the next release as announced, and continued movement on the R-script configuration format if feedback supports it.
Alternatives to FoRecoML and lintr
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 FoRecoML or lintr.
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 FoRecoML alternatives → · See all lintr alternatives →
Recent activity from FoRecoML and lintr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
- 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
- 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN ⚡
- 8mo agolintrNative pipe required by default; six linters deprecated ⚡
- 2y agolintrFalse positive and negative fixes; new CRAN maintainer
- 2y agolintrExperimental R-script configs; up-front config validation
- 3y agolintrLinter renames for consistency; Super-Linter config discovery
- 3y agolintrTest no longer leaves cache files behind
- 3y agolintrfunction_argument_linter() added; seq_linter() covers dplyr and data.table
Frequently asked questions
What is the difference between FoRecoML and lintr?
They serve adjacent needs but don't currently overlap on shipped themes. FoRecoML and lintr 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 FoRecoML better than lintr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoRecoML and lintr 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 FoRecoML?
Top FoRecoML alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoRecoML alternatives" section above for the current picks, or visit /alternatives/forecoml for the full list with editorial commentary on each.
What are the best alternatives to lintr?
Top lintr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lintr alternatives" section above for the current picks, or visit /alternatives/lintr for the full list with editorial commentary on each.