tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of dendroNetwork and sparsevctrs — 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.
Sparse vectors stopped being a storage trick and became something you can do arithmetic on
sparsevctrs supplies sparse vectors that live inside ordinary data frames and tibbles, which is what lets tidymodels carry wide, mostly-zero feature matrices without densifying them. Through 0.2.0 and 0.3.0 the package built out a computation layer on top of that storage — first summary statistics, then scalar and element-wise arithmetic — and everything since has been correctness work at the C level.
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.
sparsevctrs supplies sparse vectors that live inside ordinary data frames and tibbles, which is what lets tidymodels carry wide, mostly-zero feature matrices without densifying them. Through 0.2.0 and 0.3.0 the package built out a computation layer on top of that storage — first summary statistics, then scalar and element-wise arithmetic — and everything since has been correctness work at the C level.
The release pattern splits cleanly at 0.3.0. Before it, new functions arrive in batches; after it, five consecutive releases are bug fixes, and the bugs are the kind that come with hand-written sparse kernels: a stack imbalance when sparse_multiplication() returns all zeros, undefined behaviour in multiplication, type errors in sparse_is_na(), coercion failures on NA input. That is the expected cost of an ALTREP-backed numerical layer, and the fixes are landing steadily.
With the arithmetic surface in place and the recent releases all narrow fixes, the next one is more likely another correctness patch than a new function family. The R devel fix in 0.3.5 suggests upcoming R releases are the current source of breakage.
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 sparsevctrs.
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 sparsevctrs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dendroNetwork and sparsevctrs 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 sparsevctrs 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 sparsevctrs alternatives in Analytics are ranked by recent ship velocity. Browse the "sparsevctrs alternatives" section above for the current picks, or visit /alternatives/sparsevctrs for the full list with editorial commentary on each.