FoReco
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
A side-by-side editorial comparison of projoint and Quay — release velocity, themes, recent moves, and the top alternatives to consider.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
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.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
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.
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.
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.
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 projoint or Quay.
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
See all projoint alternatives → · See all Quay alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Quay is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Quay is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.
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.