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
- 81
- Forks
- 9
- Open issues
- 1
- Last commit
- 12 Mar 2024
Activity
- Commits
- 330
- Open pull requests
- 0
- Tagged releases
- 9
- Latest tagged release
- v0.2.0, 28 Oct 2018
- Issues closed in
- 20 days (median)
- Pull requests closed in
- –
- Pull requests merged
- –
- Created
- 15 Dec 2016
- Licence file reads as
- –
Development practices (15)
| Kind | Found |
|---|---|
| Continuous integration | GitHub Actions, R CMD check workflow The R CMD check workflow runs on macOS |
| Governance and community | Code of conduct, Contributing guide, Issue templates, Support guide |
| Docs source | README.Rmd, pkgdown GitHub Pages site last deployed 2020-10-03 |
| Coverage | Coverage reporting (Codecov) |
| Reproducibility and dev environment | data-raw/, Makefile |
| CRAN release process | cran-comments.md, CRAN-SUBMISSION |
| 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.