tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of dendroNetwork and ReLTER — release velocity, themes, recent moves, and the top alternatives to consider.
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
ReLTER provides programmatic access to the eLTER network — the European long-term ecosystem research infrastructure — pulling site metadata, datasets and activities from DEIMS-SDR and enriching them with taxonomic resolution via PESI and WORMS and raster layers from European OpenDataScience. Version 1.0.0 consolidated the function surface and passed into rOpenSci review; 1.1.0 addressed the reviewers' feedback and added vignettes and a Docker install path. Version 2.0.0 was tagged in late 2022 with release notes consisting only of a merge commit message, and nothing has shipped since.
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.
No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.
ReLTER provides programmatic access to the eLTER network — the European long-term ecosystem research infrastructure — pulling site metadata, datasets and activities from DEIMS-SDR and enriching them with taxonomic resolution via PESI and WORMS and raster layers from European OpenDataScience. Version 1.0.0 consolidated the function surface and passed into rOpenSci review; 1.1.0 addressed the reviewers' feedback and added vignettes and a Docker install path. Version 2.0.0 was tagged in late 2022 with release notes consisting only of a merge commit message, and nothing has shipped since.
The visible arc runs from a scattered set of getSite* functions to a reviewed, documented package, and then stops. The absence of notes on the 2.0.0 tag makes it impossible to say from this feed what that major version changed, and the three-year silence afterwards is the more informative signal. What the package does remains useful — the eLTER data it wraps has no other R interface — but the release history gives no evidence of active development.
Nothing in these entries supports a confident prediction about future releases; the feed shows a major version with no notes followed by silence. Whether the package is dormant or simply publishing releases elsewhere cannot be determined from what is here.
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 dendroNetwork or ReLTER.
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.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
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.
See all dendroNetwork alternatives → · See all ReLTER alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. dendroNetwork and ReLTER 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. dendroNetwork and ReLTER 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 dendroNetwork alternatives in Analytics are ranked by recent ship velocity. Browse the "dendroNetwork alternatives" section above for the current picks, or visit /alternatives/dendronetwork for the full list with editorial commentary on each.
Top ReLTER alternatives in Analytics are ranked by recent ship velocity. Browse the "ReLTER alternatives" section above for the current picks, or visit /alternatives/relter for the full list with editorial commentary on each.