FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
A side-by-side editorial comparison of dqcheckr and jstable — release velocity, themes, recent moves, and the top alternatives to consider.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
A clinical table generator paying down years of edge cases in survey-weighted models
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
Both moves point the same way: reduce what the operator has to write and know. Config generation removes the hand-authored YAML that gated first use, list_runs() and validate_config() make an existing setup inspectable, and the snapshot comparison turns accumulated run history into a second product surface. Check coverage keeps widening underneath — outlier detection, composite keys, row-count and file-size ceilings — and the reporting layer moved from rmarkdown to Quarto, with existing 0.1.x databases auto-migrated on first run.
Expect the generated configs and the drift reports to converge, so a sniffed config can seed thresholds from the snapshot history rather than from defaults, plus continued growth in the numbered QC check catalogue.
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
Each CRAN release bundles several GitHub patch versions, so the notes read as rolled-up fix lists rather than feature announcements. The substantive thread is pcut.univariate, introduced across seven display functions in 1.3.11 to allow multivariable analysis restricted to significant variables, and repaired repeatedly since as it collided with interaction terms, single-variable selections, clustered models and data.table inputs. The survey-weighted path is the other recurring source: counts, labels and family handling that worked for unweighted data kept failing once weights were involved.
Expect further patches in the survey-weighted subgroup functions, since 1.3.25 fixed four separate issues there and each recent release has surfaced more in the same area.
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 dqcheckr or jstable.
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
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.
See all dqcheckr alternatives → · See all jstable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. dqcheckr is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dqcheckr is currently shipping more aggressively (velocity 2.5 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.
Top dqcheckr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dqcheckr alternatives" section above for the current picks, or visit /alternatives/dqcheckr for the full list with editorial commentary on each.
Top jstable alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "jstable alternatives" section above for the current picks, or visit /alternatives/jstable for the full list with editorial commentary on each.