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
- 20
- Forks
- 10
- Open issues
- 6
- Last commit
- 18 Mar 2026
Activity
- Commits
- 231
- Open pull requests
- 1
- Tagged releases
- 21
- Latest tagged release
- v1.0.5, 6 Mar 2026
- In development
- Default branch at 1.0.5.9000, ahead of CRAN 1.0.5 (checked 2026-10-25)
- Issues closed in
- 33 days (median)
- Pull requests closed in
- 1 day (median)
- Pull requests merged
- 88%
- Created
- 5 Aug 2020
- Licence file reads as
- –
Development practices (8)
| 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 |
| Governance and community | Code of conduct |
| Docs source | README.Rmd |
| Coverage | Coverage reporting (Codecov) |
| CRAN release process | cran-comments.md, revdep/ |
| Lint, format, editor | Air |
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.