← Back to home
Comparison · Infra & APIs

FoRecoML vs Quay

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

FoRecoML vs Quay: at a glance

FeatureFoRecoMLQuay
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriescontainer-registry, cve-remediation, ssrf-hardening, backports
Last editorial update53m ago7d ago
WebsiteVisit →Visit →

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.

Read the full FoRecoML trajectory →

What is Quay?

Quay ships nothing but CVE remediation, mirrored across two supported branches

Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.

Read the full Quay trajectory →

FoRecoML vs Quay: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

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.

Q
Quay
INFRA · APIS
5.0

Quay ships nothing but CVE remediation, mirrored across two supported branches

◆ Current state

Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.

◆ Where it's heading

This is a registry in pure maintenance posture on its long-lived branches, with the release process itself automated down to changelog-bump commits. The recurring SSRF fixes across proxy cache and mirroring suggest a deliberate sweep through the code paths that fetch from upstream registries rather than isolated reports. Feature development, if it is happening, is landing on a branch this feed does not cover.

◆ Prediction

Expect the paired-branch cadence to continue at roughly the rate advisories land against the bundled Python and npm dependencies. The SSRF sweep looks close to complete, having now covered both proxy cache and mirroring.

Alternatives to FoRecoML and Quay

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 Quay.

See all FoRecoML alternatives → · See all Quay alternatives →

Recent activity from FoRecoML and Quay

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

  1. 7d agoQuayv3.12.21 patches six advisories and blocks SSRF in mirroring
  2. 7d agoQuayv3.10.25 carries the same advisory fixes to the 3.10 branch
  3. 27d agoQuayv3.12.20 bumps Go and blocks SSRF in proxy cache config
  4. 1mo agoQuayv3.10.24 backports the Go bump and proxy cache SSRF fix
  5. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  6. 1mo agoQuayv3.10.23 clears PyJWT, urllib3 and shell-quote advisories
  7. 1mo agoQuayv3.12.19 clears the same four dependency advisories
  8. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  9. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN

Frequently asked questions

What is the difference between FoRecoML and Quay?

They serve adjacent needs but don't currently overlap on shipped themes. Quay 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 FoRecoML better than Quay?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Quay 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 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 Quay?

Top Quay alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Quay alternatives" section above for the current picks, or visit /alternatives/quay for the full list with editorial commentary on each.