qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of constants and netrankr — release velocity, themes, recent moves, and the top alternatives to consider.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
A centrality package that absorbed an abandoned neighbour rather than let its functions vanish.
netrankr computes centrality rankings on networks using partial orders rather than committing to a single index, and lets users build their own indices from relational components. The latest release folds in functions from the archived NetSwan package and clears deprecated igraph calls. Earlier work removed the midpoint calculation from rank_intervals, a change the notes themselves flag as possibly breaking.
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
The direction set at 1.0.0 was to stop being a curated convenience wrapper and become a mechanical mirror of NIST. Hand-crafted symbol names were replaced with NIST's own ASCII symbols, categories adopted NIST's, and uncertainty switched from relative to absolute — all framed by the maintainer as necessary to make future CODATA updates routine. On top of that the package gained a correlation matrix and optional integration with the quantities package, moving it from a lookup table toward something that can propagate uncertainty.
Having rebuilt the symbol table specifically so CODATA revisions become mechanical, the next substantive release most likely tracks a new CODATA dataset rather than adding API. The experimental correlated-value support, disabled by default at 1.0.0, is the one part these entries flag as unfinished.
netrankr computes centrality rankings on networks using partial orders rather than committing to a single index, and lets users build their own indices from relational components. The latest release folds in functions from the archived NetSwan package and clears deprecated igraph calls. Earlier work removed the midpoint calculation from rank_intervals, a change the notes themselves flag as possibly breaking.
Development is sparse and driven by ecosystem pressure — igraph deprecations, CRAN archival of related packages, JOSS submission requirements. The analytic core has been stable since the partial-order framework was established; what changes is the surrounding surface and its compatibility with a moving graph stack. Absorbing NetSwan is the first real expansion in years.
Expect further igraph compatibility passes; whether the NetSwan absorption is a one-off rescue or the start of consolidating orphaned network packages is not something these entries settle.
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 constants or netrankr.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all constants alternatives → · See all netrankr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. constants and netrankr 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. constants and netrankr 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.
Top constants alternatives in Analytics are ranked by recent ship velocity. Browse the "constants alternatives" section above for the current picks, or visit /alternatives/constants-r for the full list with editorial commentary on each.
Top netrankr alternatives in Analytics are ranked by recent ship velocity. Browse the "netrankr alternatives" section above for the current picks, or visit /alternatives/netrankr-r for the full list with editorial commentary on each.