Check for hardcoded random seeds in package code — cl_check_hardcoded

Flags set.seed() calls in R/ that pass a literal, unchangeable number (e.g. set.seed(42), set.seed(seed = 42L), set.seed(-5)) as any argument. Setting a seed a user can't override or opt out of, inside a function, is a common CRAN rejection reason. Calls in tests/, \examples, vignettes/, and demos are out of scope – and not scanned at all, since checks only look at R/ – because setting a seed there is expected and recommended for reproducibility.

Usage

cl_check_hardcoded_seed(path = ".")

Arguments

path: Path to the package root. Defaults to the current directory.

Value

A tibble following the cranlint check-result contract; see AGENTS.md.

Examples

pkg_dir <- cl_example_pkg(
  r_files = list(simulate.R = c(
    "simulate <- function() {",
    "  set.seed(42)",
    "  rnorm(1)",
    "}"
  ))
)
cl_check_hardcoded_seed(pkg_dir)
#> # A tibble: 1 × 6
#>   check          file          line severity   message          policy_reference
#>   <chr>          <chr>        <int> <ord>      <chr>            <chr>           
#> 1 hardcoded_seed R/simulate.R     2 should_fix set.seed() call… https://contrib…
unlink(pkg_dir, recursive = TRUE)