← Back to home
Comparison · Analytics

invasimapr vs rmediation

A side-by-side editorial comparison of invasimapr and rmediation — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r package

invasimapr vs rmediation: at a glance

Featureinvasimaprrmediation
SectorAnalyticsAnalytics
Velocity score0.03.8
Sparks · 30d01
Top themesinvasion ecology, species traits, biodiversity, research softwaremediation analysis, numerical integration, correctness, s7 classes
Last editorial update51m ago55m ago
WebsiteVisit →Visit →

What is invasimapr?

invasimapr halved its install size and became citable; the science stayed put.

invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.

Read the full invasimapr trajectory →

What is rmediation?

RMediation shipped a three-normal CDF, then found it was silently wrong.

RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.

Read the full rmediation trajectory →

invasimapr vs rmediation: editorial side-by-side

I
invasimapr
ANALYTICS
0.0

invasimapr halved its install size and became citable; the science stayed put.

◆ Current state

invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.

◆ Where it's heading

The pressure is toward being installable and auditable rather than more capable — install slimmed from roughly 100 MB to 56 MB, R CMD check warnings and notes resolved, sp moved to Suggests, a Darwin Core-aligned data dictionary added, and a Zenodo concept DOI with CITATION.cff, codemeta.json and .zenodo.json. The package moves in lockstep with its B-Cubed sibling dissmapr, tagged within minutes of each other at both 0.1.0 and 0.2.1, which points at project-level standards deadlines rather than independent release decisions. Trait dispersion metrics and scenario exploration remain on the roadmap.

◆ Prediction

Standards compliance is now complete and the roadmap names functional trait dispersion metrics and scenario exploration tools, so the next release is the first that can plausibly be about invasion ecology rather than packaging.

R
rmediation
ANALYTICS
3.8

RMediation shipped a three-normal CDF, then found it was silently wrong.

◆ Current state

RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.

◆ Where it's heading

The package is moving from a hand-rolled numerical layer to one that checks itself: the new default integrator escalates its node count until successive rules agree, warns when it hits the cap instead of returning a number, and exposes a diagnostics argument for the convergence estimate. The correctness fix went to dev ahead of the CRAN window rather than being held for it, which suggests wrong-answer bugs are treated as release-blocking regardless of cadence. Serial mediation is where the new surface area is concentrated.

◆ Prediction

1.7.0 exists specifically to land before CRAN's 2026-08-21 update window, so the next move is a CRAN submission promoting it to main; whether hcubature survives past that as a cross-check option is the open question.

Alternatives to invasimapr and rmediation

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 invasimapr or rmediation.

See all invasimapr alternatives → · See all rmediation alternatives →

Recent activity from invasimapr and rmediation

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 8h agormediationv1.7.0 — pprodnormal3() correctness fix
  2. 1mo agoinvasimaprVersion bump; notes identical to 0.2.0
  3. 1mo agormediationp_prod3() renamed into the pprodnormal family
  4. 1mo agormediationProductNormal3: exact CDF for a product of three normals
  5. 1mo agoinvasimaprB-Cubed standards alignment; install slimmed to 56 MB
  6. 1mo agoinvasimaprinvasimapr v0.1.0: First citable release
  7. 1mo agormediationmedfit reaches CRAN; Remotes pointer dropped

Frequently asked questions

What is the difference between invasimapr and rmediation?

Both compete on the same themes — r package — within Analytics. rmediation is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is invasimapr better than rmediation?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rmediation is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to invasimapr?

Top invasimapr alternatives in Analytics are ranked by recent ship velocity. Browse the "invasimapr alternatives" section above for the current picks, or visit /alternatives/invasimapr for the full list with editorial commentary on each.

What are the best alternatives to rmediation?

Top rmediation alternatives in Analytics are ranked by recent ship velocity. Browse the "rmediation alternatives" section above for the current picks, or visit /alternatives/rmediation for the full list with editorial commentary on each.