Skip to content

samuelbharti

Personal account

5 repositories under this account are linked from a CRAN or Bioconductor package.

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

Repositories

5 repositories, 5 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:samuelbharti

Repository practices

PracticesBeta

19 practices seen across 5 families in the default branch of the 5 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 5GitHub Actions 5R CMD check workflow 5Coverage workflow 1Checks on R-devel 3
Review and style (6)
lintr 4Lint workflow 4Air 4pre-commit 4Code owners 2Pull request template 4
Documentation (2)
pkgdown site 1GitHub Pages site 5
Credit and governance (5)
Code of conduct 5Contributing guide 5CITATION.cff 5Zenodo 1Security policy 5
Release process (1)
Default branch ahead of CRAN 1 of 1

Default branch ahead of CRAN: 1 of the 1 whose default branch version could be compared with the CRAN release.

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 account'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

3of 5scanned 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
A tool's file in the repository and nothing else
1
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 Code2 repositories
    What was found: a pull request it wrote in 1; its file in the repository in 1
  • GitHub Copilot1 repository
    What was found: a pull request opened by its account in 1; commits by its account in 1; its file in the repository in 1
    Commits by its own account: 8, 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 (3)
Packages: biobouncer
  • Claude Codefirst seen 2026-07-09
    Seen in the repository: CLAUDE.md
Packages: biocohort
  • Claude Codefirst seen 2026-09-07
    Named in .gitignore: .claude
  • GitHub Copilotfirst seen 2026-02-05
    Seen in the repository: .github/instructions
    Pull request: opened by its own account
    Commits: 8 by its own account
Packages: plotomics
  • Claude Codefirst seen 2026-07-09
    Named in .gitignore: .claude
    Pull 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

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