exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
A side-by-side editorial comparison of dqcheckr and restic — 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 backup tool whose roadmap is correctness, release after release
restic ships roughly two releases a year, and the changelogs are almost entirely fixes ordered by importance. The 0.19 line (June and July 2026) continues that pattern: mount safety, SFTP behavior on Windows servers, exclude handling, and exit-code semantics. New capability appears rarely and narrowly, usually as backend credential support rather than new commands.
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.
restic ships roughly two releases a year, and the changelogs are almost entirely fixes ordered by importance. The 0.19 line (June and July 2026) continues that pattern: mount safety, SFTP behavior on Windows servers, exclude handling, and exit-code semantics. New capability appears rarely and narrowly, usually as backend credential support rather than new commands.
The concentration of work is on the platforms where a backup tool is hardest to get right — Windows ACL inheritance and VSS metadata, macOS resource forks and FUSE mounts, SFTP and rclone backends under background execution. Running alongside that is a steady push toward being scriptable: distinct exit codes for missing source paths, snapshot removal failures and SIGINT, JSON output extended across more commands, and errors on invalid environment variables instead of silent defaults.
The next release will most likely be another 0.19.x patch of platform-specific fixes, since every minor in this window has been followed by one within a month or two.
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 restic.
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.
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.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all dqcheckr alternatives → · See all restic alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dqcheckr and restic are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 and restic are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 restic alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "restic alternatives" section above for the current picks, or visit /alternatives/restic for the full list with editorial commentary on each.