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 Scrypted — 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.
Scrypted spent a year making its camera server run as a cluster, then went quiet.
Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.
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.
Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.
The direction through the tracked window is a home camera server growing into distributed infrastructure: cluster mode, cluster-aware media management, worker addressing, and detection work moving onto custom models and fp16 math. Integration breadth continues alongside it, with HomeKit audio, ONVIF PTZ, text overlays, and PIR sensors. Because the feed has not produced a tag in months, any read on current direction should be treated as the state at the last release rather than today.
The entries do not support a confident prediction; the feed has been silent since November 2025, and a stale release stream is not evidence of what the project is doing now.
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 Scrypted.
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 Scrypted alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 Scrypted alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Scrypted alternatives" section above for the current picks, or visit /alternatives/scrypted for the full list with editorial commentary on each.