WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
FoReco vs Transmission
A side-by-side editorial comparison of FoReco and Transmission — release velocity, themes, recent moves, and the top alternatives to consider.
FoReco vs Transmission: at a glance
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.
What is Transmission?
Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.
The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.
FoReco vs Transmission: editorial side-by-side
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.
Transmission
0.0INFRA · APIS
Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.
◆ Current state
The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.
◆ Where it's heading
The interesting work is at the integration boundary, not in the download engine: the RPC surface has been standardised and renamed, and beta.5 was largely spent repairing what those changes broke, including backwards-incompatible keys accidentally written into settings files. That is the cost profile of an API migration in a project with a large ecosystem of third-party remotes. With feature freeze held for seven months and no 4.1.0 final, the release is late relative to its own stated plan.
◆ Prediction
The next release should be 4.1.0 final or a further beta rather than new features, since the branch is frozen — but the entries give no signal on what is holding it.
Alternatives to FoReco and Transmission
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 FoReco or Transmission.
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 FoReco alternatives → · See all Transmission alternatives →
Recent activity from FoReco and Transmission
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
- 7mo agoTransmission4.1.0-beta.5 enters feature freeze and repairs settings-file damage
- 8mo agoTransmission4.1.0-beta.4 replaces the RPC API with a JSON-RPC 2.0 one ⚡
- 9mo agoTransmission4.1.0-beta.3 adds proxy support and streaming-friendly sequential writes
- 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
- 1y agoTransmission4.1.0-beta.2 adds sequential downloading and BEP-7 tracker fallback
- 1y agoTransmission4.1.0-beta.1 opens a branch two years in development
- 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions
Frequently asked questions
What is the difference between FoReco and Transmission?
They serve adjacent needs but don't currently overlap on shipped themes. FoReco and Transmission 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 FoReco better than Transmission?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and Transmission 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 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.
What are the best alternatives to Transmission?
Top Transmission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Transmission alternatives" section above for the current picks, or visit /alternatives/transmission for the full list with editorial commentary on each.