Menu

I scanned the GitHub Actions setup of 139 popular JS/TS repos. Only 1 passed 3 basic checks.
πŸ“°

I scanned the GitHub Actions setup of 139 popular JS/TS repos. Only 1 passed 3 basic checks.

DEV Community: cicdΒ·robsonhealsΒ·15 days ago
#BLabbzrc
#devtocicd#devto#dev#cache#repos
Reading 0:00
15s threshold

I've been building a GitHub Actions linter and didn't want to trust my own heuristics, so I ran it on real projects first: the most-starred JavaScript and TypeScript repos with 1,000–20,000 stars that were active since September 2026. That gave 149 repos, and 139 of them had workflows.

I only checked three things, all boring and all cheap to fix:

Dependency cache : do CI workflows re-download every package on every run?

Concurrency on pull requests : when you push again to a PR, does the outdated run get cancelled?

Job timeouts : does each job have timeout-minutes , or does it fall back to GitHub's default of 6 hours ?

The results

Check Result

Repos with PR workflows that have no concurrency group 97 of 129 (75%)

CI jobs with no timeout-minutes 1,329 of 2,181 (61%)

Repos that install deps with no cache in at least one CI workflow 41 of 121 (34%)

Repos that passed all three 1 of 139

These are popular, well-maintained projects run by experienced people. That isn't a criticism of them.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.