Advice on R Package Building R package goodpractice version 1.1.0 Give advice about good practices when building R packages. Advice includes functions and syntax to avoid, package structure, code complexity, code formatting, etc. Software Depends: R (>= 4.0.0) Imports: cli, covr, curl, cyclocomp (>= 1.1.0), desc, jsonlite, lintr (>= 3.0.0), praise, rcmdcheck, roxygen2, rstudioapi, spelling, tools, treesitter, treesitter.r, urlchecker, utils, whoami, withr Suggests: future, future.apply, kableExtra, knitr, rmarkdown, testthat (>= 3.0.0) Mark Padgham <mark@ropensci.org> Comprehensive R Archive Network (CRAN) Mark Padgham [aut, cre] (ORCID: <https://orcid.org/0000-0003-2172-5265>), Ascent Digital Services UK Limited [cph] (GitHub: MangoTheCat), Karina Marks [aut] (GitHub: KarinaMarks), Daniel de Bortoli [aut] (GitHub: ddbortoli), Gabor Csardi [aut], Hannah Frick [aut], Owen Jones [aut] (GitHub: owenjonesuob), Hannah Alexander [aut], Ana Simmons [ctb] (GitHub: anasimmons), Fabian Scheipl [ctb] (GitHub: fabian-s), Athanasia Mo Mowinckel [aut] (GitHub: drmowinckels, ORCID: <https://orcid.org/0000-0002-5756-0223>) MIT + file LICENSE (https://CRAN.R-project.org/package=goodpractice/LICENSE) 2026-06-05 application/tgz https://CRAN.R-project.org/package=goodpractice doi:10.32614/CRAN.package.goodpractice