Popular repos with an always-failing workflow

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 →

RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
jestjs/jest1,5301,735*1616%24
gin-gonic/gin1913518541%17
scrapy/scrapy9172,964*2518%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.

Does your repo have this?

Scan any public repo free, in seconds. No install, no card.

Scan a repo