susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
Comparison · Analytics
nflreadr vs treasury
A side-by-side editorial comparison of nflreadr and treasury — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packagecaching
nflreadr vs treasury: at a glance
What is nflreadr?
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
nflreadr is the data access layer of the nflverse, wrapping cached downloads of play-by-play, roster, contract, charting and stats releases. Its growth phase peaked with 1.3.0, which added participation data, contracts, weekly rosters, officials and the players endpoint in a single release. Since then the work has been consolidation: 1.5.0 moved to v2 players data and reorganized player stats behind nflfastR's calculate_stats() with a summary_level argument, and 1.5.1 hard-deprecated qs file support after that package was removed from CRAN in January 2026.
What is treasury?
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
nflreadr vs treasury: editorial side-by-side
nflreadr
0.0ANALYTICS
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
◆ Current state
nflreadr is the data access layer of the nflverse, wrapping cached downloads of play-by-play, roster, contract, charting and stats releases. Its growth phase peaked with 1.3.0, which added participation data, contracts, weekly rosters, officials and the players endpoint in a single release. Since then the work has been consolidation: 1.5.0 moved to v2 players data and reorganized player stats behind nflfastR's calculate_stats() with a summary_level argument, and 1.5.1 hard-deprecated qs file support after that package was removed from CRAN in January 2026.
◆ Where it's heading
Two external clocks drive this package and neither is under its control. Feature releases land before the NFL season opens — 1.5.0 says so explicitly — and breaking changes are timed to that window. The other clock is CRAN's: losing the qs dependency forced a serialization format out of the package entirely, leaving parquet, rds and csv. The upstream coupling to nflfastR is tightening too, with player and team stats now sourced from its calculation functions rather than computed here.
◆ Prediction
The pattern of a pre-season consolidation release is well established, so the next substantive version is likely timed to the following season's opener rather than to any internal roadmap.
treasury
0.0ANALYTICS
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
◆ Current state
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
◆ Where it's heading
Endpoint coverage looks essentially complete, so the work has moved to the metadata a downstream analyst needs to join and audit results — cusip and maturity_date on bill quotes, the feed's updated_at stamp, and the extrapolation factor behind 2002-2006 long-term rate estimates. Error handling is tightening in the same direction: an out-of-range month now fails with a message instead of quietly returning nothing. That is the profile of a wrapper moving from coverage to correctness, where the remaining bugs are the subtle ones that only surface in other people's locales.
◆ Prediction
Expect further column-level enrichment and input validation on the endpoints already covered rather than new data sources, since the structural pieces — data.table returns and caching — are already in place.
Alternatives to nflreadr and treasury
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 nflreadr or treasury.
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
robma
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
See all nflreadr alternatives → · See all treasury alternatives →
Recent activity from nflreadr and treasury
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agotreasuryBill rates gain CUSIP and maturity date; locale bug fixed
- 3mo agonflreadrnflreadr 1.5.1
- 4mo agotreasuryOptional response caching, one day by default
- 11mo agonflreadrnflreadr 1.5.0
- 11mo agotreasuryRate functions renamed to singular for consistency
- 1y agotreasuryEvery function now returns a data.table ⚡
- 2y agonflreadrnflreadr 1.4.1
- 2y agotreasuryHQM, coupon-issue and breakeven inflation curves added
- 2y agonflreadrnflreadr 1.4.0
- 3y agonflreadrnflreadr 1.3.2
- 3y agonflreadrnflreadr 1.3.1
Frequently asked questions
What is the difference between nflreadr and treasury?
Both compete on the same themes — r-package, caching — within Analytics. nflreadr and treasury 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 nflreadr better than treasury?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nflreadr and treasury 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 nflreadr?
Top nflreadr alternatives in Analytics are ranked by recent ship velocity. Browse the "nflreadr alternatives" section above for the current picks, or visit /alternatives/nflreadr for the full list with editorial commentary on each.
What are the best alternatives to treasury?
Top treasury alternatives in Analytics are ranked by recent ship velocity. Browse the "treasury alternatives" section above for the current picks, or visit /alternatives/treasury for the full list with editorial commentary on each.