fastrg
A fast random-graph sampler that spent 0.3.1 fixing what its parameters actually mean.
A side-by-side editorial comparison of cfbfastr and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
College football's open data client hit v2 — and now reports how many API calls you have left.
cfbfastR retrieves college football data — play-by-play, box scores, betting lines, ratings and recruiting — from the CollegeFootballData API, ESPN endpoints and the sportsdataverse data repository. Version 2.0.0 in September 2025 was the first release in over three years and rebuilt the package against CFBD's v2 API. Every load_cfb_*() function changed its underlying source to comply with CFBD's terms, the play-by-play dataset gained team and game identifiers users previously had to join in themselves, and a batch of new endpoints arrived covering opponent-adjusted metrics, FPI ratings and live scoreboard and play data.
Rho's release machinery is now more rigorous than the product it ships.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
cfbfastR retrieves college football data — play-by-play, box scores, betting lines, ratings and recruiting — from the CollegeFootballData API, ESPN endpoints and the sportsdataverse data repository. Version 2.0.0 in September 2025 was the first release in over three years and rebuilt the package against CFBD's v2 API. Every load_cfb_*() function changed its underlying source to comply with CFBD's terms, the play-by-play dataset gained team and game identifiers users previously had to join in themselves, and a batch of new endpoints arrived covering opponent-adjusted metrics, FPI ratings and live scoreboard and play data.
The package's direction is now set by the data provider rather than by its own plans, and that provider has moved to metered access — the free tier is capped at 1,000 calls a month, with limits tied to membership level. cfbd_api_key_info() reporting a user's tier and usage is the clearest sign of that shift: quota is now something an analysis has to manage. The long gap before 2.0.0 and its arrival largely through a first-time contributor also indicate a package sustained by community effort rather than steady maintenance.
The live scoreboard and play endpoints are the natural place for the next work, since they are the ones that benefit from in-season iteration. Given the release notes warn users to check their pipelines, follow-up fixes for the changed loading functions are likely before anything new lands.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, CONDITIONAL_GO records, checksums bound to exact commits, limitations named out loud rather than buried. dev.41 exists solely to rehearse the native updater across Windows and macOS, which is the last piece of distribution infrastructure between a dev train and something installable by people who won't build from source. Feature work and shipping work are advancing on separate tracks.
The updater acceptance target points at a 0.4.0 line that can update itself, so the next entry that matters is either dev.40's real publication or the first build not labelled evaluation-only. Whether Windows signing moves off the SignPath trial certificate is the open question these entries leave unanswered.
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 cfbfastr or Rho.
A fast random-graph sampler that spent 0.3.1 fixing what its parameters actually mean.
A young Mathematics Genealogy client spending its first four releases satisfying CRAN.
The natverse package that taught neuron data to remember which brain space it lives in.
The NBLAST neuron-similarity engine is stable code on life support, shipping once every few years.
A random-walk generator that outgrew one dimension and renamed its core column to prove it.
Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.
See all cfbfastr alternatives → · See all Rho alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top cfbfastr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfbfastr alternatives" section above for the current picks, or visit /alternatives/cfbfastr for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.