ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of checkhelper and Rmonize — 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.
Collapsed a pile of parameters into one object and renamed every report column
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
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.
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
The arc runs from correctness toward interface. Version 1.0.1 was bug fixes found on real data, 1.1.0 added a debug parameter so harmonization could be tested with incomplete inputs, and 2.0.0 is a deliberate simplification that breaks existing code in exchange for a smaller surface. Renaming outputs from expressions like 'Categories::missing' and 'Nb. non-valid values' to 'Non-valid categories' and 'Number of non-valid values' points at reports being read by people who are not the person who wrote the harmonization rules.
Expect the superseded parameters and the renamed demo object to be removed outright rather than left superseded, and continued work on the visual reports, which carry the largest volume of referenced issues across all three versions.
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 Rmonize.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore declared its API stable with every survey design type covered.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all checkhelper alternatives → · See all Rmonize 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 Rmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rmonize alternatives" section above for the current picks, or visit /alternatives/rmonize for the full list with editorial commentary on each.