wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A side-by-side editorial comparison of carrier and EDAForge — release velocity, themes, recent moves, and the top alternatives to consider.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
EDAForge's release feed shows a package changing identity between its first two tags. The v0.1.0 notes describe DataAudit, a data-quality auditing package built around audit_data(), reusable audit_rules() and audit_score(), with install instructions still pointing at vinodhpmd/DataAudit, while the repository now serves EDAForge. Only three tags exist, one of which is a bare compare link with no notes, and the most recent is a CRAN-policy cleanup rather than feature work.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.
The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.
EDAForge's release feed shows a package changing identity between its first two tags. The v0.1.0 notes describe DataAudit, a data-quality auditing package built around audit_data(), reusable audit_rules() and audit_score(), with install instructions still pointing at vinodhpmd/DataAudit, while the repository now serves EDAForge. Only three tags exist, one of which is a bare compare link with no notes, and the most recent is a CRAN-policy cleanup rather than feature work.
The substance so far is all in the DataAudit-named 0.1.0: more than a dozen check families spanning missing values, duplicates, ranges, patterns, dependencies and grouped sequences, wrapped in a structured report object with print and summary methods. The 0.1.1 that follows removes a default output path, moves examples to tempdir() and adds an introductory vignette, which is the standard shape of a package being made acceptable to CRAN. The public identity is currently ahead of the release notes, so a reader arriving at the feed cannot tell from it what EDAForge does.
Expect the next tag to align the notes with the EDAForge name and add exploratory-analysis functions alongside the auditing core; the compliance pass in 0.1.1 points at a CRAN submission as the near-term goal.
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 carrier or EDAForge.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
See all carrier alternatives → · See all EDAForge alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. EDAForge is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EDAForge is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top carrier alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "carrier alternatives" section above for the current picks, or visit /alternatives/carrier for the full list with editorial commentary on each.
Top EDAForge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "EDAForge alternatives" section above for the current picks, or visit /alternatives/edaforge for the full list with editorial commentary on each.