← Back to home
Comparison · Infra & APIs

aftables vs PEIMAN2

A side-by-side editorial comparison of aftables and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.

aftables vs PEIMAN2: at a glance

FeatureaftablesPEIMAN2
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesaccessibility, spreadsheets, government-statistics, openxlsx2proteomics, post-translational-modification, enrichment-analysis, reproducibility
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is aftables?

Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.

aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.

Read the full aftables trajectory →

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.

Read the full PEIMAN2 trajectory →

aftables vs PEIMAN2: editorial side-by-side

A
aftables
INFRA · APIS
0.0

Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.

◆ Current state

aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.

◆ Where it's heading

The history reads in two phases. As a11ytables the work was about what belongs in an accessible spreadsheet, adding arbitrary pre-table metadata rows and enforcing rules such as rejecting tab titles that start with a numeral. Since the rename the work has been structural: a new backend, and configuration moved out of function arguments into a file that can be version-controlled and shared across a team. That second phase suits the audience, since government analysts producing recurring statistical releases want the same document properties applied every time rather than re-specified per run.

◆ Prediction

Expect the config.yaml surface to grow to cover more of what is currently passed as arguments, given it arrived alongside alternative author, title and keywords arguments that it plainly supersedes. With the openxlsx2 migration complete, further releases are likely to be formatting fixes surfaced by real departmental publications, as 2.0.1 already was.

P
PEIMAN2
INFRA · APIS
0.0

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 aftables 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 aftables or PEIMAN2.

See all aftables alternatives → · See all PEIMAN2 alternatives →

Recent activity from aftables and PEIMAN2

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agoPEIMAN2Database updates decouple from package releases
  2. 4mo agoaftablesrlang import restored for older R versions
  3. 5mo agoaftablesWorkbook engine moved to openxlsx2; config.yaml introduced
  4. 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
  5. 1y agoPEIMAN2Documentation fix for the second example dataset
  6. 1y agoaftablesPackage renamed from a11ytables to aftables
  7. 2y agoaftablesTab titles beginning with a numeral now rejected
  8. 2y agoaftablescustom_rows allows arbitrary pre-table metadata
  9. 2y agoaftablesTable count spelled out; README spelling corrected
  10. 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped

Frequently asked questions

What is the difference between aftables and PEIMAN2?

They serve adjacent needs but don't currently overlap on shipped themes. aftables 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 aftables better than PEIMAN2?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aftables 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 aftables?

Top aftables alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "aftables alternatives" section above for the current picks, or visit /alternatives/aftables 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.