A workflow that fails on almost every run, usually a scheduled one nobody watches, is the most common thing we find that nobody has turned off. It is rarely a code problem and almost always an invisible-background-noise one. Below are well-known projects whose own scorecard flags it. Read the fix →
| Repo | Runs (30d) | CI min (30d) | Recoverable min/mo | Failure rate | Findings |
|---|---|---|---|---|---|
| jestjs/jest | 1,530 | 1,735* | 161 | 6% | 24 |
| gin-gonic/gin | 191 | 351 | 85 | 41% | 17 |
| scrapy/scrapy | 917 | 2,964* | 25 | 18% | 10 |
* CI min, recoverable min and failure rate cover only the latest 500 runs of a repo with more in 30 days.
Public data from each repo's GitHub Actions. Minutes are wall-clock workflow time over 30 days. These repos run Actions free (public repos always do). Each scorecard shows the private-repo dollar equivalent as a labeled estimate. Repo owners can remove their scorecard any time.