Casdoor
casdoor ships several times a day, mostly tightening organization boundaries.
A side-by-side editorial comparison of dittodb and pkgdown — 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.
pkgdown now generates llms.txt and a markdown copy of every documentation page
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
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.
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
Two audiences are now being served from one build. Human-facing work continues in small increments - dark-mode plot filtering, new translations, a local http server so search works in preview - while the new machine-facing output is opt-out rather than opt-in. The default matters more than the feature: thousands of package sites will start emitting llms.txt without their maintainers choosing to.
Expect the markdown output to gain the same configuration surface the HTML has, and the llms.txt contents to get more selective as maintainers discover what ends up in it; a way to exclude individual pages is the obvious next request.
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 pkgdown.
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
waldo keeps shedding dependencies while teaching its diff engine new object systems
See all dittodb alternatives → · See all pkgdown alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dittodb and pkgdown 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 pkgdown 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 pkgdown alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgdown alternatives" section above for the current picks, or visit /alternatives/pkgdown for the full list with editorial commentary on each.