aimeertaylor

Personal account

1 repository under this account is linked from a CRAN or Bioconductor package.

1: repository
1: package
1: scanned; last on 2026-10-11

Repositories

1 repository, 1 package

aimeertaylor/Pv3Rs ↗Pv3Rs

No repository or package matches.

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

CRAN packages in search: owner:aimeertaylor

Repository practices

PracticesBeta

8 practices seen across 4 families in the default branch of the 1 scanned repository

Continuous integration (4)

Any CI configured, Travis config alone not countedGitHub ActionsR CMD check workflowChecks on R-devel

Reproducibility (1)

data-raw

Documentation (2)

pkgdown siteGitHub Pages site

Release process (1)

Default branch ahead of CRAN

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 and the repository has none of its own. The note under its family then says whether it is the repository's own or the account's default.

A repository without the file may still follow the practice another way.

How this is detected·Detection ruleset v3 (2026-09-26)·The same counts across every scanned repository

AI coding tools

AI coding toolsBeta

We found no AI coding tool in this repository.

Finding nothing does not mean no tool was used. Some tools leave nothing we can find in a repository's files, pull requests or commit messages.

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

How this is detected·Detection ruleset v3 (updated 2026-09-19)