← Back to home
Comparison · Analytics

medrobust vs rmediation

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

Shared themes:r package

medrobust vs rmediation: at a glance

Featuremedrobustrmediation
SectorAnalyticsAnalytics
Velocity score0.03.8
Sparks · 30d01
Top themescausal mediation, partial identification, misclassification, sensitivity analysismediation analysis, numerical integration, correctness, s7 classes
Last editorial update47m ago54m ago
WebsiteVisit →Visit →

What is medrobust?

medrobust made its partial-identification bounds usable by giving them confidence intervals.

medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.

Read the full medrobust 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 →

medrobust vs rmediation: editorial side-by-side

M
medrobust
ANALYTICS
0.0

medrobust made its partial-identification bounds usable by giving them confidence intervals.

◆ Current state

medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.

◆ Where it's heading

The pattern is deliberate and symmetric: 0.3.0 shipped the mediator-side example on NCHS natality data, 0.4.0 its exposure-side mirror on NHANES, each demonstrating what the bounds do when reporting accuracy is allowed to depend on the outcome. Alongside that runs a consistent concern with failing usefully rather than loudly — bound_ne() returns NA bounds with a machine-readable reason and a typed condition instead of aborting, so a simulation replicate is recorded rather than lost, and non-finite endpoint standard errors produce a documented NA rather than a silent one. That is a package expecting to be run thousands of times inside someone else's loop.

◆ Prediction

Both identification paths now have a dataset, a vignette and interval coverage, so the next release is most likely the deferred CRAN submission rather than new methodology.

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

See all medrobust alternatives → · See all rmediation alternatives →

Recent activity from medrobust and rmediation

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

  1. 8h agormediationv1.7.0 — pprodnormal3() correctness fix
  2. 1mo agormediationp_prod3() renamed into the pprodnormal family
  3. 1mo agormediationProductNormal3: exact CDF for a product of three normals
  4. 1mo agormediationmedfit reaches CRAN; Remotes pointer dropped
  5. 2mo agomedrobustNHANES exposure-side misclassification example dataset
  6. 2mo agomedrobustNatality example dataset; bounds degrade instead of aborting
  7. 2mo agomedrobustBounds corrected against oracles; Imbens-Manski intervals added

Frequently asked questions

What is the difference between medrobust 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 medrobust 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 medrobust?

Top medrobust alternatives in Analytics are ranked by recent ship velocity. Browse the "medrobust alternatives" section above for the current picks, or visit /alternatives/medrobust 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.