Skip to main content
GET
Scan recent workflow runs
Attackers who steal a token often push a workflow that sends secrets to their server, let it run once, then revert the commit or force-push over it. The file disappears from the repository, but the run stays in the Actions tab. This endpoint takes each recent run, fetches the workflow file at the exact commit it ran, analyzes it, and checks whether that commit is still part of its branch. Costs 10 units of your rate limit.

Path parameters

Query parameters

Example

Response

Finding

Same fields as workflow findings, plus: For workflow versions that still match the default branch, only high and critical findings are included. Use Analyze a workflow for the full hardening report on current files.

Run

Branch deletion after a merged pull request is normal, so branch_deleted alone does not produce a finding.

Rules specific to runs

Errors

Limits

Only public repositories are supported. GitHub keeps run history for 90 days by default, and repository admins can delete runs, so a clean result covers what is still visible.

Path Parameters

owner
string
required
Pattern: ^[A-Za-z0-9_.-]{1,100}$
repo
string
required
Pattern: ^[A-Za-z0-9_.-]{1,100}$

Query Parameters

limit
integer
default:30
Required range: 1 <= x <= 50

Response

Run history report

repository
object
required
runs_scanned
integer
required
summary
object
required
findings
object[]
required
runs
object[]
required
checks
object
required
checked_at
string<date-time>
required