← Back to home
Comparison · Analytics

fastml vs rATTAINS

A side-by-side editorial comparison of fastml and rATTAINS — release velocity, themes, recent moves, and the top alternatives to consider.

fastml vs rATTAINS: at a glance

FeaturefastmlrATTAINS
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesautoml, tidymodels, survival analysis, cross-validationwater-quality, epa-data, r-package, api-wrapper
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is fastml?

fastml added survival modelling and leakage-proof resampling, moving past classification and regression.

A tidymodels-based AutoML wrapper that trains, tunes and compares many engines from one call. The 0.6.x line added engine-specific tuning parameters, class-imbalance handling, early stopping and DALEX-based explainability. The 0.7.5 release is far larger: a full survival analysis task with its own engines, MICE imputation and integrated Brier scoring, plus unbiased nested cross-validation, grouped, blocked and rolling resampling helpers, fold-wise imputation, recipe leakage checks, and a sandbox for user-supplied preprocessing.

Read the full fastml trajectory →

What is rATTAINS?

The R client for EPA water quality data spent two releases undoing its own promises about data shape.

rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.

Read the full rATTAINS trajectory →

fastml vs rATTAINS: editorial side-by-side

F
fastml
ANALYTICS
0.0

fastml added survival modelling and leakage-proof resampling, moving past classification and regression.

◆ Current state

A tidymodels-based AutoML wrapper that trains, tunes and compares many engines from one call. The 0.6.x line added engine-specific tuning parameters, class-imbalance handling, early stopping and DALEX-based explainability. The 0.7.5 release is far larger: a full survival analysis task with its own engines, MICE imputation and integrated Brier scoring, plus unbiased nested cross-validation, grouped, blocked and rolling resampling helpers, fold-wise imputation, recipe leakage checks, and a sandbox for user-supplied preprocessing.

◆ Where it's heading

The package is moving from convenience wrapper to something that has to be defensible statistically. Nested cross-validation, fold-wise rather than up-front imputation, and explicit leakage checks are all corrections to the shortcuts that make AutoML easy and its scores optimistic. Survival adds a third task type alongside classification and regression, and it arrived with its own metrics rather than being bolted onto the existing ones. Note the entry body is cut off at 8,000 characters, so the release is larger than what is shown.

◆ Prediction

Expect the remaining survival engines to fill in and the sandboxing of custom preprocessing to tighten, since both were still being iterated on within this same release's commit list.

R
rATTAINS
ANALYTICS
0.0

The R client for EPA water quality data spent two releases undoing its own promises about data shape.

◆ Current state

rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.

◆ Where it's heading

The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.

◆ Prediction

Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.

Alternatives to fastml and rATTAINS

Other Analytics 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 fastml or rATTAINS.

See all fastml alternatives → · See all rATTAINS alternatives →

Recent activity from fastml and rATTAINS

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agorATTAINSATTAINS now requires an API key, and the package follows
  2. 8mo agofastmlVersion 0.7.5
  3. 8mo agorATTAINSThe tibblify dependency goes, and with it the stable data shapes
  4. 1y agofastmlEngine-specific tuning, imbalance handling and explainability
  5. 1y agofastmlSingle-workflow evaluation fix
  6. 1y agorATTAINSTest suite updated for vcr v2
  7. 1y agofastmlVersion 0.5.0
  8. 3y agorATTAINS1.0.0 commits to stable return structures via tibblify
  9. 3y agorATTAINSCaching removed after hoardr was archived
  10. 4y agorATTAINSRequests retry on timeout, with offline detection

Frequently asked questions

What is the difference between fastml and rATTAINS?

They serve adjacent needs but don't currently overlap on shipped themes. fastml and rATTAINS 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 fastml better than rATTAINS?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fastml and rATTAINS 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 Analytics products to evaluate alongside.

What are the best alternatives to fastml?

Top fastml alternatives in Analytics are ranked by recent ship velocity. Browse the "fastml alternatives" section above for the current picks, or visit /alternatives/fastml for the full list with editorial commentary on each.

What are the best alternatives to rATTAINS?

Top rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.