FoReco
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
A side-by-side editorial comparison of Drizzle ORM and nuggets — release velocity, themes, recent moves, and the top alternatives to consider.
Drizzle's 1.0 RC cycle pairs a performance rebuild with first-class agent tooling
Drizzle ORM is deep in its 1.0.0 release-candidate cycle. Two engineering thrusts dominate: a rewritten internals layer (codecs, JIT mappers, Effect v4) that fixes long-standing data-mapping bugs while cutting query latency, and a push to bring every dialect (Postgres, MySQL, SQLite) to parity under that new system. Alongside the ORM, Drizzle Kit is gaining machine-readable output and an explicit AI-agent surface.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
Drizzle ORM is deep in its 1.0.0 release-candidate cycle. Two engineering thrusts dominate: a rewritten internals layer (codecs, JIT mappers, Effect v4) that fixes long-standing data-mapping bugs while cutting query latency, and a push to bring every dialect (Postgres, MySQL, SQLite) to parity under that new system. Alongside the ORM, Drizzle Kit is gaining machine-readable output and an explicit AI-agent surface.
The codec system is the spine of this cycle — it unifies how drivers normalize data and unlocks both correctness fixes and speed. After porting it across dialects (rc.3 MySQL, rc.4 SQLite), Drizzle is converging on a stable 1.0. The newer signal is Drizzle Kit going agent-native: JSON output contracts, a programmatic SDK, an MCP server, and bundled Agent Skills aimed at AI coding assistants driving migrations.
Expect the RC cycle to wind toward a 1.0.0 stable release once remaining dialect parity (notably the SQLite Effect work) lands, with continued investment in the agent-facing Drizzle Kit surface.
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
Two forces are shaping the package. One is coverage: baseline, complement and paired-baseline contrasts, correlations, tautologies, ancestors and clustering have all been added as first-class dig_ or explore_ surfaces, so the same search engine now answers a widening set of questions. The other is weight — Shiny packages moved from Imports to Suggests, BH and RcppThread dropped, XSIMD updated, parse_condition() rewritten in C++ — which keeps a package with an interactive app from forcing that app's dependencies on every user. Deprecations are handled through lifecycle rather than removed abruptly.
Expect the sparse-data optimisation to extend from crisp to fuzzy data, and explore() to keep gaining tabs as each new pattern family lands, on the roughly six-week cadence the 2.2 line has held.
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 Drizzle ORM or nuggets.
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.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
See all Drizzle ORM alternatives → · See all nuggets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Drizzle ORM is currently shipping more aggressively (velocity 3.8 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. Drizzle ORM is currently shipping more aggressively (velocity 3.8 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 Drizzle ORM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Drizzle ORM alternatives" section above for the current picks, or visit /alternatives/drizzle for the full list with editorial commentary on each.
Top nuggets alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nuggets alternatives" section above for the current picks, or visit /alternatives/nuggets for the full list with editorial commentary on each.