← Back to all sparks
C

checkhelper

INFRA · APIS
Velocity0.0

A package to help deal with devtools::check outputs

checkhelper grew from a check wrapper into a CRAN pre-submission auditor.

r-packagescran-compliancestatic-analysisdeveloper-toolscode-audit
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.

Recent moves

  1. 3mo ago

    A static audit_* family for CRAN pre-submission checks

    ⚡ SPARK

    The release that redefines the package's job: four static auditors for download calls, unquoted DESCRIPTION package names, \dontrun{} blocks and old-style CITATION calls, plus a combined check-and-coverage pass. It turns a set of check helpers into a pre-submission auditor.

    View source ↗
  2. 2y ago

    Test fixes for roxygen2 changes

    A maintenance release adjusting unit tests to roxygen2 changes and downgrading find_missing_values() from warnings to messages. The two-year gap that follows it is the context for how much 1.0.0 had to carry.

    View source ↗
  3. 3y ago

    checkhelper 0.1.0 - First CRAN Release

    The first CRAN release, built around check_clean_userspace() for detecting files left behind by tests, examples and vignettes. It establishes the userspace-hygiene check that 1.0.0 later hardens with a partial-run fallback.

    View source ↗