← Back to home
Comparison · Infra & APIs

dqcheckr vs survivoR

A side-by-side editorial comparison of dqcheckr and survivoR — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

dqcheckr vs survivoR: at a glance

FeaturedqcheckrsurvivoR
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesdata-quality, duckdb, drift-analysis, yaml-configdata-package, r-package, television, reality-tv
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is dqcheckr?

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.

Read the full dqcheckr trajectory →

What is survivoR?

A Survivor data package that keeps turning a TV show into a relational database

survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.

Read the full survivoR trajectory →

dqcheckr vs survivoR: editorial side-by-side

D
dqcheckr
INFRA · APIS
2.5

dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

S
survivoR
INFRA · APIS
0.0

A Survivor data package that keeps turning a TV show into a relational database

◆ Current state

survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.

◆ Where it's heading

The work is less about adding seasons than about making the tables join cleanly. 2.3.1 rebuilt challenge_description and challenge_results around a shared challenge_id, added challenge characteristic flags and result notes, and put logical finalist, winner and jury flags on castaways. Since then the pattern repeats at smaller scale: boot_order as its own table, season_name deprecated everywhere except season_summary, castaways cleaned so people booted twice appear once. Derived analytical columns are being separated from raw records rather than mixed into them.

◆ Prediction

Expect the next release to add the current season's data on the same broadcast-following cadence, with any structural work continuing to split derived scores out of the raw tables.

Alternatives to dqcheckr and survivoR

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 survivoR.

See all dqcheckr alternatives → · See all survivoR alternatives →

Recent activity from dqcheckr and survivoR

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 24d agodqcheckrConfig generation from data sniffing; run listing added
  2. 2mo agodqcheckrDuckDB CSV ingestion fixed for undetectable delimiters
  3. 2mo agodqcheckrSnapshot drift analysis arrives; reports move to Quarto
  4. 2mo agosurvivoRUS50 and AU12 land, castaway scores split into three tiers
  5. 7mo agosurvivoRUS49 data completed and season 50 cast added
  6. 11mo agosurvivoRSurvivor Australia vs. The World added
  7. 1y agosurvivoRboot_order table added and castaways deduplicated
  8. 2y agosurvivoRComplete AU09 data reaches CRAN
  9. 2y agosurvivoRChallenge tables rebuilt around a shared linking key

Frequently asked questions

What is the difference between dqcheckr and survivoR?

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.

Is dqcheckr better than survivoR?

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.

What are the best alternatives to dqcheckr?

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.

What are the best alternatives to survivoR?

Top survivoR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "survivoR alternatives" section above for the current picks, or visit /alternatives/survivor for the full list with editorial commentary on each.