rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of checkhelper and gofedf — release velocity, themes, recent moves, and the top alternatives to consider.
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
A two-test goodness-of-fit package opens itself up to any weight function
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
The design commitment is static analysis — AST walks via getParseData(), line-by-line Rd reading, no eval() and no namespace loading — so the tool can report on a package it never runs. That commitment is what made the roxygen2 8.x break survivable: the audit pipeline itself was verified correct under 8.1.0 and only the test scaffolding had to go, now guarded by a dedicated regression test. fix_globals(write = TRUE) is being sanded down in parallel, no longer flattening per-function grouping comments or writing a degenerate empty globalVariables() shell.
The immediate move is the 1.0.1 submission itself, clearing the archival notice. Beyond that, each additional CRAN incoming-check rule remains a candidate for another audit_* function; the open question these notes still leave is whether the family ever gets a single combined entry point.
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
The package is generalising rather than accumulating. Each release removed a hard-coded decision: first how eigenvalues are computed, offering both the analytical route and a matrix approximation; then which weight function defines the statistic at all. The maintainer's own framing in 1.1.0 is a contrast against what earlier versions would not let you do, which is the shape of a package aiming to become a framework.
An arbitrary weight function is the extensibility point that matters for EDF tests; what it lacks is calibration guidance, since Type I error behaviour was the argued benefit of the analytical eigenvalue route. Documented recommendations or diagnostics for user-chosen weights are the natural follow-up, though the entries do not announce one.
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 checkhelper or gofedf.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all checkhelper alternatives → · See all gofedf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. checkhelper is currently shipping more aggressively (velocity 2.5 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. checkhelper is currently shipping more aggressively (velocity 2.5 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 checkhelper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "checkhelper alternatives" section above for the current picks, or visit /alternatives/checkhelper for the full list with editorial commentary on each.
Top gofedf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gofedf alternatives" section above for the current picks, or visit /alternatives/gofedf for the full list with editorial commentary on each.