whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
A side-by-side editorial comparison of portfoliobacktest and rapr — release velocity, themes, recent moves, and the top alternatives to consider.
Four dormant years end with a test fix, not a feature
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
rapr pulls Rangeland Analysis Platform data into R — vegetation cover and production rasters derived from Landsat and Sentinel-2, plus the tabular summary APIs. The 1.1.3 release replaces the single-purpose table function with a general get_rap_table() covering the cover, coverMeteorology, production and production16day endpoints. The package reached CRAN in 2025 and is maintained by brownag, who also maintains the GeoPackage interface gpkg.
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.
Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.
rapr pulls Rangeland Analysis Platform data into R — vegetation cover and production rasters derived from Landsat and Sentinel-2, plus the tabular summary APIs. The 1.1.3 release replaces the single-purpose table function with a general get_rap_table() covering the cover, coverMeteorology, production and production16day endpoints. The package reached CRAN in 2025 and is maintained by brownag, who also maintains the GeoPackage interface gpkg.
The shape is familiar for a young API client: add access to one endpoint, then generalise it once a second endpoint proves the pattern. get_rap_production16day_table() arrived in 1.1.0 and was deprecated three releases later in favour of a product argument. Between those, the work was error handling — empty geometries, server-side HTTP failures, warning timing — the unglamorous half of wrapping a remote service. The 1.0.0 release had already set the ambition by exposing both the 30m Landsat and 10m Sentinel-2 sources behind one argument.
Expect the remaining RAP endpoints to be folded into get_rap_table() as they are needed, and the deprecated 16-day function to be removed once the general interface has been out long enough.
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 portfoliobacktest or rapr.
whirl turned script logging into a standardized provenance artifact regulators can read.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
A small B-Cubed utility for turning R Markdown into publishable docs
An R interface to GeoPackage that keeps sanding down its own API
R's logging package handed to new maintainers and rebuilt from the inside out
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
See all portfoliobacktest alternatives → · See all rapr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. portfoliobacktest and rapr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. portfoliobacktest and rapr 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.
Top portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.
Top rapr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rapr alternatives" section above for the current picks, or visit /alternatives/rapr for the full list with editorial commentary on each.