WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of dqcheckr and legendry — 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 ggplot2 extension quietly turning axes and legends into a place where other plots can live.
legendry extends ggplot2's guide system, letting axes and legends be composed from primitives and keys rather than accepted as given. The most recent release added guides for user-defined keys, upset matrices, arbitrary symbol placement, freeform annotations, and side-plots attached to an axis, plus a run-length-encoded range key and subtitles on custom axes. Between feature releases the package ships small patches, several of them tracking ggplot2's own changes.
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.
legendry extends ggplot2's guide system, letting axes and legends be composed from primitives and keys rather than accepted as given. The most recent release added guides for user-defined keys, upset matrices, arbitrary symbol placement, freeform annotations, and side-plots attached to an axis, plus a run-length-encoded range key and subtitles on custom axes. Between feature releases the package ships small patches, several of them tracking ggplot2's own changes.
The direction is toward treating a guide as a rendering slot rather than a label strip. Dendrogram scales arrived in 0.2.0 with a matching axis guide; the newest release adds side-plots and upset symbol matrices to the same position. Each of these puts real graphical content where an axis used to be, and each one ships with a key function so the composition stays user-controllable. Note that this feed's order is unreliable: 0.2.1 was published eight months after 0.2.4 and minutes before 0.3.0, so neither version numbers nor timestamps indicate release order here.
The pattern of pairing each new guide with a matching key function is consistent enough that the next feature release will likely follow it again; the recurring forwards-compatibility patches also suggest another ggplot2-tracking release whenever upstream moves.
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 legendry.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all dqcheckr alternatives → · See all legendry 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 legendry alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "legendry alternatives" section above for the current picks, or visit /alternatives/legendry for the full list with editorial commentary on each.