WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of openair and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.
Air quality analysis rebuilt on ggplot2, twenty years of lattice plotting dropped in one release.
openair is the reference toolkit for UK and European air quality data analysis, covering import from national monitoring networks, time averaging, polar and trajectory plots, and trend estimation. Version 3.0.0 rewrote every plotting function in ggplot2 and removed lattice, latticeExtra, hexbin, and mapproj from the dependency tree; 3.1.0 followed six weeks later to settle how parameters reach those functions, remapping base and lattice graphics arguments to ggplot2 equivalents with a warning rather than failing outright.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
openair is the reference toolkit for UK and European air quality data analysis, covering import from national monitoring networks, time averaging, polar and trajectory plots, and trend estimation. Version 3.0.0 rewrote every plotting function in ggplot2 and removed lattice, latticeExtra, hexbin, and mapproj from the dependency tree; 3.1.0 followed six weeks later to settle how parameters reach those functions, remapping base and lattice graphics arguments to ggplot2 equivalents with a warning rather than failing outright.
Two threads run through these releases. The first is the rendering migration and its long tail — deprecated arguments rehomed into breakOpts(), graphical parameters standardized on ggplot2 conventions, trajectory projections collapsed from three arguments into a single crs. The second is data access decaying underneath the package: importEurope() now errors for recent years because the database behind it was retired, while importUKAQ() gained automatic source detection and steadily more careful ratification handling. Correctness fixes keep landing in the analytical core too, including a corrected TheilSen intercept and more consistent bin boundaries in multi-period time averaging.
The migration is not finished — 3.1.0 is still remapping legacy graphics arguments with warnings — so expect a release that turns those deprecations into removals, and continued churn around European data import while the replacement service settles.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
Rhino is converging on scaffolding as its main surface — the framework's value is increasingly in what it generates for you rather than what it does at runtime, and 1.12 extends that generation to instructions meant for AI coding agents rather than humans. The maintainer change and the CI/coverage work in the same release read as consolidation after a long gap: 1.11 shipped in April 2025, 1.12 not until June 2026.
More `use_*` scaffolding functions are the obvious next increment, since two arrived in a single release. Whether the AGENTS.md instructions grow into deeper agent tooling is not something these entries settle.
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 openair or Rhino.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all openair alternatives → · See all Rhino alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. openair and Rhino 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. openair and Rhino 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 openair alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "openair alternatives" section above for the current picks, or visit /alternatives/openair for the full list with editorial commentary on each.
Top Rhino alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rhino alternatives" section above for the current picks, or visit /alternatives/rhino-r for the full list with editorial commentary on each.