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
- 8
- Forks
- 0
- Open issues
- 0
- Last commit
- 19 Oct 2023
Activity
- Commits
- 266
- Open pull requests
- 0
- Tagged releases
- 2
- Latest tagged release
- 0.4.0, 19 Oct 2023
- Issues closed in
- 4 days (median)
- Pull requests closed in
- 2 days (median)
- Pull requests merged
- 70%
- Created
- 12 Mar 2020
- Licence file reads as
- –
Development practices (5)
| 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 |
| Coverage | Coverage reporting (Codecov) |
| 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.