Skip to content

epiverse-trace

Organization

16 repositories under this organization are linked from a CRAN or Bioconductor package.

16
repositories
16
packages
16
scanned
last on 2026-10-22
2
with an AI coding tool found
of 16 scanned

Repositories

Repository practices

PracticesBeta

16 practices seen across 6 families in the default branch of the 16 scanned repositories

Each chip gives how many repositories have that practice. The fill is its share of them.

Continuous integration (5)
Any CI configured, Travis config alone not counted 16GitHub Actions 16R CMD check workflow 16Coverage workflow 16Checks on R-devel 16
Review and style (4)
lintr 16Lint workflow 15pre-commit 2Pull request template 16

Pull request template: the repository's own in 3, the organization's default in 13.

Reproducibility (1)
data-raw 7
Documentation (2)
pkgdown site 16GitHub Pages site 16
Credit and governance (3)
Code of conduct 16Contributing guide 16CITATION.cff 16

Code of conduct: the repository's own in 0, the organization's default in 16.

Contributing guide: the repository's own in 2, the organization's default in 14.

Release process (1)
Default branch ahead of CRAN 10
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

Found inBeta

2of 16scanned 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
2
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.

A repository where two tools were found is counted once in the total and once under each tool, so the tool rows add up to more than 2.

Finding nothing does not mean no tool was used.

How this is detected·Detection ruleset v3 (updated 2026-09-19)
By tool
  • Claude Code2 repositories
    What was found: its file in the repository in 1; commits crediting it in 2
    Commits crediting it: at least 20, in 2 repositories
  • GitHub Copilot1 repository
    What was found: a pull request opened by its account in 1; commits by its account in 1
    Commits by its own account: 7, in 1 repository
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.

Repositories where a tool was found (2)
Packages: epichains
  • Claude Codefirst seen 2026-07-07
    Seen in the repository: CLAUDE.md
    Named in .Rbuildignore: CLAUDE.local.md, CLAUDE.md
    Commits: at least 19 crediting it in the message
  • GitHub Copilotfirst seen 2026-06-08
    Pull request: opened by its own account
    Commits: 7 by its own account
Packages: epiparameter
  • Claude Codefirst seen on or before 2026-09-16
    Commits: at least 1 crediting it in the message

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

Privacy choices

These apply to this browser and are stored on this device only. Nothing about your choice is sent to us.

Read the privacy policy