rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of Cobbler and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
A backport branch kept alive for downstreams, with the main line nowhere in sight.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
This is a stabilization branch serving downstream packagers rather than a product advancing on its own. The work that does land splits cleanly into three buckets: distribution coverage (Ubuntu 22.04, Debian 12, AlmaLinux, RHEL9, openSUSE and SLE signatures), API surface for integrators, and security backports. 3.3.3 flagged dump_vars as the replacement for get_blended_data as of 3.4.0 — a version that has not appeared in any release since.
Expect continued single-purpose backports to 3.3.x and older branches as CVEs surface; the entries give no indication of when or whether the 3.4.0 work these releases keep deferring to will ship.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
The package is stabilizing its input contract rather than growing its filtering methods. Metadata column names are now forced lowercase inside import_data() regardless of how the file was written, imported peak_tables names not present in the injection column are lowercased too, and get_meta_data() was renamed to get_metadata() in the same pass. Before that the work was infrastructural — Rcpp introduced to speed up filtering, data.table moved from Depends to Imports, and memory errors cleared so the package passes Valgrind and both sanitizers. Note the earliest entry compares against a v1.0.0 tag that precedes 0.1.0 in the repository, so version ordering in this feed is not reliable.
The case-normalization work has now touched both metadata columns and peak table names across two consecutive releases, which suggests the input-matching problem is not fully closed and a third pass is plausible. Nothing in these entries points to new filtering methods.
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 Cobbler or mpactr.
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 Cobbler alternatives → · See all mpactr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cobbler and mpactr 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. Cobbler and mpactr 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 Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler for the full list with editorial commentary on each.
Top mpactr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mpactr alternatives" section above for the current picks, or visit /alternatives/mpactr for the full list with editorial commentary on each.