The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
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[@]dogado.de.

CRAN Package Check Results for Maintainer ‘Hadley Wickham <hadley at posit.co>’

Last updated on 2026-08-07 05:49:53 CEST.

Package OK NOTE ERROR Other
bigrquery 13
dbplyr 13
diffviewer 13
doclisting 13
downlit 13
dplyr 6 5 2
dtplyr 13
ellmer 13
evaluate 13
forcats 13
generics 13
ggvis 11 2
haven 13
httr 13
httr2 13
lobstr 10 3
log4r 9
mockery 13
modelr 13
multidplyr 13
nasaweather 13
odbc 11 2 1
pkgdown 13
pool 13
productplots 13
profvis 13
purrr 12 1
rappdirs 12 1
rdtools 13
reshape2 13
roxygen2 13
rvest 13
S7 3 9 1 1
stringr 12 1
testthat 13
tidyr 13 1
waldo 13
yaml 11 1 1 1

Package bigrquery

Current CRAN status: OK: 13

Package dbplyr

Current CRAN status: OK: 13

Package diffviewer

Current CRAN status: OK: 13

Package doclisting

Current CRAN status: OK: 13

Package downlit

Current CRAN status: OK: 13

Package dplyr

Current CRAN status: OK: 6, NOTE: 5, ERROR: 2

Version: 1.2.1
Check: Rd contents
Result: NOTE Rd files without \usage: ‘scoped.Rd’ \arguments should not be documented without \usage. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 1.2.1
Check: whether package can be installed
Result: ERROR Installation failed. Flavors: r-devel-windows-x86_64, r-release-windows-x86_64

Version: 1.2.1
Check: compiled code
Result: NOTE File ‘dplyr/libs/dplyr.so’: Found non-API calls to R: ‘PRVALUE’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’, ‘SET_PRCODE’, ‘SET_PRENV’, ‘SET_PRVALUE’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 1.2.1
Check: compiled code
Result: NOTE File 'dplyr/libs/x64/dplyr.dll': Found non-API calls to R: 'PRVALUE', 'Rf_allocSExp', 'Rf_findVarInFrame3', 'SET_PRCODE', 'SET_PRENV', 'SET_PRVALUE' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-oldrel-windows-x86_64

Package dtplyr

Current CRAN status: OK: 13

Package ellmer

Current CRAN status: OK: 13

Package evaluate

Current CRAN status: OK: 13

Package forcats

Current CRAN status: OK: 13

Package generics

Current CRAN status: OK: 13

Package ggvis

Current CRAN status: OK: 11, NOTE: 2

Version: 0.4.10
Check: Rd contents
Result: NOTE Rd files without \usage: ‘group_by.Rd’ ‘pipe.Rd’ ‘scales.Rd’ \arguments should not be documented without \usage. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Package haven

Current CRAN status: OK: 13

Package httr

Current CRAN status: OK: 13

Package httr2

Current CRAN status: OK: 13

Package lobstr

Current CRAN status: OK: 10, NOTE: 3

Version: 1.2.1
Check: compiled code
Result: NOTE File ‘lobstr/libs/lobstr.so’: Found non-API calls to R: ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_PRCODE’, ‘SET_PRENV’, ‘SET_PRVALUE’, ‘SET_TRUELENGTH’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 1.2.1
Check: compiled code
Result: NOTE File 'lobstr/libs/x64/lobstr.dll': Found non-API calls to R: 'PRENV', 'PRVALUE', 'R_PromiseExpr', 'Rf_allocSExp', 'Rf_findVarInFrame3', 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_PRCODE', 'SET_PRENV', 'SET_PRVALUE', 'SET_TRUELENGTH' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-oldrel-windows-x86_64

Package log4r

Current CRAN status: OK: 9

Package mockery

Current CRAN status: OK: 13

Package modelr

Current CRAN status: OK: 13

Package multidplyr

Current CRAN status: OK: 13

Package nasaweather

Current CRAN status: OK: 13

Package odbc

Current CRAN status: OK: 11, NOTE: 2, Other: 1

Additional issues

M1mac M1mac

Version: 1.7.0
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘vctrs’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Package pkgdown

Current CRAN status: OK: 13

Package pool

Current CRAN status: OK: 13

Package productplots

Current CRAN status: OK: 13

Package profvis

Current CRAN status: OK: 13

Package purrr

Current CRAN status: OK: 12, ERROR: 1

Version: 1.2.2
Check: re-building of vignette outputs
Result: ERROR Error(s) in re-building vignettes: --- re-building ‘base.Rmd’ using rmarkdown Error: processing vignette 'base.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘base.Rmd’ --- re-building ‘other-langs.Rmd’ using rmarkdown Error: processing vignette 'other-langs.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘other-langs.Rmd’ --- re-building ‘purrr.Rmd’ using rmarkdown Error: processing vignette 'purrr.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘purrr.Rmd’ SUMMARY: processing the following files failed: ‘base.Rmd’ ‘other-langs.Rmd’ ‘purrr.Rmd’ Error: Vignette re-building failed. Execution halted Flavor: r-release-macos-arm64

Package rappdirs

Current CRAN status: OK: 12, ERROR: 1

Version: 0.3.4
Check: tests
Result: ERROR Running ‘testthat.R’ [0s/1s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(rappdirs) > > # ensure CRAN settings don't affect tests > Sys.unsetenv("R_USER_DATA_DIR") > Sys.unsetenv("R_USER_CONFIG_DIR") > Sys.unsetenv("R_USER_CACHE_DIR") > > test_check("rappdirs") [ FAIL 0 | WARN 0 | SKIP 3 | PASS 45 ] ══ Skipped tests (3) ═══════════════════════════════════════════════════════════ Error in base::nchar(wide_chars$test, type = "width") : cannot open file '/Volumes/Builds/packages/sonoma-arm64/Rlib/4.6/cli/R/sysdata.rdb': No such file or directory Calls: test_check ... unicode_pre -> setup_unicode_width_fix -> <Anonymous> Execution halted Flavor: r-release-macos-arm64

Package rdtools

Current CRAN status: OK: 13

Package reshape2

Current CRAN status: OK: 13

Package roxygen2

Current CRAN status: OK: 13

Package rvest

Current CRAN status: OK: 13

Package S7

Current CRAN status: OK: 3, NOTE: 9, ERROR: 1, Other: 1

Additional issues

rchk

Version: 0.2.2
Check: compiled code
Result: NOTE File ‘S7/libs/S7.so’: Found non-API call to R: ‘Rf_findVarInFrame’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64

Version: 0.2.2
Check: compiled code
Result: NOTE File 'S7/libs/x64/S7.dll': Found non-API call to R: 'Rf_findVarInFrame' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavors: r-devel-windows-x86_64, r-release-windows-x86_64

Version: 0.2.2
Check: re-building of vignette outputs
Result: ERROR Error(s) in re-building vignettes: Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted Error in loadVignetteBuilder(pkgdir) : vignette builder 'knitr' not found Calls: <Anonymous> -> loadVignetteBuilder Execution halted SUMMARY: processing the following files failed: ‘S7.Rmd’ ‘classes-objects.Rmd’ ‘compatibility.Rmd’ ‘generics-methods.Rmd’ ‘motivation.Rmd’ ‘packages.Rmd’ ‘performance.Rmd’ Error: Vignette re-building failed. Execution halted Flavor: r-release-macos-arm64

Version: 0.2.2
Check: package vignettes
Result: NOTE Package has ‘vignettes’ subdirectory but apparently no vignettes. Perhaps the ‘VignetteBuilder’ information is missing from the DESCRIPTION file? Flavor: r-release-macos-x86_64

Package stringr

Current CRAN status: OK: 12, ERROR: 1

Version: 1.6.0
Check: re-building of vignette outputs
Result: ERROR Error(s) in re-building vignettes: --- re-building ‘from-base.Rmd’ using rmarkdown Error: processing vignette 'from-base.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘from-base.Rmd’ --- re-building ‘locale-sensitive.Rmd’ using rmarkdown Error: processing vignette 'locale-sensitive.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘locale-sensitive.Rmd’ --- re-building ‘regular-expressions.Rmd’ using rmarkdown Error: processing vignette 'regular-expressions.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘regular-expressions.Rmd’ --- re-building ‘stringr.Rmd’ using rmarkdown Error: processing vignette 'stringr.Rmd' failed with diagnostics: there is no package called ‘sass’ --- failed re-building ‘stringr.Rmd’ SUMMARY: processing the following files failed: ‘from-base.Rmd’ ‘locale-sensitive.Rmd’ ‘regular-expressions.Rmd’ ‘stringr.Rmd’ Error: Vignette re-building failed. Execution halted Flavor: r-release-macos-arm64

Package testthat

Current CRAN status: OK: 13

Package tidyr

Current CRAN status: OK: 13, Other: 1

Additional issues

rchk

Package waldo

Current CRAN status: OK: 13

Package yaml

Current CRAN status: OK: 11, NOTE: 1, ERROR: 1, Other: 1

Additional issues

rchk

Version: 2.3.12
Check: for unstated dependencies in vignettes
Result: NOTE Error: error in inferior call: .onLoad failed in loadNamespace() for 'knitr', details: call: loadNamespace(x) error: there is no package called ‘evaluate’ Execution halted Flavor: r-release-macos-arm64

Version: 2.3.12
Check: tests
Result: ERROR Running ‘testthat.R’ [0s/0s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(yaml) > > test_check("yaml") Error in loadNamespace(x) : there is no package called 'cli' Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart Execution halted Flavor: r-release-macos-x86_64

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.
Health stats visible at Monitor.