HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
driveR vs finnts
A side-by-side editorial comparison of driveR and finnts — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
driveR vs finnts: at a glance
What is driveR?
A cancer driver prioritization package that ships rarely and mostly to stay installable
driveR prioritizes cancer driver genes from somatic variant and copy number data, combining coding impact scores, noncoding impact, copy number alteration scores and hotspot annotations into a multi-task learning classification model. Version 0.5.0 added gene-level SCNA data frames as an accepted input to create_features_df(), with an example table shipped alongside, widening the entry point beyond the segment-level format. The same release moved org.Hs.eg.db and both hg19 and hg38 TxDb annotation packages from Imports to Suggests under new CRAN policy, with dependent functions now raising an error when they are absent rather than silently degrading.
What is finnts?
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.
driveR vs finnts: editorial side-by-side
driveR
0.0INFRA · APIS
A cancer driver prioritization package that ships rarely and mostly to stay installable
◆ Current state
driveR prioritizes cancer driver genes from somatic variant and copy number data, combining coding impact scores, noncoding impact, copy number alteration scores and hotspot annotations into a multi-task learning classification model. Version 0.5.0 added gene-level SCNA data frames as an accepted input to create_features_df(), with an example table shipped alongside, widening the entry point beyond the segment-level format. The same release moved org.Hs.eg.db and both hg19 and hg38 TxDb annotation packages from Imports to Suggests under new CRAN policy, with dependent functions now raising an error when they are absent rather than silently degrading.
◆ Where it's heading
Releases are infrequent and split cleanly between capability and correction. GRCh38 support arrived in 0.4.0 and cancer-type-specific thresholds were refreshed in 0.3.0, while the 0.2.x pair fixed scoring errors serious enough to require retraining: a column name mismatch meant the SCNA score was not being computed at all, and MCR table coordinates needed converting from hg18 to hg19. Both times the bundled classification model and thresholds were rebuilt as a consequence. Since 0.4.0 the changes have been input handling and packaging rather than method.
◆ Prediction
The move of the annotation databases to Suggests suggests a leaner install is the current priority; the entries give no indication of planned model or scoring changes.
finnts
0.0INFRA · APIS
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
◆ Current state
finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.
◆ Where it's heading
Cadence is roughly annual and the commit history is almost entirely one maintainer, with occasional outside contributions. The direction across the last four releases is consolidation of the forecasting internals — multi-horizon models, feature selection, reconciliation fixes — rather than new surface for users. The changelogs themselves are unedited PR dumps, which makes the arc harder to read than the work probably warrants.
◆ Prediction
Hierarchical reconciliation has produced a bug fix in three of the last four releases, so the next one likely touches it again; nothing in the entries points to a specific new capability.
Alternatives to driveR and finnts
Other Infra & APIs 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 driveR or finnts.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
See all driveR alternatives → · See all finnts alternatives →
Recent activity from driveR and finnts
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agodriveRGene-level copy number input accepted, annotation packages made optional
- 11mo agofinntsGlobal model updates and a weekly reconciliation fix
- 1y agofinntsMulti-horizon models, hierarchy drivers, Synapse 3.4 migration
- 2y agofinntsARIMAX support and feature selection added
- 3y agodriveRCRAN documentation error fixed
- 3y agofinntsdplyr 1.1.0 compatibility and a reconciliation fix
- 4y agodriveRGRCh38 genome build supported
- 4y agodriveRCancer-type-specific thresholds updated
- 5y agodriveRMCR coordinates converted to hg19 and the model retrained
- 5y agodriveRCopy number score was never being computed, model rebuilt
Frequently asked questions
What is the difference between driveR and finnts?
Both compete on the same themes — r-package — within Infra & APIs. driveR and finnts 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.
Is driveR better than finnts?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. driveR and finnts 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to driveR?
Top driveR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "driveR alternatives" section above for the current picks, or visit /alternatives/driver for the full list with editorial commentary on each.
What are the best alternatives to finnts?
Top finnts alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "finnts alternatives" section above for the current picks, or visit /alternatives/finnts for the full list with editorial commentary on each.