ANALYTICS
mirai removed its dispatcher process and added memory backpressure to the queue.
Alternatives · analytics tools
epiparameter alternatives
The best epiparameter alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to epiparameter? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, epiparameter 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 epiparameter
epiparameter split its parameter library out of the package — and relicensed what remained.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to epiparameter
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
ggsurvfit is in correctness-and-compatibility mode, not feature mode.
ANALYTICS
nanonext keeps shrinking its build requirements while adding messaging primitives.
ANALYTICS
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
ANALYTICS
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
ANALYTICS
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
ANALYTICS
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
ANALYTICS
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
ANALYTICS
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
ANALYTICS
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
ANALYTICS
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
ANALYTICS
The EDI data client is being dragged through its repository's identity-system migration.
epiparameter 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 |
|---|---|---|---|---|
| epiparameter (baseline) | 0.0 | 0 | epiverse-traceepidemiological-parameterspackage-architecture | Parameter library moves to epiparameterDB; package relicensed to MIT alone |
| mirai | 2.5 | 0 | parallel-computingasyncbackpressure | Dispatcher becomes a thread, and the queue gains a memory budget |
| ggsurvfit | 2.5 | 0 | survival-analysisggplot2competing-risks | — |
| nanonext | 2.5 | 0 | async-messagingnnghttp-server | Zero-copy message forwarding, and cmake dropped from the build |
| DataSpaceR | 2.5 | 0 | hiv-researchimmunology-dataapi-client | Query API rebuilt and DAASH antibody sequence access added |
| metatools | 0.0 | 0 | pharmaversesdtmadam | — |
| marquee | 0.0 | 0 | r-libtypographymarkdown | — |
| logrx | 0.0 | 0 | pharmaverseloggingclinical-trials | — |
| lobstr | 0.0 | 0 | r-libintrospectionmemory | truelength reporting dropped for public C API compliance |
| GSODR | 0.0 | 0 | ropensciweather-datar-package | — |
| giscoR | 0.0 | 0 | eurostatgeospatialropensci | 1.0 caches the dataset index so new vintages need no release |
| FedData | 0.0 | 0 | ropenscigeospatialr-package | sp and raster dropped; everything returns terra or sf |
| EDIutils | 0.0 | 0 | ropenscir-packageapi-client | EDI-IDs replace Distinguished Names as authentication moves to IAM |
The 12 best epiparameter alternatives, in depth
1. mirai · velocity 2.5
Mirai removed its dispatcher process and added memory backpressure to the queue.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Dispatcher becomes a thread, and the queue gains a memory budget”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, mirai focuses on parallel computing, async and backpressure.
mirai and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. ggsurvfit · velocity 2.5
Ggsurvfit is in correctness-and-compatibility mode, not feature mode.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, ggsurvfit focuses on survival analysis, ggplot2 and competing risks.
ggsurvfit and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ggsurvfit trajectory → · Compare epiparameter vs ggsurvfit →
3. nanonext · velocity 2.5
Nanonext keeps shrinking its build requirements while adding messaging primitives.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Zero-copy message forwarding, and cmake dropped from the build”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, nanonext focuses on async messaging, nng and http server.
nanonext and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full nanonext trajectory → · Compare epiparameter vs nanonext →
4. DataSpaceR · velocity 2.5
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Query API rebuilt and DAASH antibody sequence access added”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, DataSpaceR focuses on hiv research, immunology data and api client.
DataSpaceR and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full DataSpaceR trajectory → · Compare epiparameter vs DataSpaceR →
5. metatools · velocity 0.0
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, metatools focuses on pharmaverse, sdtm and adam.
metatools and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full metatools trajectory → · Compare epiparameter vs metatools →
6. marquee · velocity 0.0
Marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, marquee focuses on r lib, typography and markdown.
marquee and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full marquee trajectory → · Compare epiparameter vs marquee →
7. logrx · velocity 0.0
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, logrx focuses on pharmaverse, logging and clinical trials.
logrx and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. lobstr · velocity 0.0
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “truelength reporting dropped for public C API compliance”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, lobstr focuses on r lib, introspection and memory.
lobstr and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. GSODR · velocity 0.0
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, GSODR focuses on ropensci, weather data and r package.
GSODR and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. giscoR · velocity 0.0
GiscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0 caches the dataset index so new vintages need no release”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, giscoR focuses on eurostat, geospatial and ropensci.
giscoR and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. FedData · velocity 0.0
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “sp and raster dropped; everything returns terra or sf”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, FedData focuses on ropensci, geospatial and r package.
FedData and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full FedData trajectory → · Compare epiparameter vs FedData →
12. EDIutils · velocity 0.0
The EDI data client is being dragged through its repository's identity-system migration.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “EDI-IDs replace Distinguished Names as authentication moves to IAM”.
Where epiparameter leans on epiverse trace, epidemiological parameters and package architecture, EDIutils focuses on ropensci, r package and api client.
EDIutils and epiparameter have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full EDIutils trajectory → · Compare epiparameter vs EDIutils →
Frequently asked questions
What are the best alternatives to epiparameter?
The top epiparameter alternatives we currently track in analytics tools are mirai, ggsurvfit, nanonext, DataSpaceR, metatools, ranked by recent ship velocity.
How is this list of epiparameter alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare epiparameter directly with one of these alternatives?
Yes — every card has a "Compare with epiparameter" link to a side-by-side /compare page.