rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of PEIMAN2 and PowerTOST — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A bioequivalence sample-size workhorse whose news is which regulator it now covers
PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.
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.
PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.
The package is in long maintenance with a widening regulatory surface: the statistical methods are settled, and releases arrive when an agency publishes a framework that can be expressed as a settings variant of an existing method. Function naming has been deliberately decoupled from any single agency, with the deprecated FDA-suffixed aliases carried for years before removal. Cadence has slowed to roughly one release every eighteen months.
The next release is most likely another regulator setting or a small fix; on the deprecation notice already given, the power.NTIDFDA()-style aliases are the obvious removal candidate.
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 PEIMAN2 or PowerTOST.
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 PEIMAN2 alternatives → · See all PowerTOST alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. PEIMAN2 and PowerTOST 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. PEIMAN2 and PowerTOST 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 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.
Top PowerTOST alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PowerTOST alternatives" section above for the current picks, or visit /alternatives/powertost for the full list with editorial commentary on each.