tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of EDIutils and hoardr — release velocity, themes, recent moves, and the top alternatives to consider.
The EDI data client is being dragged through its repository's identity-system migration.
EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.
This is a client whose roadmap belongs to its server. Every meaningful release tracks something EDI changed — a deprecated endpoint, a resource outage breaking CRAN checks, and now a whole identity system — and the package's job is to absorb the churn while keeping the R interface stable. The 2.0.0 break was handled by pointing users at where to find their new EDI-ID rather than by papering over the change.
Expect continued follow-through on the IAM migration as the old auth token is fully retired, and further releases keyed to EDI service changes rather than to new client features.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
This is infrastructure that has reached its final shape. Three of the last three releases were reactive: two responses to CRAN test-failure notifications, one to a maintainer handover. The single behavioural change in that stretch — forward slashes in paths on every operating system — is a consistency fix for downstream packages rather than a feature. Its release cadence is set by CRAN's checks, not by demand.
Expect the next release to be triggered by another CRAN check failure rather than by new functionality, matching every release since 2018.
Other Analytics 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 EDIutils or hoardr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all EDIutils alternatives → · See all hoardr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci, r-package — within Analytics. EDIutils and hoardr 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. EDIutils and hoardr 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 Analytics products to evaluate alongside.
Top EDIutils alternatives in Analytics are ranked by recent ship velocity. Browse the "EDIutils alternatives" section above for the current picks, or visit /alternatives/ediutils for the full list with editorial commentary on each.
Top hoardr alternatives in Analytics are ranked by recent ship velocity. Browse the "hoardr alternatives" section above for the current picks, or visit /alternatives/hoardr for the full list with editorial commentary on each.