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 EDAForge and lintr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
lintr makes the native pipe the default rule and clears out a decade of deprecations
lintr is the static analysis standard for R packages, and its 3.3.0 release does two things at once: it changes pipe_consistency_linter() to require the native pipe, following the Tidyverse Style Guide, and it completes a long deprecation program — six linters fully deprecated, several arguments defunct, and a batch of functions removed outright. The 3.1.x line before it was accuracy work and a maintainer handoff to Michael Chirico.
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.
lintr is the static analysis standard for R packages, and its 3.3.0 release does two things at once: it changes pipe_consistency_linter() to require the native pipe, following the Tidyverse Style Guide, and it completes a long deprecation program — six linters fully deprecated, several arguments defunct, and a batch of functions removed outright. The 3.1.x line before it was accuracy work and a maintainer handoff to Michael Chirico.
The package has been consolidating: overlapping linters renamed and merged, configuration validated up front, and an experimental R-script config offered as a possible replacement for the DCF format. Alongside that, a sustained campaign against false positives and false negatives in individual linters, which is where most contributor effort goes.
Expect the six warning-deprecated linters to be removed in the next release as announced, and continued movement on the R-script configuration format if feedback supports it.
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 EDAForge or lintr.
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 EDAForge alternatives → · See all lintr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 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.
Top lintr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lintr alternatives" section above for the current picks, or visit /alternatives/lintr for the full list with editorial commentary on each.