r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of CRediTas and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
A CRediT author-statement generator that renamed itself, then went quiet for two years.
CRediTas turns a contributor-roles table into a CRediT Author Statement for a paper. The 0.2.0 release in April 2023 did the heavy lifting — package rename, a full object_verb() API rename, and output that drops straight into R Markdown or Quarto. The 0.3.0 release in August 2025 is the only activity since and carries no changelog text beyond a pointer to NEWS.md.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
CRediTas turns a contributor-roles table into a CRediT Author Statement for a paper. The 0.2.0 release in April 2023 did the heavy lifting — package rename, a full object_verb() API rename, and output that drops straight into R Markdown or Quarto. The 0.3.0 release in August 2025 is the only activity since and carries no changelog text beyond a pointer to NEWS.md.
Development front-loaded a breaking cleanup during rOpenSci review and has coasted since. The design bet made in 0.2.0 — return a string for inline use rather than write a file — pointed the package at literate authoring workflows rather than at standalone scripts, and nothing since has moved away from it. The empty 0.3.0 note makes the current direction impossible to read from the feed.
Too little is published to call the next move; the 0.3.0 entry would need to carry its actual changes for the trajectory to be readable from the changelog at all.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
Four consecutive releases open with the same line — documentation and code updated for server-side changes, cited by OSM wiki revision range. That is a maintainer treating an evolving remote API as a versioned contract and auditing against it each cycle, which is unusual discipline and the main reason to trust this client over a hand-rolled wrapper. The second thread is fitting into R's spatial conventions rather than exposing OSM's, visible in the bbox coercion work and the httr2 upgrades landing with upstream help.
The pattern is stable enough to call: another release synchronised to the next OSM wiki revision range, adding whatever endpoints appeared and adjusting whatever changed shape.
Other Analytics 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 CRediTas or osmapiR.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all CRediTas alternatives → · See all osmapiR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CRediTas and osmapiR 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. CRediTas and osmapiR 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 Analytics products to evaluate alongside.
Top CRediTas alternatives in Analytics are ranked by recent ship velocity. Browse the "CRediTas alternatives" section above for the current picks, or visit /alternatives/creditas for the full list with editorial commentary on each.
Top osmapiR alternatives in Analytics are ranked by recent ship velocity. Browse the "osmapiR alternatives" section above for the current picks, or visit /alternatives/osmapir for the full list with editorial commentary on each.