mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of lares and packageRank — release velocity, themes, recent moves, and the top alternatives to consider.
One analyst's toolbox, still shipping: Meta MMM tooling beside Wordle solvers
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
CRAN download analytics maintained one micro-change at a time, hundreds per year
packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
Over two years the Robyn tooling matured first — robyn_performance() and robyn_modelselector() were rebuilt release after release through 2024 — and recent work has drifted outward into media and API plumbing: encrypted file helpers in 5.3.2, then an iTunes-first metadata path, MP3 tag writing, and a move of holidays() onto the Nager.Date API in 5.4.0. Cadence is roughly quarterly and the package has been quiet for three months.
The pattern in nearly every release is that a third-party API moves and lares follows it — Meta's version bumps, Robyn 3.12.0, now Nager.Date. Expect the next release to be another compatibility pass plus whatever utility the author needed that week; nothing in these entries points at a structural change.
packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.
There is no directional arc here; there is a maintainer keeping a measurement instrument calibrated against a data source that keeps moving. CRAN's logs went missing for a week in 2025 and the package now ships those dates as data and draws them as polygons on every plot. A chatgpt argument has been threaded through the plotting functions since 0.9.6. Function surface churns constantly — arguments renamed, plot helpers archived, others integrated.
Given the cadence, the next release will be another few dozen adjustments concentrated wherever CRAN's logs last surprised the maintainer. The consolidation of plotting arguments toward a single axis.package annotation looks unfinished.
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 lares or packageRank.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all lares alternatives → · See all packageRank alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lares and packageRank 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. lares and packageRank 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 lares alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lares alternatives" section above for the current picks, or visit /alternatives/lares for the full list with editorial commentary on each.
Top packageRank alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "packageRank alternatives" section above for the current picks, or visit /alternatives/packagerank for the full list with editorial commentary on each.