tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of dendroNetwork and taxizedb — 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.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
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.
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.
Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.
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 taxizedb.
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 taxizedb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. dendroNetwork and taxizedb 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 taxizedb 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 taxizedb alternatives in Analytics are ranked by recent ship velocity. Browse the "taxizedb alternatives" section above for the current picks, or visit /alternatives/taxizedb for the full list with editorial commentary on each.