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 and Codeberg.Repository signals
- Stars
- 4no change on 30 days ago
- Forks
- 0
- Open issues
- 5
- Last commit
- 5 Oct 2026
Activity
- Commits
- 251
- Open pull requests
- 1
- Tagged releases
- 2
- Latest tagged release
- v0.3.0, 16 Feb 2026
- In development
- Default branch at 0.3.0.9000, ahead of CRAN 0.3.0 (checked 2026-10-25)
- Issues closed in
- 130 days (median)
- Pull requests closed in
- 0 days (median)
- Pull requests merged
- 100%
- Created
- 1 Jan 2023
- Licence file reads as
- –
Development practices (9)
| 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 |
| Docs source | README.Rmd, pkgdown GitHub Pages site last deployed 2026-10-05 The repository has a site deploy workflow |
| 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
AI tools
Method, AI tools Method Beta What is found in a repository is not a measure of the code.AI tool findings
Tools
| Tool | First seen | Found |
|---|---|---|
| Codex | 6 Feb 2026 | Pull request it wrote: opened by a project member |
- Pull request