Evidence · DiggingBeagle record
GHAgentCI: Coding-Agent Invocations in CI Workflow Histories
Dataset of coding-agent CI histories and explicit workflow guard configurations.
- Published
- Nov 11, 2026
- Source role
- primary disclosure
Evidence record
Dataset of coding-agent CI histories and explicit workflow guard configurations.
Claim-level citations (2)
- supportsMost sampled coding-agent CI workflows lacked at least one explicitly declared permission or artifact-pinning control: GHAgentCI mined historical GitHub workflow revisions, then classified agent invocations and visible guard settings at the file level. It distinguishes a guard absent from a workflow file from a guard actually absent at runtime, since platform and organization defaults may enforce additional restrictions. The dataset reports 159,878 historical revisions and 9,265 agentic workflows in the latest snapshot. Explicit token permissions appeared in roughly 19 percent and dedicated action SHA pinning in 24 percent. This is a reproducible configuration census, not an observed exploitation rate.
GHAgentCI dataset, reported 159878 revisions, latest workflow guard rates and manual validation
- supportsMost sampled coding-agent CI workflows lacked at least one explicitly declared permission or artifact-pinning control: The sample cannot establish effective permissions for every repository or the outcome of tool calls; deriving compromise incidence from missing YAML declarations would exceed the evidence. The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Primary disclosure: results, scope and limitations