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
- 51no change on 30 days ago
- Forks
- 10
- Open issues
- 7
- Last commit
- 8 May 2026
Activity
- Commits
- 216
- Open pull requests
- 0
- Tagged releases
- 17
- Latest tagged release
- v0.4.4, 23 Jun 2025
- In development
- Default branch at 0.4.4.3, ahead of CRAN 0.4.4 (checked 2026-10-25)
- Issues closed in
- 1 day (median)
- Pull requests closed in
- 0 days (median)
- Pull requests merged
- 91%
- Created
- 18 Apr 2017
- Licence file reads as
- –
Development practices (5)
| Kind | Found |
|---|---|
| Continuous integration | GitHub Actions |
| Docs source | pkgdown GitHub Pages site last deployed 2025-06-23 |
| CRAN release process | cran-comments.md |
| Lint, format, editor | RStudio project |
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.