A tables-listings-graphs package that reached CRAN and then went quiet.
wikitaxa alternatives
The best wikitaxa alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to wikitaxa? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, wikitaxa shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About wikitaxa
A six-year silence broken by a dependency that CRAN deleted underneath it
wikitaxa is the rOpenSci client for pulling taxonomic records out of Wikipedia, Wikidata, Wikispecies and Wikicommons, and it has been feature-complete since 2017. The v0.5.0 release in February 2026 arrived after nearly six years of silence, and it exists because CRAN archived WikidataR — the library wikitaxa used to reach Wikidata. The fix routes those calls through WikipediR directly, which removes a third-party single point of failure from the package's dependency graph.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to wikitaxa
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
wikitaxa vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| wikitaxa (baseline) | 0.0 | 0 | taxonomywikidataropensci | — |
| tidytlg | 0.0 | 0 | clinical-trialstablesr-package | — |
| Tplyr | 0.0 | 0 | clinical-trialstablestraceability | 1.0.0 introduces the traceability metadata framework |
| rlistings | 0.0 | 0 | clinical-trialslistingspagination | — |
| hoardr | 0.0 | 0 | cachingr-packageropensci | — |
| gigs | 0.0 | 0 | growth-standardsneonatal-healthr-package | Conversion API rewritten around data frames and classify_growth() |
| riem | 0.0 | 0 | weather-dataapi-clientr-package | — |
| datasetjson | 0.0 | 0 | clinical-datacdiscjson | Dataset-JSON 1.1.0 support with a redesigned object model |
| ijtiff | 0.0 | 0 | imagingtiffr-package | — |
| tern | 0.0 | 0 | clinical-trialstablesr-package | Two dozen more analysis functions drop make_afun() |
| posteriordb | 0.0 | 0 | bayesianbenchmarkingreference-data | — |
| tinkr | 0.0 | 0 | markdownxmlr-package | First release: the extensible yarn R6 class |
| excluder | 0.0 | 0 | survey-datadata-cleaningr-package | — |
The 12 best wikitaxa alternatives, in depth
1. tidytlg · velocity 0.0
A tables-listings-graphs package that reached CRAN and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, tidytlg focuses on clinical trials, tables and r package.
tidytlg and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. Tplyr · velocity 0.0
Tplyr made clinical summary tables explain where every number came from.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 introduces the traceability metadata framework”.
Where wikitaxa leans on taxonomy, wikidata and ropensci, Tplyr focuses on clinical trials, tables and traceability.
Tplyr and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. rlistings · velocity 0.0
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, rlistings focuses on clinical trials, listings and pagination.
rlistings and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full rlistings trajectory → · Compare wikitaxa vs rlistings →
4. hoardr · velocity 0.0
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, hoardr focuses on caching, r package and ropensci.
hoardr and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. gigs · velocity 0.0
Gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Conversion API rewritten around data frames and classify_growth()”.
Where wikitaxa leans on taxonomy, wikidata and ropensci, gigs focuses on growth standards, neonatal health and r package.
gigs and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. riem · velocity 0.0
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, riem focuses on weather data, api client and r package.
riem and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. datasetjson · velocity 0.0
Datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Dataset-JSON 1.1.0 support with a redesigned object model”.
Where wikitaxa leans on taxonomy, wikidata and ropensci, datasetjson focuses on clinical data, cdisc and json.
datasetjson and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datasetjson trajectory → · Compare wikitaxa vs datasetjson →
8. ijtiff · velocity 0.0
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, ijtiff focuses on imaging, tiff and r package.
ijtiff and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. tern · velocity 0.0
Tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Two dozen more analysis functions drop make_afun()”.
Where wikitaxa leans on taxonomy, wikidata and ropensci, tern focuses on clinical trials, tables and r package.
tern and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. posteriordb · velocity 0.0
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, posteriordb focuses on bayesian, benchmarking and reference data.
posteriordb and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full posteriordb trajectory → · Compare wikitaxa vs posteriordb →
11. tinkr · velocity 0.0
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “First release: the extensible yarn R6 class”.
Where wikitaxa leans on taxonomy, wikidata and ropensci, tinkr focuses on markdown, xml and r package.
tinkr and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. excluder · velocity 0.0
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where wikitaxa leans on taxonomy, wikidata and ropensci, excluder focuses on survey data, data cleaning and r package.
excluder and wikitaxa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to wikitaxa?
The top wikitaxa alternatives we currently track in analytics tools are tidytlg, Tplyr, rlistings, hoardr, gigs, ranked by recent ship velocity.
How is this list of wikitaxa alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare wikitaxa directly with one of these alternatives?
Yes — every card has a "Compare with wikitaxa" link to a side-by-side /compare page.