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 Vault — 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.
Vault under IBM lands 2.0.0, with FIPS 140-3 and HSM enterprise builds inside two weeks.
Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.
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.
Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.
This is the cadence of a project completing a major-version rollout — community GA first, then RC and GA enterprise-flavor builds, then security-tracking SDK backports — rather than a roadmap pivot. The fact that FIPS 140-3 and HSM enterprise builds shipped in the same window as the 2.0 cycle is the signal worth holding onto: Vault's federal and regulated-industry posture is being kept intact under the new owner, and auth plugin version bumps suggest the wider ecosystem is staying in step.
Expect 2.x feature-bearing minor releases over the next few months, with FIPS 140-3 and HSM enterprise variants tracked alongside the community builds. GA bumps for the auth plugins to match the 2.x line are likely. Worth watching for more visible IBM branding or any Cloud-side packaging shifts that signal repositioning under the new owner.
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 Vault.
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 Vault 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 Vault 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 Vault 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 Vault alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Vault alternatives" section above for the current picks, or visit /alternatives/vault for the full list with editorial commentary on each.