Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
checkhelper vs goodpractice
A side-by-side editorial comparison of checkhelper and goodpractice — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:static-analysis
checkhelper vs goodpractice: at a glance
What is checkhelper?
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
Two years of near-silence ended with a 1.0.0 that adds 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. check_n_covr() runs R CMD check and coverage in a single test pass instead of two.
What is goodpractice?
The R package-quality checker returns from CRAN limbo with checks you can select by category.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
checkhelper vs goodpractice: editorial side-by-side
checkhelper
0.0INFRA · APIS
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
◆ Current state
Two years of near-silence ended with a 1.0.0 that adds 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. check_n_covr() runs R CMD check and coverage in a single test pass instead of two.
◆ Where it's heading
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. The existing fix_globals() was reworked the same way: it merges with an existing R/globals.R instead of overwriting it, and separates data.table and rlang pronouns from real undeclared globals so they get an @importFrom line rather than a globalVariables() entry.
◆ Prediction
Each additional CRAN incoming-check rule is a candidate for another audit_* function; the open question these notes leave is whether the family ever gets a single combined entry point.
goodpractice
0.0INFRA · APIS
The R package-quality checker returns from CRAN limbo with checks you can select by category.
◆ Current state
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
◆ Where it's heading
The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.
◆ Prediction
With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.
Alternatives to checkhelper and goodpractice
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 goodpractice.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all checkhelper alternatives → · See all goodpractice alternatives →
Recent activity from checkhelper and goodpractice
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agogoodpracticeChecks organized into 16 selectable groups with presets ⚡
- 3mo agocheckhelperA static audit_* family for CRAN pre-submission checks ⚡
- 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
- 2y agocheckhelperTest fixes for roxygen2 changes
- 3y agocheckhelpercheckhelper 0.1.0 - First CRAN Release
- 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
- 5y agogoodpracticePackage logo added
Frequently asked questions
What is the difference between checkhelper and goodpractice?
Both compete on the same themes — static-analysis — within Infra & APIs. checkhelper and goodpractice 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 checkhelper better than goodpractice?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. checkhelper and goodpractice 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to checkhelper?
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.
What are the best alternatives to goodpractice?
Top goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.