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
- 3no change on 30 days ago
- Forks
- 0
- Open issues
- 1
- Last commit
- 8 Sep 2023
Activity
- Commits
- 54
- Open pull requests
- 0
- Tagged releases
- 3
- Latest tagged release
- v0.1-4, 2 Sep 2023
- In development
- Default branch at 0.1-4.9000, ahead of CRAN 0.1-4 (checked 2026-10-25)
- Issues closed in
- –
- Pull requests closed in
- –
- Pull requests merged
- –
- Created
- 22 May 2017
- Licence file reads as
- –
Development practices (2)
| Kind | Found |
|---|---|
| Docs source | README.Rmd |
| CRAN release process | cran-comments.md |
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.