Skip to content

weiandata

Organization

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

4
repositories
4
packages
4
scanned
last on 2026-10-11
4
with an AI coding tool found
of 4 scanned

Repositories

4 repositories, 4 packages

Ownership as of 2026-10-18. A repository that moved to another account is listed under its new owner.

CRAN packages in search: owner:weiandata

Repository practices

PracticesBeta

15 practices seen across 6 families in the default branch of the 4 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 4GitHub Actions 4R CMD check workflow 4Coverage workflow 1Checks on R-devel 2
Review and style (3)
EditorConfig 4Code owners 4Pull request template 4
Reproducibility (2)
renv 1data-raw 1
Documentation (1)
pkgdown site 1
Credit and governance (3)
Code of conduct 1Contributing guide 4Security policy 4
Release process (1)
Default branch ahead of CRAN 1
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

4of 4scanned 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
4
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.

How this is detected·Detection ruleset v3 (updated 2026-09-19)
By tool
  • Claude Code4 repositories
    What was found: commits crediting it in 4
    Commits crediting it: at least 43, 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.

Repositories where a tool was found (4)
Packages: DCC
  • Claude Codefirst seen on or before 2026-07-17
    Named in .Rbuildignore: .claude
    Commits: at least 12 crediting it in the message
Packages: IRTC
  • Claude Codefirst seen 2026-07-17
    Commits: at least 20 crediting it in the message
Packages: LISTC
  • Claude Codefirst seen 2026-07-18
    Commits: at least 10 crediting it in the message
Packages: WFC
  • Claude Codefirst seen 2026-07-28
    Named in .Rbuildignore: .claude
    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