R Observatory: Metrics for renv version 1.3.1

Balamuta, James Joseph

doi:10.5281/zenodo.21843040

renv

1.3.1Package record

Project Environments

29packages dependsuggested by 38

4.3Mdownloads / year

–test coverage

13/13flavors OK

Overview

About

Maintained by Kevin UsheyCRAN page ↗GitHub ↗Website ↗Issues ↗Declared funder: Posit Software, PBC

A dependency management toolkit for R. Using 'renv', you can create and manage project-local R libraries, save the state of these libraries to a 'lockfile', and later restore your library as required. Together, these tools can help make your projects more isolated, portable, and reproducible.

Changes in 1.3.1

renv::hydrate() no longer reports packages that are already installed in the project library as "not available locally", nor re-installs them, when those packages are not found in the user or site libraries. (#2172)
renv::restore() and renv::install() now install repository archives of packages whose lockfile record includes a RemoteSubdir field (for example, packages originally built from a sub-directory of a GitHub repository and then published to a custom repository). Previously, renv failed to find the DESCRIPTION file within such archives and fell back to cloning the package's git repository instead. (#1703)
renv now writes the GithubSubdir field, alongside the other Github* compatibility fields, when installing a package from a sub-directory of a GitHub repository. (#2165)

Show all changes in 1.3.1Hide the rest of the changes in 1.3.1

renv::lockfile_validate() now reports a clear error when the jsonvalidate package is not installed. (#2184)
renv now warns when a retrieved package is not the one that was requested, for example because a download cache entry or a repository served a tarball for a different package. Previously, renv silently installed whatever package it had retrieved. (#2322)
Concurrent restores sharing a package cache no longer fail with errors like dependency 'rlang' is not available when they build the same package at the same time. Previously, the restore that finished last replaced the cache entry that the other restore's library already linked to, which briefly left that link dangling. renv now links a duplicate build to the existing cache entry instead, unless that package was requested to be rebuilt. (#2400)
renv::install() and renv::restore() now check the cache again just before building each package, and install from the cache if a matching entry has appeared since the up-front check. Concurrent restores sharing a cache thus converge on the first build of each package rather than all building every package that was missing from the cache when they started. (#2403)
New cache entries now appear atomically when the cache lives on a different filesystem than the project library (for example, a cache on a mounted volume in CI). Previously, renv moved packages into such a cache with mv, which copies the package into its final location piece by piece; a concurrent restore could observe the partially-copied entry and link its library to it. renv now copies the package into a temporary directory alongside its final location and renames it into place. (#2402)
renv::install() and renv::restore() no longer leave .renv-backup-* directories behind in the library when staged installs are disabled (via the renv.config.install.staged option) and more packages are ready to be built than can be built at once. Previously, renv could lose track of the backup of an existing installation while its package waited to be built, so that the backup was neither removed after a successful install, nor restored after a failed one. (#2407)
A vendored copy of renv (created with renv:::vendor()) now bundles the files it reads at runtime, so that system requirements checks, git credential helpers, and discovery of renv::use() calls work when renv itself is not installed. Previously these looked the files up in an installed copy of renv. (#2397)
renv::sysreqs() now reports the system requirements of the recursive dependencies of the requested packages as well. Previously, only the requested packages themselves were considered, so that (for example) renv::sysreqs("ragg") did not report the system libraries required by systemfonts and textshaping, even though ragg cannot be installed without them. Use recursive = FALSE to restore the old behavior. (#2352)
renv::sysreqs() now reports on the packages recorded in the project lockfile by default, together with the packages used in the project. This is the same set of packages that renv::restore() would install, so the system requirements for a project can be computed from renv.lock alone -- for example, when authoring a Dockerfile, before any R packages have been installed. (#2352)
renv::sysreqs() gains a source argument, controlling which version of each package is used when computing system requirements. System requirements (and package dependencies) are specific to a particular version of a package, so the versions used matter. For each package, the requested sources are tried in order: "lockfile" uses the version recorded in the project lockfile, "library" uses the installed version of the package, and "crandb" queries <https://crandb.r-pkg.org> for the latest version available from the active package repositories. The default consults all three, in that order. Previously, the latest CRAN release of each package was always used. The local argument is superseded by source = "library". See ?renv::sysreqs for more details. (#2352)
When pak integration is enabled (via the renv.config.pak.enabled option) and pak is itself recorded in the lockfile, renv::restore() now installs and uses the recorded version of pak, rather than the latest version available from the pak repositories. Other functions use the recorded version when pak needs to be installed, and otherwise leave the installed version of pak alone. Lockfile records for versions of pak older than the minimum version supported by renv are ignored, and renv falls back to the previous behavior if the recorded version cannot be installed. (#2169)
renv::install() now signals an error when a requested package fails to install, even if an older version of that package remains installed. Previously, a failed upgrade, or a transactional install that was rolled back, could return without an error. (#2384)
renv::restore() now installs the versions recorded in the lockfile even when another package declares one of those dependencies in the Remotes: field of its DESCRIPTION. Previously, the Remotes: entry took precedence, so restore could install (or record) the remote's latest commit instead, and then report that the dependency tree was repaired. Similarly, renv::install() now prefers the project's own Remotes: entries, and exact version requirements such as bread (== 1.0.0), over another package's Remotes: entry for the same package. This was a regression in renv 1.2.0. The project's Remotes: entries now also apply to packages that are only indirect dependencies. (#2395)
When another package's Remotes: entry supplies a dependency, renv::install() and renv::restore() now install that dependency from the remote. Previously, a dependency from a git remote could be installed from the package repositories (or the lockfile) instead, while being recorded as coming from the remote. Relatedly, when another package requires a newer version of a package from a git remote (or another non-repository source), renv no longer reports that package at the latest repository version while installing the recorded one; the unsatisfied requirement is reported instead. This was a regression in renv 1.2.0. (#2395)

From NEWS.md in the release

Install

R (CRAN)pak (dev)Ubuntu (r2u)Fedora (COPR)openSUSE (OBS)

install.packages("renv", repos = "https://cloud.r-project.org/")

Installs the current CRAN release. Prebuilt binaries on Windows and macOS.

if (!requireNamespace("pak", quietly = TRUE))
  install.packages("pak", repos = "https://cloud.r-project.org/")
pak::pak("rstudio/renv")

Development version from rstudio/renv. Installs pak first if it is not already available.

Release

# enable cranapt (r2u) if it is not already set up, then install
grep -rqs r2u.stat.illinois.edu /etc/apt/sources.list /etc/apt/sources.list.d/ \
  || curl -fsSL https://raw.githubusercontent.com/eddelbuettel/r2u/master/inst/scripts/add_cranapt_noble.sh | sudo bash
sudo apt install -y r-cran-renv

Fast Ubuntu binaries via r2u (no compilation). The cranapt setup runs once and is skipped when it is already enabled. We list this channel from recorded r2u download activity rather than from a live index of the repository, so treat it as last known rather than guaranteed.

bspm (used by r2u) also needs make: sudo apt install make

# enable the iucar/cran COPR if it is not already present, then install
ls /etc/yum.repos.d/*iucar*cran*.repo >/dev/null 2>&1 \
  || sudo dnf copr enable -y iucar/cran
sudo dnf install -y R-CRAN-renv

RPMs from the iucar/cran COPR, rebuilt from CRAN.

For install.packages() integration in R, also: sudo dnf install R-CoprManager

# add the autoCRAN OBS repo (Tumbleweed) if it is missing, then install
zypper -q lr | grep -qi autoCRAN \
  || sudo zypper addrepo https://download.opensuse.org/repositories/devel:/languages:/R:/autoCRAN/openSUSE_Tumbleweed/devel:languages:R:autoCRAN.repo
sudo zypper install -y R-renv

RPMs auto-built from CRAN on openSUSE OBS (Tumbleweed). We list this channel from recorded autoCRAN download activity rather than from a live index of the repository, so treat it as last known rather than guaranteed.

Health

CRAN checks

13OK

CRAN check page ↗

Slowest check: 11.4 min · r-devel-linux-x86_64-fedora-gcc

Status changes

OK13 OK2026-10-17
WARNING12 OK, 1 WARNING2026-10-01
OK13 OK2026-08-21
WARNING12 OK, 1 WARNING2026-08-17
OK13 OK2026-08-05

Show 12 earlier changesHide 12 earlier changes

NOTE12 OK, 1 NOTE2026-08-01
OK13 OK2026-06-09
ERROR12 OK, 1 ERROR2026-06-08
OK13 OK2026-05-02
NOTE12 OK, 1 NOTE2026-04-29
ERROR11 OK, 1 NOTE, 1 ERROR2026-04-28
NOTE11 OK, 1 NOTE2026-04-25
OK14 OK2026-04-09
NOTE13 OK, 1 NOTE2026-03-28
WARNING10 OK, 3 NOTE, 1 WARNING2026-03-20
NOTE13 OK, 1 NOTE2026-03-17
OK14 OK2026-03-10

Advisories

none known

How this is measured·How advisories are found

Documentation

In release 1.3.1

READMEYes · 381 wordsVignettesYes · 11 · staticNEWSYes · 100% structured · mentions 1.3.1Citation fileNoWebsiteYes · pkgdown

Help pages: 49 (6 internal)includes a package overview page
Examples that run: 6%2 run in a plain check · 33 never run
Exported functions with examples: 77%
Documented parameters: 100%
Return-value docs: 75%
Help pages citing references: 0%

Vignettes (11)

Introduction to renv HTML
Frequently asked questions HTML
Installing packages HTML
Package development HTML
Package sources HTML
packrat vs. renv HTML
Project profiles HTML
Using Python with renv HTML
Using renv with continuous integration HTML
Using renv with Docker HTML

Show 1 moreHide 1 vignette

Using renv with Posit Connect HTML

How these are measured

Downloads

4.3M

CRAN downloads in the past year

Rank #191 · ~11.8K/day · ~359.7K/mo

Releases R versions

Daily download trend is not available in this view yet.

313.4K30 days

877.4K90 days

4.3M1 year

Compare downloads with other packages →

Also on18.1K r2u15 autocran53.9K conda_forge244 c2d4u

How downloads are counted

Repository

rstudio/renv ↗Organization: rstudio

1,164Stars

169Forks

197Open issues

0Open PRs

26Releases

3,411Commits

81Commit identities

License file reads as MIT · 3,411 commits · Last activity 2026-10-17 · +0.1% stars, 30d · Default branch at 1.3.1.9000, ahead of CRAN 1.3.1 (checked 2026-10-18)

Responsiveness

How these are sampled

PRs merged (all time): 87%
Median days to close, 50 most recently updated closed issues: 6
Median days to close, 50 most recently updated closed PRs: 0

Stars over time

2025-10-17 · 1,0932026-10-18 · 1,164

How these are measured

PracticesBeta

11 development-tooling and community-health practices detected across 6 families in the upstream repository

Checks run against github.com/rstudio/renv on 2026-10-18.

Continuous integration (2)

GitHub ActionsR CMD check workflow

The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel

Governance and community (1)

Issue templates

Docs source (4)

README.Rmdpkgdown

GitHub Pages site last deployed 2026-10-17 · The repository has a site deploy workflow

pkgdown site last built 2026-10-06

Coverage (2)

Coverage reporting (Codecov).covrignore

Show all practicesHide 2 practices

Lint, format, editor (1)

RStudio project

Git structural (1)

.gitattributes

How this is detected·Detection ruleset v3 (2026-09-26)

Dependencies

Declared dependencies

27 external dependencies (excludes base and recommended)

Installing renv adds no packages beyond those that come with R.

Depends (0)

none

Imports (1)

utils

LinkingTo (0)

none

Suggests (28)

BiocManager clicompilercovr cpp11 curl devtools generics gitcreds jsonlite jsonvalidate knitr miniUI modules packrat pak pkgload R6 remotes reticulate rmarkdown rstudioapi shiny testthat uuid waldo yaml webfakes

Enhances (0)

none

Dependency license breakdown →

Reverse dependencies

29direct

35indirect

Imports 29

Suggested by 38

Show the 48 most downloaded packagesHide the 48 most downloaded packages

Depends, Imports or LinkingTo, most downloaded first

Suggests, most downloaded first

SimDesign golem attachment dockerfiler mlr3batchmark btw bundle logrx teal BeeBDC inlpubs tidytlg shinyscholar colleyRstats HaDeX framework shiny2docker weakARMA pacs

and 19 more packages that suggest it on CRAN ↗

How these are counted

Code & Tests

People & History

People (3)

Kevin Ushey

Author, Maintainer since 0.8.0 (2019)

Hadley Wickham

Author · added in 1.0.0

Posit Software, PBC

Copyright holder, Funder · added in 0.17.0

Listed in earlier versions (2)

RStudio

no longer listed · 0.8.0 to 0.13.2

RStudio, PBC

no longer listed · 0.14.0 to 0.16.0

Releases (59)

Pick two releases to compare their code metrics.

1.3.1Latest
record
2026-09-29 · current release · diff ↗
1.3.0
record
2026-09-29 · diff ↗
1.2.4
record
2026-08-03 · diff ↗ ·
added 1 export
lockfile
1.2.3
record
2026-05-16 · diff ↗
R
R 4.6.0 released · 2026-04-24
1.2.2
record
2026-04-16 · diff ↗
1.2.1
record
2026-04-12 · diff ↗
1.2.0
record
2026-03-25 · diff ↗ ·
added 1 export
plan
1.1.8
record
2026-03-05 · diff ↗
1.1.7
record
2026-01-27 · diff ↗
1.1.6
record
2026-01-16 · diff ↗ ·
added 1 export
vulns
1.1.5
record
2025-07-24 · diff ↗
R
R 4.5.0 released · 2025-04-11
1.1.4
record
2025-03-20 · diff ↗
1.1.3
record
2025-03-18 · diff ↗
1.1.2
record
2025-03-03 · diff ↗ ·
added 1 export
sysreqs

Show 51 earlier eventsHide 51 earlier events

1.1.1
record
2025-02-07 · diff ↗
1.1.0
record
2025-01-29 · diff ↗
1.0.11
record
2024-10-12 · diff ↗
1.0.10
record
2024-10-05 · diff ↗
1.0.9
record
2024-09-24 · diff ↗
1.0.8
record
2024-09-20 · diff ↗ ·
added 2 exports
lockfile_validate, retrieve
R
R 4.4.0 released · 2024-04-24
1.0.7
record
2024-04-12 · diff ↗
1.0.6
record
2024-04-11 · diff ↗
1.0.5
record
2024-02-29 · diff ↗
1.0.4
record
2024-02-21 · diff ↗
1.0.3
record
2023-09-19 · diff ↗
1.0.2
record
2023-08-15 · diff ↗
1.0.1
record
2023-08-10 · diff ↗
1.0.0
record
2023-07-07 · diff ↗ ·
added 6 exports
checkout, lockfile_create, lockfile_modify, lockfile_read, lockfile_write, sandbox
R
R 4.3.0 released · 2023-04-21
0.17.3
record
2023-04-06 · diff ↗
0.17.2
record
2023-03-18 · diff ↗
0.17.1
record
2023-03-16 · diff ↗
0.17.0
record
2023-03-02 · diff ↗
0.16.0
record
2022-09-29 · diff ↗
0.15.5
record
2022-05-27 · diff ↗
R
R 4.2.0 released · 2022-04-22
0.15.4
record
2022-03-03 · diff ↗
0.15.3
record
2022-02-28 · diff ↗ ·
added 1 export
autoload
0.15.2
record
2022-01-24 · diff ↗
0.15.1
record
2022-01-13 · diff ↗
0.15.0
record
2022-01-04 · diff ↗ ·
added 1 export
repair
0.14.0
record
2021-07-21 · diff ↗ ·
added 2 exports
config, embed
R
R 4.1.0 released · 2021-05-18
0.13.2
record
2021-03-30 · diff ↗
0.13.1
record
2021-03-18 · diff ↗
0.13.0
record
2021-02-24 · diff ↗ ·
added 1 export
use
0.12.5
record
2021-01-09 · diff ↗
0.12.4
record
2021-01-07 · diff ↗
0.12.3
record
2020-11-25 · diff ↗
0.12.2
record
2020-11-05 · diff ↗
0.12.1
record
2020-11-02 · diff ↗
0.12.0
record
2020-08-28 · diff ↗
0.11.0
record
2020-06-26 · diff ↗
0.10.0
record
2020-05-06 · diff ↗
R
R 4.0.0 released · 2020-04-24
0.9.3
record
2020-02-10 · diff ↗ ·
added 1 export
scaffold
0.9.2
record
2019-12-09 · diff ↗
0.9.1
record
2019-12-09 · diff ↗
0.9.0
record
2019-12-05 · diff ↗ ·
added 3 exports
record, rehash, run
0.8.3
record
2019-11-11 · diff ↗ ·
added 1 export
diagnostics
0.8.2
record
2019-10-26 · diff ↗
0.8.1
record
2019-10-26 · diff ↗
0.8.0
record
2019-10-25
R
R 3.6.0 released · 2019-04-26

Package metadata

First published: 2019-10-25
Total releases: 59 / 7 yrs
License: MIT + file LICENSE OSI
Download size: 1.5 MB

Appears in task views

Reproducible Research

Cite

Cite this package

Run in R for the authors' preferred citation:

citation("renv")

Format

Ushey, K., Posit Software, PBC, & Wickham, H. (2026). renv: Project Environments (Version 1.3.1) [Computer software]. https://doi.org/10.32614/CRAN.package.renv

This package has no citation file, so citation() returns this entry built from DESCRIPTION.

Cite the R Observatory

For a number measured here: a download total, a coverage figure, an archival date.

Format

APA

Balamuta, J. J. (2026). R Observatory: Metrics for renv version 1.3.1 [Data set]. HJJB, LLC. Data release v2026-10-21. https://doi.org/10.5281/zenodo.21843040

From data release v2026-10-21, which the citation names so these numbers can be found later. More on citing and the projects behind them.

Report a problem with this page →