Repository
Method, figures by host Method Repository signals are the figures read from the source repository a package links to: stars, forks, issues, commits, releases and the time issues take to close. They are read from GitHub, GitLab, Codeberg and Bitbucket.Repository signals
URL and BugReports fields of its DESCRIPTION file. Read-only mirrors, the cran and bioc accounts on GitHub and git.bioconductor.org, are left out.
- Stars
- 33no change on 30 days ago
- Forks
- 8
- Open issues
- –
- Last commit
- 18 Jul 2026
Activity
- Commits
- 114
- Open pull requests
- 0
- Tagged releases
- 0
- Latest tagged release
- –
- Issues closed in
- –
- Pull requests closed in
- 0 days (median)
- Pull requests merged
- 100%
- Created
- 18 Jan 2022
- Licence file reads as
- –
Development practices (2)
| Kind | Found |
|---|---|
| Continuous integration | GitHub Actions, R CMD check workflow The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel |
Method, repository practices Method Beta Each week a scan of the public source repository a package links to looks for the tools a maintainer has set up, and the Repository section lists the findings. Repositories on GitHub and GitLab are scanned.Repository practices
R CMD build reads .Rbuildignore and leaves out files used only in development, such as .github/, .lintr, renv/, a Dockerfile and cran-comments.md, so the released source file holds almost none of them. The repository is the one place these files stay visible.