Repositories
Most R packages are developed in a public repository. Here is where those repositories sit, what they carry, and how long work stays open.
- 16,803
- Packages with a repository
- 16,654
- Distinct repositories
- 43
- Hosts represented
16,237
Packages with a public repository in 2026
Packages with a known public repository each year. The latest year is a direct count and earlier years are reconstructed from events.
5.0
Median stars in 2026
Across packages with a public repository that year.
1.0
Median open issues in 2026
Across packages with a public repository that year.
Hosting
Where R package repositories are hosted, and how the share breaks down.
Out of 16,803 packages with a repository we could read.
Repository contents
Scanned from the repository tree. A package may follow a practice by other means, so these counts are lower bounds.
Continuous integration
Automated testing and build services configured in the repository.
Checks on R-devel is a share of the repositories with an R CMD check workflow, not of every repository scanned.
Review and style
Tools and conventions that shape how code is written and reviewed.
A pull request template counts when GitHub shows one for the repository, including an organization default from its .github repository.
From Sep 26, 2026 the scan also finds pull request templates under lower-case names, in more folders and as organization defaults, so that count rose that week.
Reproducibility
Infrastructure for recreating the development or analysis environment.
Documentation
Package websites and how they are deployed.
For agents and models
Files published for machine readers rather than people.
Credit and governance
How the project tracks contributions, funding, and decision-making.
A code of conduct or contributing guide counts when GitHub shows one for the repository, including an organization default from its .github repository.
Release process
How the default branch compares with the release on CRAN.
The share is of the repositories whose default branch version could be compared with the CRAN release, not of every repository scanned.
Out of 16,242 repositories scanned. Detection methodology
Time to close
Each repository contributes its own median. Only those with at least one closure are included.
Days to close an issue
The repository median, so half of its closed issues took longer.
10,114 repositories have this measurement.
Days to close a pull request
Closed covers merged and rejected alike.
9,715 repositories have this measurement.
Notes
How repositories are counted
Repository URLs come from each package's DESCRIPTION file. A repository serving multiple packages counts once in the distinct total but once per package elsewhere. 75 of these repositories are marked archived by their host while the package is still published. Practice counts are lower bounds: the weekly scan sees only what is committed, and anything in .Rbuildignore is invisible.