France's national flood statistics, ported out of Fortran and into R.
offsetreg alternatives
The best offsetreg alternatives in developer tools, ranked by Sparkpulse's velocity_score.
Updated Aug 18, 2026
Looking for the best alternatives to offsetreg? Sparkpulse tracks and ranks 12 alternatives in developer tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, offsetreg 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 offsetreg
The parsnip extension for exposure models grew from one algorithm to three
offsetreg supplies parsnip model specifications for regressions with offsets, the form actuarial and epidemiological work needs when modelling rates over exposure. It launched with a single specification, poisson_reg_offset(), backed by glm and glmnet engines. Version 1.1.0 added two more model types - boost_tree_offset() for boosted trees via xgboost and decision_tree_exposure() for weighted decision trees via rpart - and 1.2.0 has been consolidation: argument passthrough to the underlying glm and glmnet calls, an xgboost 3.0 minimum with API accommodation, and cli-formatted messages.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to offsetreg
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Bayesian luminescence dating that finally replaced its folder-structure input format.
An epidemic-economic model teaching its interventions to react to the outbreak itself.
A parallel-chain helper for bkmr that has settled into pure upkeep.
A cancer driver prioritization package that ships rarely and mostly to stay installable
A meteorology ggplot2 extension where the netCDF reader became the main event
offsetreg 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 |
|---|---|---|---|---|
| offsetreg (baseline) | 0.0 | 0 | tidymodelsparsnipr-package | Boosted trees and weighted decision trees join the offset model family |
| HydroPortailStats | 0.0 | 0 | hydrologyflood-frequencybayesian-statistics | Historical flood records enter the estimator via an HBay port |
| bsvarSIGNs | 0.0 | 0 | bayesian-statisticseconometricsstructural-var | Launch: sign, zero and narrative restrictions for bsvars |
| estimatr | 0.0 | 0 | causal-inferenceexperimentsrobust-standard-errors | — |
| ggdist | 0.0 | 0 | data-visualizationuncertaintybayesian-statistics | Blurred dotplots draw Monte Carlo error; weights reach every estimator |
| ipaddress | 0.0 | 0 | networkingip-addressesrcpp | 1.0.0 breaks the interface to make it vector-native |
| ltertools | 0.0 | 0 | data-harmonizationecologylter | — |
| finnts | 0.0 | 0 | forecastingtime-seriestidymodels | — |
| BayLum | 0.0 | 0 | bayesian-statisticsluminescence-datinggeochronology | One data-file function and a YAML config replace the folder layout |
| daedalus | 0.0 | 0 | epidemic-modellinghealth-economicsnpi-policy | Interventions now lift in response to live R_t |
| bkmrhat | 0.0 | 0 | bayesian-statisticsmcmcparallel-computing | — |
| driveR | 0.0 | 0 | cancer-genomicsbioinformaticsr-package | — |
| metR | 0.0 | 0 | meteorologyggplot2r-package | — |
The 12 best offsetreg alternatives, in depth
1. HydroPortailStats · velocity 0.0
France's national flood statistics, ported out of Fortran and into R.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Historical flood records enter the estimator via an HBay port”.
Where offsetreg leans on tidymodels, parsnip and r package, HydroPortailStats focuses on hydrology, flood frequency and bayesian statistics.
HydroPortailStats and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full HydroPortailStats trajectory → · Compare offsetreg vs HydroPortailStats →
2. bsvarSIGNs · velocity 0.0
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Launch: sign, zero and narrative restrictions for bsvars”.
Where offsetreg leans on tidymodels, parsnip and r package, bsvarSIGNs focuses on bayesian statistics, econometrics and structural var.
bsvarSIGNs and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full bsvarSIGNs trajectory → · Compare offsetreg vs bsvarSIGNs →
3. estimatr · velocity 0.0
Fast design-based estimators for experiments, coasting on CRAN patches.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, estimatr focuses on causal inference, experiments and robust standard errors.
estimatr and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full estimatr trajectory → · Compare offsetreg vs estimatr →
4. ggdist · velocity 0.0
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Blurred dotplots draw Monte Carlo error; weights reach every estimator”.
Where offsetreg leans on tidymodels, parsnip and r package, ggdist focuses on data visualization, uncertainty and bayesian statistics.
ggdist and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. ipaddress · velocity 0.0
IP address vectors for R that hit 1.0 and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 breaks the interface to make it vector-native”.
Where offsetreg leans on tidymodels, parsnip and r package, ipaddress focuses on networking, ip addresses and rcpp.
ipaddress and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ipaddress trajectory → · Compare offsetreg vs ipaddress →
6. ltertools · velocity 0.0
A column-key toolkit for stitching decades of ecological field data into one table.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, ltertools focuses on data harmonization, ecology and lter.
ltertools and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ltertools trajectory → · Compare offsetreg vs ltertools →
7. finnts · velocity 0.0
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, finnts focuses on forecasting, time series and tidymodels.
finnts and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. BayLum · velocity 0.0
Bayesian luminescence dating that finally replaced its folder-structure input format.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “One data-file function and a YAML config replace the folder layout”.
Where offsetreg leans on tidymodels, parsnip and r package, BayLum focuses on bayesian statistics, luminescence dating and geochronology.
BayLum and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. daedalus · velocity 0.0
An epidemic-economic model teaching its interventions to react to the outbreak itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Interventions now lift in response to live R_t”.
Where offsetreg leans on tidymodels, parsnip and r package, daedalus focuses on epidemic modelling, health economics and npi policy.
daedalus and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full daedalus trajectory → · Compare offsetreg vs daedalus →
10. bkmrhat · velocity 0.0
A parallel-chain helper for bkmr that has settled into pure upkeep.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, bkmrhat focuses on bayesian statistics, mcmc and parallel computing.
bkmrhat and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. driveR · velocity 0.0
A cancer driver prioritization package that ships rarely and mostly to stay installable.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, driveR focuses on cancer genomics, bioinformatics and r package.
driveR and offsetreg have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. metR · velocity 0.0
A meteorology ggplot2 extension where the netCDF reader became the main event.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where offsetreg leans on tidymodels, parsnip and r package, metR focuses on meteorology, ggplot2 and r package.
metR and offsetreg 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 offsetreg?
The top offsetreg alternatives we currently track in developer tools are HydroPortailStats, bsvarSIGNs, estimatr, ggdist, ipaddress, ranked by recent ship velocity.
How is this list of offsetreg alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare offsetreg directly with one of these alternatives?
Yes — every card has a "Compare with offsetreg" link to a side-by-side /compare page.