The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

checkhelper: Deal with Check Outputs

Deal with packages 'check' outputs and reduce the risk of rejection by 'CRAN' by following policies.

Version: 1.0.0
Depends: R (≥ 4.0)
Imports: cli, covr, desc, devtools, dplyr, glue, knitr, lifecycle, magrittr, pkgbuild, pkgload, purrr, rcmdcheck, roxygen2, stringi, stringr, tibble, tools, utils, whisker (≥ 0.4), withr
Suggests: attachment, callr, rmarkdown, testthat, usethis
Published: 2026-05-13
DOI: 10.32614/CRAN.package.checkhelper
Author: Vincent Guyader ORCID iD [aut, cre], Sebastien Rochette ORCID iD [aut] (previous maintainer), Arthur Bréant ORCID iD [aut], Murielle Delmotte ORCID iD [aut], ThinkR [cph]
Maintainer: Vincent Guyader <vincent at thinkr.fr>
BugReports: https://github.com/ThinkR-open/checkhelper/issues
License: MIT + file LICENSE
URL: https://thinkr-open.github.io/checkhelper/, https://github.com/ThinkR-open/checkhelper
NeedsCompilation: no
Language: en-US
Materials: README, NEWS
CRAN checks: checkhelper results

Documentation:

Reference manual: checkhelper.html , checkhelper.pdf
Vignettes: Auditing an R package you have just received (source, R code)
Pre-submission gates (source, R code)

Downloads:

Package source: checkhelper_1.0.0.tar.gz
Windows binaries: r-devel: checkhelper_1.0.0.zip, r-release: checkhelper_1.0.0.zip, r-oldrel: checkhelper_1.0.0.zip
macOS binaries: r-release (arm64): checkhelper_1.0.0.tgz, r-oldrel (arm64): checkhelper_1.0.0.tgz, r-release (x86_64): checkhelper_1.0.0.tgz, r-oldrel (x86_64): checkhelper_1.0.0.tgz
Old sources: checkhelper archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=checkhelper to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.