STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
cfbfastr vs collinear
A side-by-side editorial comparison of cfbfastr and collinear — release velocity, themes, recent moves, and the top alternatives to consider.
cfbfastr vs collinear: at a glance
What is cfbfastr?
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.
What is collinear?
collinear has broken its API twice to stop making the user pick thresholds.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
cfbfastr vs collinear: editorial side-by-side
cfbfastr
0.0ANALYTICS
College football's open data client hit v2 — and now reports how many API calls you have left.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
collinear
0.0ANALYTICS
collinear has broken its API twice to stop making the user pick thresholds.
◆ Current state
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
◆ Where it's heading
The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.
◆ Prediction
3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.
Alternatives to cfbfastr and collinear
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 collinear.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
See all cfbfastr alternatives → · See all collinear alternatives →
Recent activity from cfbfastr and collinear
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agocollinearNamespace, NA and sf fixes; example data moves to spatialData
- 8mo agocollinearAdaptive thresholds, multi-response support and a new output class ⚡
- 11mo agocfbfastrRebuilt on CFBD API v2 with metered access and live endpoints ⚡
- 1y agocollinearCategorical responses, f_auto() defaults and future-based parallelism ⚡
- 4y agocfbfastrESPN endpoints and repo-backed loaders added
- 4y agocfbfastrAll outputs standardised as tibbles with a custom class
- 4y agocfbfastrCRAN release with option-restoring cleanup
- 4y agocfbfastrMinor fixes to betting and FPI rating functions
- 4y agocfbfastrESPN scoreboard and play-by-play access, with argument cleanup
Frequently asked questions
What is the difference between cfbfastr and collinear?
They serve adjacent needs but don't currently overlap on shipped themes. cfbfastr and collinear 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 cfbfastr better than collinear?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cfbfastr and collinear 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 cfbfastr?
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.
What are the best alternatives to collinear?
Top collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear for the full list with editorial commentary on each.