goat
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
A side-by-side editorial comparison of rollupTree and sdcMicro — release velocity, themes, recent moves, and the top alternatives to consider.
The recursive-computation engine under massProps grows the accessors its consumer needed
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
A 20-year anonymization toolbox now has a language model inside its refinement loop.
sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.
On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.
sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.
Two threads run in parallel. The visible one is the LLM-assisted anonymization path maturing: 5.8.2 gives its refinement loop early stopping via tol and patience so it stops when the combined utility score plateaus instead of burning all max_iter rounds, and teaches query_llm() to drop the temperature parameter for reasoning models that reject it. The other is unglamorous statistical correctness — a distinct l-diversity computation fixed for NAs in key variables, with the C++ simplified and tests added. The release also ships reproducibility scripts for a SoftwareX paper, which suggests the AI path is being written up rather than quietly trialled.
The provider-compatibility fix is reactive — a parameter dropped because one model family rejected it — so expect more of the same as query_llm() meets other backends. Given tol and patience were added to stop wasted iterations, cost or runtime of the refinement loop is the live concern, and further controls on it are the likeliest next move.
Other Infra & APIs 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 rollupTree or sdcMicro.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all rollupTree alternatives → · See all sdcMicro alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rollupTree and sdcMicro 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. rollupTree and sdcMicro 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 Infra & APIs products to evaluate alongside.
Top rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.
Top sdcMicro alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "sdcMicro alternatives" section above for the current picks, or visit /alternatives/sdcmicro for the full list with editorial commentary on each.