← All scorecards

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 →

calcom/cal.com
500+runs (30d)
$1est. (30d)
26findings
mui/material-ui
500+runs (30d)
$13est. (30d)
24findings
nuxt/nuxt
500+runs (30d)
$4est. (30d)
28findings
jestjs/jest
500+runs (30d)
$27est. (30d)
15findings
microsoft/playwright
500+runs (30d)
$49est. (30d)
35findings
react-hook-form/react-hook-form
500+runs (30d)
$4est. (30d)
20findings
trpc/trpc
500+runs (30d)
$8est. (30d)
17findings
gohugoio/hugo
370runs (30d)
$52est. (30d)
10findings
drizzle-team/drizzle-orm
282runs (30d)
$6est. (30d)
8findings
psf/requests
259runs (30d)
$2est. (30d)
20findings
pallets/flask
51runs (30d)
$0est. (30d)
5findings

Public data from each repo's GitHub Actions. These repos run Actions free (public repos always do); the dollar figures are the equivalent cost on a private repo, a rough estimate at standard Linux pricing. Actual runners and matrices vary. 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