Recurring audits
Have a repository audit itself every week or every day, with the same report and email as a manual run.
Most security debt arrives quietly, in ordinary pull requests. A recurring audit re-checks a repository on a schedule so the next report lands without anyone deciding to run one.
Turning it on
Open a repository in the dashboard and pick Every week or Every day next to the risk trend. The choice takes effect immediately and can be turned off the same way.
What a scheduled run does
- It runs the same audit a manual run would, with your plan's file and character limits and the same model.
- It writes a full report, which appears in the repository's history and in the findings explorer.
- It emails you when it finishes, in the language saved on your account, unless you turned that email off.
- It counts against your monthly audit allowance, like any other audit.
Limits worth knowing
- Scheduled runs carry no GitHub session, so they cover public repositories.
- When your monthly allowance is used up, the run is skipped rather than failed, and the schedule picks up again next month.
- A daily schedule on the Free plan will exhaust three audits in three days; weekly suits it better.
Schedules are checked every two hours, so a weekly audit runs within two hours of becoming due rather than at an exact clock time.