Open statistics
What do the scans find?
Real findings from public repository scans. No private repos, source code or usernames are shown.
Most common findings
A finding means a check identified a risk. These are not counts of deployments that actually failed.
| Check | Red findings | Needs review | Share with findings |
|---|---|---|---|
| Environment variables | 7 | 1 | 42%8 / 19 checked repos |
| Next.js entrypoint | 2 | 3 | 28%5 / 18 checked repos |
| Import paths | 2 | 0 | 11%2 / 18 checked repos |
| Server / Edge compatibility | 2 | 0 | 11%2 / 19 checked repos |
| Build configuration | 0 | 1 | 6%1 / 17 checked repos |
| Dependencies | 0 | 1 | 6%1 / 16 checked repos |
| Supabase | 0 | 1 | 33%1 / 3 checked repos |
| Prisma / database | 0 | 0 | 0%0 / 2 checked repos |
| Exposed secrets | 0 | 0 | 0%0 / 17 checked repos |
Scans per day
Complete public scans, including rescans. Days use UTC.
How we count
We use up to the 5,000 latest complete public scans from the past 30 days, excluding example reports and partial scans. Rankings use the latest complete scan per repo so rescans do not carry extra weight. Each percentage uses the repos where that check ran as its denominator. Ignored checks are excluded. This is a self-selected sample, not representative of all GitHub repos.
Updated: · Data is cached for about one minute.
Recent activitySee the stats →
- A public repo was scanned · 16:00 UTC
- A public repo was scanned · 16:00 UTC
- A public repo was scanned · 12:00 UTC
- A public repo was scanned · 12:00 UTC
- A public repo was scanned · 11:00 UTC
- A public repo was scanned · 21:00 UTC
- A public repo was scanned · 19:00 UTC
- A public repo was scanned · 19:00 UTC
Anonymous · times rounded to the hour · refreshes every minute
From finding to fix
Learn why builds fail, or check your own repository.