← Back to home
Comparison · Infra & APIs

retroharmonize vs SuperTokens

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

retroharmonize vs SuperTokens: at a glance

FeatureretroharmonizeSuperTokens
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themessurvey-data, data-harmonization, labelled-data, reproducibilityauthentication, saml, user-migration, account-linking
Last editorial update53m ago12d ago
WebsiteVisit →Visit →

What is retroharmonize?

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

Read the full retroharmonize trajectory →

What is SuperTokens?

SuperTokens is hardening SAML and building a migration path off other auth providers.

SuperTokens is an open-source authentication service, and its core repo is running a 12.0 canary line alongside stable patches. The work in this window falls into two piles: SAML security — XML signature wrapping protection in 12.0.2-canary, further hardening in the 12.0.10 release — and migration mode, where new core-user-data records can be created as MIGRATED and the transition is now blocked while inconsistent users exist. Release notes are thin, usually a PR title or two per tag.

Read the full SuperTokens trajectory →

retroharmonize vs SuperTokens: editorial side-by-side

R
retroharmonize
INFRA · APIS
0.0

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

◆ Current state

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

◆ Where it's heading

The design bet has been constant since the first release — comprehensive S3 classes that carry labels and missing-value semantics through every transformation, so the harmonization is documented rather than reconstructed. What has changed is where effort goes. Early releases added harmonization functions and a worked Arab Barometer case study; recent ones are code quality and CRAN survival. Note that the version numbering in this feed is not monotonic: 0.1.13 was released roughly nine months before 0.1.7, so version order here does not indicate release order.

◆ Prediction

Having just restored CRAN availability through a refactor rather than a feature, the near-term work is most likely consolidation of the vctrs integration the notes describe rather than new harmonization functions.

S
SuperTokens
INFRA · APIS
2.5

SuperTokens is hardening SAML and building a migration path off other auth providers.

◆ Current state

SuperTokens is an open-source authentication service, and its core repo is running a 12.0 canary line alongside stable patches. The work in this window falls into two piles: SAML security — XML signature wrapping protection in 12.0.2-canary, further hardening in the 12.0.10 release — and migration mode, where new core-user-data records can be created as MIGRATED and the transition is now blocked while inconsistent users exist. Release notes are thin, usually a PR title or two per tag.

◆ Where it's heading

Migration mode plus account-linking exploration is the tell: this is infrastructure for importing an existing user base from another provider without breaking identity linkage mid-flight, and the guard added in 12.0.5-canary shows they hit the inconsistent-state case in practice. The SAML work runs in parallel because enterprise SAML is what a team is usually migrating toward. Also worth noting: an automated contributor, supertokens-agent-runner, opened its first PRs in this window, so part of the fix and test volume is now agent-authored.

◆ Prediction

A stable 12.x release consolidating the canary migration-mode work is the readable next step, likely once the MIGRATED transition guards have run without incident. More SAML hardening should be expected given two separate fixes landed in this window alone.

Alternatives to retroharmonize and SuperTokens

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 retroharmonize or SuperTokens.

See all retroharmonize alternatives → · See all SuperTokens alternatives →

Recent activity from retroharmonize and SuperTokens

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

  1. 13d agoSuperTokensSAML hardening lands on the stable 12.0 line
  2. 1mo agoSuperTokensMigration mode blocks transition while inconsistent users exist
  3. 1mo agoSuperTokens12.0.4-canary ships with no described changes
  4. 1mo agoSuperTokensActivity log table put into use
  5. 2mo agoSuperTokensSAML gains XML signature wrapping protection
  6. 2mo agoSuperTokensNew core user data records can be created as MIGRATED
  7. 3mo agoretroharmonizeCRAN modernisation release
  8. 7mo agoretroharmonizeRelease candidate; notes cite code quality with no detail
  9. 4y agoretroharmonizeImproved documentation
  10. 5y agoretroharmonize0.1.7 With case study on harmonizing Arab Barometer surveys
  11. 5y agoretroharmonizeretroharmonize 0.1.13 is on CRAN
  12. 6y agoretroharmonize0.1.0 Retrospective harmonization of survey data files in R

Frequently asked questions

What is the difference between retroharmonize and SuperTokens?

They serve adjacent needs but don't currently overlap on shipped themes. SuperTokens is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is retroharmonize better than SuperTokens?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. SuperTokens is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to retroharmonize?

Top retroharmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "retroharmonize alternatives" section above for the current picks, or visit /alternatives/retroharmonize for the full list with editorial commentary on each.

What are the best alternatives to SuperTokens?

Top SuperTokens alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "SuperTokens alternatives" section above for the current picks, or visit /alternatives/supertokens for the full list with editorial commentary on each.