ANALYTICS
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
Alternatives · analytics tools
refsplitr alternatives
The best refsplitr alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to refsplitr? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, refsplitr shipped 0 meaningful updates in the last 30 days and carries a velocity score of 5.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 refsplitr
Author disambiguation for bibliometrics, still grinding on the hard part: which names are the same person.
refsplitr parses Web of Science reference records into tidy data and tries to resolve which author strings belong to the same researcher, then georeferences their institutional addresses for network and map visualizations. The active work is squarely on the disambiguation core: 1.2.3 continues refining the author grouping algorithm and 1.2.1 adjusted ORCID ID matching. Earlier, 1.2.0 replaced the address parsing algorithm and changed the default georeferencing option for author institutions.
Velocity 5.0 · Last update 2h ago
Top 12 alternatives to refsplitr
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
ANALYTICS
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
ANALYTICS
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
ANALYTICS
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
ANALYTICS
Sparse vectors stopped being a storage trick and became something you can do arithmetic on
ANALYTICS
A Darwin Core validator that went quiet for two years, then surfaced only to raise its R floor
ANALYTICS
Four releases in three years, each one teaching the serializer about a model type it couldn't carry
ANALYTICS
The R port of LIME has shipped one commit in three years, and it was an xgboost compatibility patch
ANALYTICS
One maintainer, one or two new collective-motion metrics per release, for two years straight
ANALYTICS
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
refsplitr 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 |
|---|---|---|---|---|
| refsplitr (baseline) | 5.0 | 0 | bibliometricsauthor-disambiguationgeoreferencing | — |
| tidymodels | 0.0 | 0 | tidymodelsmeta-packagedependency-management | — |
| datapack | 0.0 | 0 | research-datadataoneprovenance | Assembled data packages become editable in place |
| USAboundaries | 0.0 | 0 | geospatialcensus-datasf | Data split into a companion package; all boundaries become sf |
| slider | 0.0 | 0 | sliding-windowstidyversec-api-compliance | — |
| simtrial | 0.0 | 0 | clinical-trialsgroup-sequentialsurvival-analysis | RMST and milestone tests, plus a user-definable cut and test framework |
| nodbi | 0.0 | 0 | document-databasesjsonduckdb | Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres |
| sparsevctrs | 0.0 | 0 | sparse-datatidymodelsaltrep | Scalar and element-wise arithmetic for sparse vectors |
| dwctaxon | 0.0 | 0 | darwin-coretaxonomydata-validation | — |
| bundle | 0.0 | 0 | serializationtidymodelsmodel-deployment | — |
| lime | 0.0 | 0 | explainabilitymachine-learningmaintenance-mode | — |
| spatsoc | 0.0 | 0 | movement-ecologysocial-networksspatial-analysis | — |
| r2rtf | 0.0 | 0 | clinical-reportingrtfinternationalization | r2rtf 1.2.0 |
The 12 best refsplitr alternatives, in depth
1. tidymodels · velocity 0.0
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, tidymodels focuses on tidymodels, meta package and dependency management.
tidymodels and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full tidymodels trajectory → · Compare refsplitr vs tidymodels →
2. datapack · velocity 0.0
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Assembled data packages become editable in place”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, datapack focuses on research data, dataone and provenance.
datapack and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datapack trajectory → · Compare refsplitr vs datapack →
3. USAboundaries · velocity 0.0
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Data split into a companion package; all boundaries become sf”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, USAboundaries focuses on geospatial, census data and sf.
USAboundaries and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full USAboundaries trajectory → · Compare refsplitr vs USAboundaries →
4. slider · velocity 0.0
Feature-complete since 2021, and every release since has been paying CRAN's C API bill.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, slider focuses on sliding windows, tidyverse and c api compliance.
slider and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. simtrial · velocity 0.0
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “RMST and milestone tests, plus a user-definable cut and test framework”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, simtrial focuses on clinical trials, group sequential and survival analysis.
simtrial and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full simtrial trajectory → · Compare refsplitr vs simtrial →
6. nodbi · velocity 0.0
One document API over six databases, and every release is spent absorbing their JSON engines' churn.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, nodbi focuses on document databases, json and duckdb.
nodbi and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. sparsevctrs · velocity 0.0
Sparse vectors stopped being a storage trick and became something you can do arithmetic on.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Scalar and element-wise arithmetic for sparse vectors”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, sparsevctrs focuses on sparse data, tidymodels and altrep.
sparsevctrs and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full sparsevctrs trajectory → · Compare refsplitr vs sparsevctrs →
8. dwctaxon · velocity 0.0
A Darwin Core validator that went quiet for two years, then surfaced only to raise its R floor.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, dwctaxon focuses on darwin core, taxonomy and data validation.
dwctaxon and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full dwctaxon trajectory → · Compare refsplitr vs dwctaxon →
9. bundle · velocity 0.0
Four releases in three years, each one teaching the serializer about a model type it couldn't carry.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, bundle focuses on serialization, tidymodels and model deployment.
bundle and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. lime · velocity 0.0
The R port of LIME has shipped one commit in three years, and it was an xgboost compatibility patch.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, lime focuses on explainability, machine learning and maintenance mode.
lime and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. spatsoc · velocity 0.0
One maintainer, one or two new collective-motion metrics per release, for two years straight.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, spatsoc focuses on movement ecology, social networks and spatial analysis.
spatsoc and refsplitr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. r2rtf · velocity 0.0
The clinical-report table engine learned Chinese, then learned to leave RTF entirely.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “r2rtf 1.2.0”.
Where refsplitr leans on bibliometrics, author disambiguation and georeferencing, r2rtf focuses on clinical reporting, rtf and internationalization.
r2rtf and refsplitr 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 refsplitr?
The top refsplitr alternatives we currently track in analytics tools are tidymodels, datapack, USAboundaries, slider, simtrial, ranked by recent ship velocity.
How is this list of refsplitr alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare refsplitr directly with one of these alternatives?
Yes — every card has a "Compare with refsplitr" link to a side-by-side /compare page.