tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of cloudml and dendroNetwork — release velocity, themes, recent moves, and the top alternatives to consider.
Six years since the last functional change, and Google renamed the service it wraps in the release before that
cloudml lets R users train keras, tfestimators and tensorflow models on Google's managed machine learning service, tune hyperparameters there, and deploy the results. Its last release with functional content was 0.6.1 in September 2019, which adapted to Google renaming the service from ml-engine to ai-platform. The only entry since is a 2025 documentation update made to satisfy CRAN.
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.
cloudml lets R users train keras, tfestimators and tensorflow models on Google's managed machine learning service, tune hyperparameters there, and deploy the results. Its last release with functional content was 0.6.1 in September 2019, which adapted to Google renaming the service from ml-engine to ai-platform. The only entry since is a 2025 documentation update made to satisfy CRAN.
The visible arc is short and stops abruptly. Releases through 2018 tracked the TensorFlow runtime version and patched packaging problems; 0.6.1 added a customCommands hook so users could run OS-level setup before package installation, and adjusted to the service's new name. Then nothing for six years. A 2025 release containing only documentation changes is the standard signal of a package being kept on CRAN rather than being developed.
There is nothing in this feed to support a prediction of functional work. The most likely next event is another CRAN-driven documentation patch, or archival.
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.
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 cloudml or dendroNetwork.
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 cloudml alternatives → · See all dendroNetwork alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cloudml and dendroNetwork 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. cloudml and dendroNetwork 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 cloudml alternatives in Analytics are ranked by recent ship velocity. Browse the "cloudml alternatives" section above for the current picks, or visit /alternatives/cloudml for the full list with editorial commentary on each.
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.