Repositories
Method, owners and their repositories 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.
| Repository | Packages | Stars | Forks | Last commit |
|---|---|---|---|---|
| eponge | eponge | 0 | 0 | 26 Mar 2020 |
| matricks | matricks | 4 | 0 | 3 Mar 2020 |
| path.chain | path.chain | 10 | 1 | 8 Oct 2024 |
Practices
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.
- Found
- Not found
Continuous integration
- Travis CI (config file)2 of 3
- AppVeyor3 of 3
Docs source
- pkgdown3 of 3
Coverage
- Codecov1 of 3
CRAN release process
- cran-comments.md1 of 3
Lint, format, editor
- RStudio project3 of 3