dscore
The D-score reference implementation rebuilt its measurement foundation on seven countries.
A side-by-side editorial comparison of lares and PEIMAN2 — 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.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
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.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
The package has been moving from a fixed snapshot toward versioned, user-selectable data. Earlier releases updated the bundled database in place — 1.0.0 shipped the March 2025 version and said little else — which meant the annotation vintage was whatever the package version implied. Now update_peiman_database() downloads and caches external database files and UniProt PTM lists, enrichment workflows take a database_version argument, and the mass-spec translators take a ptmlist_version, so an analysis can pin a dated database rather than a package release. The CRAN-safe default is preserved deliberately: loading, examples and checks still use the bundled internal data and need no network.
Version pinning is now expressible but the release notes do not describe how a chosen version is recorded in output, so surfacing the active database version in results is the natural companion. The database and the UniProt PTM list are versioned separately, which leaves room for a combined manifest.
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 PEIMAN2.
The D-score reference implementation rebuilt its measurement foundation on seven countries.
A football-viz package just swapped scraping for an API and broke its own output to do it.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
The recursive-computation engine under massProps grows the accessors its consumer needed
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
See all lares alternatives → · See all PEIMAN2 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 PEIMAN2 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 PEIMAN2 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 PEIMAN2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PEIMAN2 alternatives" section above for the current picks, or visit /alternatives/peiman2 for the full list with editorial commentary on each.