epiforecasts
Organization8 repositories under this organization are linked from a CRAN or Bioconductor package.
- 8
- repositories
- 8
- packages
- 8
- scanned
- last on 2026-10-22
- 6
- with an AI coding tool found
- of 8 scanned
Repositories
No repository or package matches.
Ownership as of 2026-10-25. A repository that moved to another account is listed under its new owner.
owner:epiforecastsRepository practices
18 practices seen across 6 families in the default branch of the 8 scanned repositories
Each chip gives how many repositories have that practice. The fill is its share of them.
Code of conduct: the repository's own in 3, the organization's default in 5.
How to read thisHide how to read this
A practice counts when its file is in the repository.
A code of conduct, contributing guide or pull request template also counts when GitHub shows the organization's default from its .github repository on a repository that has none of its own. The note under its family then says how many are the repositories' own and how many are the default.
A repository without the file may still follow the practice another way.
AI coding tools
6of 8scanned repositories have a tool found in them
- A pull request opened by a tool's account, commits by a tool's account, or commits whose message credits a tool
- 6
How to read thisHide how to read this
Some tools leave nothing we can find in a repository's files, pull requests or commit messages.
Finding nothing does not mean no tool was used.
- Claude Code6 repositoriesWhat was found: a pull request it wrote in 4; commits by its account in 1; its file in the repository in 3; commits crediting it in 4Commits by its own account: 1, in 1 repositoryCommits crediting it: at least 94, in 4 repositories
How to read thisHide how to read this
The same commit can be in both counts, for example when a tool's own account made it and its message also credits the tool.
Commits crediting a tool are counted from the searches run so far, so that figure is a minimum.
Each count covers the whole default branch, which in some repositories includes code outside the R package.
The two commit counts answer different questions and are never added. Commits crediting a tool are a minimum.
- Claude Codefirst seen 2026-01-21Seen in the repository: CLAUDE.mdNamed in .Rbuildignore: .claude, CLAUDE.mdNamed in .gitignore: .claudePull request it wrote: opened by a project member
- Claude Codefirst seen 2025-11-24Named in .Rbuildignore: .claudeCommits: at least 1 crediting it in the message
- Claude Codefirst seen 2025-10-31Seen in the repository: CLAUDE.mdNamed in .Rbuildignore: .claude, CLAUDE.local.md, CLAUDE.mdNamed in .gitignore: .claudePull request it wrote: opened by a project memberCommits: 1 by its own account · at least 20 crediting it in the message
- Claude Codefirst seen 2026-01-20Named in .Rbuildignore: .claudeCommits: at least 2 crediting it in the message
- Claude Codefirst seen 2026-02-01Named in .Rbuildignore: .claudeNamed in .gitignore: .claudePull request it wrote: opened by a project memberCommits: at least 71 crediting it in the message
- Claude Codefirst seen 2025-12-05Seen in the repository: CLAUDE.mdNamed in .Rbuildignore: .claude, CLAUDE.local.md, CLAUDE.mdNamed in .gitignore: CLAUDE.local.mdPull request it wrote: opened by a project member
A line in .gitignore or .Rbuildignore that names a tool's folder is not counted here. RStudio 2026.06 and later add lines like it when they update a project's ignore files, whether or not the tool is used.
AI findings for repositories whose maintainers asked to be left out are not shown. Ask to be left out
3repositories
They have a review tool's configuration or reviews by its account.
These tools review pull requests and are not counted as tools that wrote code.