rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
Cobbler vs PEIMAN2
A side-by-side editorial comparison of Cobbler and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
Cobbler vs PEIMAN2: at a glance
What is Cobbler?
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.
What is PEIMAN2?
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.
Cobbler vs PEIMAN2: editorial side-by-side
Cobbler
0.0INFRA · APIS
A backport branch kept alive for downstreams, with the main line nowhere in sight.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
PEIMAN2
0.0INFRA · APIS
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Cobbler and PEIMAN2
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 PEIMAN2.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all Cobbler alternatives → · See all PEIMAN2 alternatives →
Recent activity from Cobbler and PEIMAN2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoCobblerCobbler 3.2.3 backports the CVE-2024-47533 admin API fix
- 2mo agoPEIMAN2Database updates decouple from package releases ⚡
- 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
- 1y agoPEIMAN2Documentation fix for the second example dataset
- 1y agoCobblerCobbler 3.3.7 closes an admin-API authentication bypass
- 2y agoCobblerCobbler 3.3.6 adds EFI support to buildiso
- 2y agoCobblerCobbler 3.3.5 adds collection indices and lazy loading
- 2y agoCobblerCobbler 3.3.4 extends packaging to Ubuntu 22.04 and Debian 12
- 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
- 4y agoCobblerCobbler 3.3.3 adds resolved-value XML-RPC endpoints for Uyuni
Frequently asked questions
What is the difference between Cobbler and PEIMAN2?
They serve adjacent needs but don't currently overlap on shipped themes. Cobbler 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.
Is Cobbler better than PEIMAN2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cobbler 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.
What are the best alternatives to Cobbler?
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.
What are the best alternatives to PEIMAN2?
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.