secuTrialR
A Swiss clinical-trial data reader that surfaces once every couple of years to clear check notes.
Comparison · Analytics
broom.helpers vs edibble
A side-by-side editorial comparison of broom.helpers and edibble — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
broom.helpers vs edibble: at a glance
What is broom.helpers?
The tidying engine under gtsummary keeps widening its model coverage while retiring its own selector layer.
broom.helpers standardises the output of regression models so downstream packages can render them, and its release notes are essentially a running list of newly supported model classes. Recent versions added quantreg, svyVGAM, VGAM, glmtoolbox and mmrm support alongside a steady stream of fixes for fixest and survey models. In parallel it has spent three releases dismantling its own selector helpers in favour of the cards package.
What is edibble?
A grammar for experimental design that learned to compose designs and track its own provenance.
edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.
broom.helpers vs edibble: editorial side-by-side
broom.helpers
0.0ANALYTICS
The tidying engine under gtsummary keeps widening its model coverage while retiring its own selector layer.
◆ Current state
broom.helpers standardises the output of regression models so downstream packages can render them, and its release notes are essentially a running list of newly supported model classes. Recent versions added quantreg, svyVGAM, VGAM, glmtoolbox and mmrm support alongside a steady stream of fixes for fixest and survey models. In parallel it has spent three releases dismantling its own selector helpers in favour of the cards package.
◆ Where it's heading
Two arcs run in parallel. The first is accretive: each release absorbs another modelling package, which is the natural job of a translation layer and shows no sign of slowing. The second is subtractive and now complete — the dot-prefixed selector functions were deprecated in 1.17.0, hard deprecated in 1.20.0, and removed in 1.22.0, alongside the deprecation of tidy_marginal_means() and tidy_margins() as their upstream packages moved or left CRAN. The package is consolidating on parameters and marginaleffects as its computational backends while shedding machinery that now belongs to gtsummary's ecosystem.
◆ Prediction
The next release will most likely add support for another model class and continue trimming tidiers whose upstream packages have been superseded, following the pattern of the last six.
edibble
0.0ANALYTICS
A grammar for experimental design that learned to compose designs and track its own provenance.
◆ Current state
edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.
◆ Where it's heading
Development has moved from vocabulary to composition. Early releases established the core grammar; 1.0.0 replaced the internal R6 machinery with a Provenance object that tracks both internal and external commands, which is what lets a design carry its own construction history. On that foundation 1.1.0 added the ability to add two designs together, express conditional treatment structures, and split simulation specification from execution. The 2025 release turns toward a different entry point — wiring up level edges and unit attributes when an edibble object is built from data that already exists, rather than from a design declared up front.
◆ Prediction
Expect continued work on designs derived from existing data, since that is where the last release concentrated and it is the path least covered by the declarative grammar.
Alternatives to broom.helpers and edibble
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 broom.helpers or edibble.
flightsbr
Brazil's flight-data package keeps working around what ANAC publishes and when.
rolap
A star-schema modelling package grew a query language, a deployment path, and then a map layer.
kwb.db
A water-research lab's ODBC helper, still fighting Windows database drivers a decade in.
r2dii.match
PACTA's loan-book matcher opened up to sector taxonomies other than its own.
r2dii.plot
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
See all broom.helpers alternatives → · See all edibble alternatives →
Recent activity from broom.helpers and edibble
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agobroom.helpersQuantile regression support lands as legacy selectors are removed
- 1y agobroom.helpersExperimental tidier for survey-weighted VGAM models
- 1y agoedibbleBetter handling of designs built from existing data
- 1y agobroom.helpersNew grouping controls for tidied model results
- 1y agobroom.helpersMarginal means tidier hard deprecated
- 1y agobroom.helpersInstrumental variable support for fixest models
- 1y agobroom.helpersbroom.helpers 1.17.0 ⚡
- 2y agoedibbleedibble 1.1.0 ⚡
- 2y agoedibbleInternals rebuilt on a command-tracking Provenance object
- 3y agoedibbleS3 consistency and citation modernised
- 3y agoedibbleRd files fixed for HTML5 compatibility
- 4y agoedibbleInitial release
Frequently asked questions
What is the difference between broom.helpers and edibble?
Both compete on the same themes — r-package — within Analytics. broom.helpers and edibble 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.
Is broom.helpers better than edibble?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. broom.helpers and edibble 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.
What are the best alternatives to broom.helpers?
Top broom.helpers alternatives in Analytics are ranked by recent ship velocity. Browse the "broom.helpers alternatives" section above for the current picks, or visit /alternatives/broom-helpers for the full list with editorial commentary on each.
What are the best alternatives to edibble?
Top edibble alternatives in Analytics are ranked by recent ship velocity. Browse the "edibble alternatives" section above for the current picks, or visit /alternatives/edibble for the full list with editorial commentary on each.