rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of melodi and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
INSEE's statistics API gets a French R client that keeps meeting its edge cases
Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.
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.
Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.
The work is convergence with an API that is still moving. Version 0.3.0 added label lookups so codes become readable; 1.0.0 centralised configuration; 1.0.1 and 1.0.2 each fix a place where a real dataset does not match the assumed shape — get_range_geo() needing an extra label field, then the consumer price index series naming its value column differently from every other dataset. Release notes are in French, which is consistent with the audience.
The 1.0.x pattern is one dataset-shape exception per release, which suggests the client is still discovering how much the Melodi datasets vary rather than converging on a general parser. Expect more of the same until the variation is handled generically.
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 melodi or PEIMAN2.
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
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 melodi 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. melodi 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. melodi 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 melodi alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "melodi alternatives" section above for the current picks, or visit /alternatives/melodi 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.