Skip to content

rOpenGov

Organization

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

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

Repositories

Repository practices

PracticesBeta

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

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

Continuous integration (6)
Any CI configured, Travis config alone not counted 15GitHub Actions 15R CMD check workflow 14Coverage workflow 12Checks on R-devel 14 of 14Travis CI (config file) 1

Checks on R-devel: 14 of the 14 with an R CMD check workflow.

Review and style (4)
lintr 1Lint workflow 3jarl 1Air 1
Reproducibility (1)
data-raw 6
Documentation (2)
pkgdown site 12GitHub Pages site 14
Credit and governance (4)
Code of conduct 5Contributing guide 2CITATION.cff 5codemeta 4
Release process (1)
Default branch ahead of CRAN 3
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 15scanned 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
1
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.

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 1
    Commits crediting it: at least 6, in 1 repository
  • Codex1 repository
    What was found: its file in the repository in 1
  • GitHub Copilot1 repository
    What was found: its file in the repository in 1
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: eurostat
  • Claude Codefirst seen on or before 2026-09-13
    Commits: at least 6 crediting it in the message
Packages: giscoR
  • Claude Codefirst seen 2026-04-25
    Seen in the repository: .claude
    Named in .Rbuildignore: .claude
  • Codexfirst seen 2026-07-18
    Seen in the repository: .codex
    Named in .Rbuildignore: .codex
  • GitHub Copilotfirst seen 2026-03-22
    Seen in the repository: .github/agents, .github/skills

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

From outside contributors

1repository

A coding agent was used in a pull request from someone outside the project, sent from a fork or by a person who is not an owner, member or collaborator.

These are the contributors' tools and are not counted above.

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