ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of pakret and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
Package citation for R documents, quietly growing to meet Quarto.
pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.
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.
pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.
Every release in this window removes a specific friction someone hit while writing a document. Bib files that had to exist beforehand now get created; single-letter package names like R and C stopped being lower-cased in titles; the package works when loaded after conflicted; citing many packages got faster; and version numbers became optional for documents where they are noise. The 0.3.1 Quarto support extends the same idea to the format its users are moving to. Nothing here is architectural, and nothing needs to be.
Expect continued alignment with Quarto as more of its syntax surfaces become relevant, and further refinement of how multi-reference packages resolve to a single entry, which the BibTeX type priority work in 0.2.0 started. The entries give no indication of a 1.0.
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 pakret or PEIMAN2.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore declared its API stable with every survey design type covered.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
A German electricity load-profile package added gas and doubled the market it serves.
See all pakret 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. pakret 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. pakret 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 pakret alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pakret alternatives" section above for the current picks, or visit /alternatives/pakret 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.