Casdoor
casdoor ships several times a day, mostly tightening organization boundaries.
A side-by-side editorial comparison of dittodb and waldo — release velocity, themes, recent moves, and the top alternatives to consider.
dittodb has spent four years on CRAN link fixes and one DBI bump.
dittodb records and replays database interactions so tests can run without a live database, sitting behind DBI and dbplyr. The visible history splits cleanly in two: functional work through 0.1.8 broadening which databases and situations can be captured, then three consecutive maintenance releases. The most recent adds DBI 1.3.0 compatibility and nothing else.
waldo keeps shedding dependencies while teaching its diff engine new object systems
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
dittodb records and replays database interactions so tests can run without a live database, sitting behind DBI and dbplyr. The visible history splits cleanly in two: functional work through 0.1.8 broadening which databases and situations can be captured, then three consecutive maintenance releases. The most recent adds DBI 1.3.0 compatibility and nothing else.
The functional direction was always coverage: more databases, more situations that can be mocked, better failure messages when the recording setup is wrong. That work stopped after 0.1.8 in 2024, and the package has since only answered CRAN link checks and a DBI release. Full transaction support with separate mock directories was flagged as planned back in 0.1.4 and has not appeared.
The last three releases are pure upkeep, so the next most likely tracks another DBI or dbplyr change rather than delivering the transaction support still outstanding.
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.
Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.
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 dittodb or waldo.
casdoor ships several times a day, mostly tightening organization boundaries.
downlit's HTML contract was set in 0.4.0; every release since tracks R itself.
connectapi is becoming the scripted administration surface for Posit Connect.
chromote turned the browser itself into a pinned, downloadable dependency.
lifecycle gave the tidyverse the word superseded, then spent years tuning who gets warned
pkgdown now generates llms.txt and a markdown copy of every documentation page
See all dittodb alternatives → · See all waldo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — testing — within Infra & APIs. dittodb and waldo are shipping at a similar cadence (velocity 0.0 vs 0.0, 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. dittodb and waldo are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top dittodb alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dittodb alternatives" section above for the current picks, or visit /alternatives/dittodb for the full list with editorial commentary on each.
Top waldo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "waldo alternatives" section above for the current picks, or visit /alternatives/waldo for the full list with editorial commentary on each.