← Back to home
Comparison · Infra & APIs

EDAForge vs FoReco

A side-by-side editorial comparison of EDAForge and FoReco — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

EDAForge vs FoReco: at a glance

FeatureEDAForgeFoReco
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesdata-quality, validation, eda, cranforecasting, hierarchical-reconciliation, time-series, s3-classes
Last editorial update1h ago53m ago
WebsiteVisit →Visit →

What is EDAForge?

EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.

EDAForge's release feed shows a package changing identity between its first two tags. The v0.1.0 notes describe DataAudit, a data-quality auditing package built around audit_data(), reusable audit_rules() and audit_score(), with install instructions still pointing at vinodhpmd/DataAudit, while the repository now serves EDAForge. Only three tags exist, one of which is a bare compare link with no notes, and the most recent is a CRAN-policy cleanup rather than feature work.

Read the full EDAForge trajectory →

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.

Read the full FoReco trajectory →

EDAForge vs FoReco: editorial side-by-side

E
EDAForge
INFRA · APIS
5.0

EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.

◆ Current state

EDAForge's release feed shows a package changing identity between its first two tags. The v0.1.0 notes describe DataAudit, a data-quality auditing package built around audit_data(), reusable audit_rules() and audit_score(), with install instructions still pointing at vinodhpmd/DataAudit, while the repository now serves EDAForge. Only three tags exist, one of which is a bare compare link with no notes, and the most recent is a CRAN-policy cleanup rather than feature work.

◆ Where it's heading

The substance so far is all in the DataAudit-named 0.1.0: more than a dozen check families spanning missing values, duplicates, ranges, patterns, dependencies and grouped sequences, wrapped in a structured report object with print and summary methods. The 0.1.1 that follows removes a default output path, moves examples to tempdir() and adds an introductory vignette, which is the standard shape of a package being made acceptable to CRAN. The public identity is currently ahead of the release notes, so a reader arriving at the feed cannot tell from it what EDAForge does.

◆ Prediction

Expect the next tag to align the notes with the EDAForge name and add exploratory-analysis functions alongside the auditing core; the compliance pass in 0.1.1 points at a CRAN submission as the near-term goal.

F
FoReco
INFRA · APIS
0.0

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 EDAForge 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 EDAForge or FoReco.

See all EDAForge alternatives → · See all FoReco alternatives →

Recent activity from EDAForge and FoReco

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 18d agoEDAForgeCRAN-policy pass: no default write path, intro vignette
  2. 22d agoEDAForgeInitial release under the package's former name, DataAudit
  3. 27d agoEDAForgeEDAForge v0.1.0
  4. 1mo agoFoRecoStrict argument validation and a pruned help index
  5. 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object
  6. 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
  7. 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
  8. 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
  9. 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions

Frequently asked questions

What is the difference between EDAForge and FoReco?

Both compete on the same themes — r-package — within Infra & APIs. EDAForge 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 EDAForge better than FoReco?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EDAForge 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to EDAForge?

Top EDAForge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "EDAForge alternatives" section above for the current picks, or visit /alternatives/edaforge 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.