jestjs/jest - GitHub Actions cost & CI smells

From the depmedic OSS benchmark dataset. Source: public workflow YAML in jestjs/jest/.github/workflows.

Workflows

Per-run $ (modeled)

$0.90

Monthly $ @ 30/day

$806.4

ci-doctor findings

Numbers are modeled: 8 minutes per priced job, 30 runs per day per workflow, 30-day month, GitHub-hosted runner rate sheet. jestjs/jest's real run frequency is unknown to me. Smells, however, are real - they come from parsing the actual YAML.

Findings by rule

Rule	Hits
`missing-timeout`	16
`missing-permissions`	4

Per-workflow breakdown

Workflow	Jobs	Per-run $	Findings
`nodejs.yml`	10	$0.45	4
`close-stale.yml`	2	$0.13	2
`issues.yml`	2	$0.13	2
`lock.yml`	1	$0.06	1
`nightly.yml`	7	$0.06	1
`pkg-pr-new.yml`	1	$0.06	2
`prepare-cache.yml`	1	$0.00	2
`test-nightly.yml`	2	$0.00	3
`test.yml`	2	$0.00	3

Examples of what ci-doctor reports

nodejs.yml · WARN missing-timeout
Job 'ts-compatibility' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

nodejs.yml · WARN missing-timeout
Job 'static-checks' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

nodejs.yml · WARN missing-timeout
Job 'test-leak' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

close-stale.yml · WARN missing-timeout
Job 'stale' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

close-stale.yml · WARN missing-timeout
Job 'stale-legacy' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

issues.yml · WARN missing-timeout
Job 'questions' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

What you can do

If you maintain jestjs/jest or a similar workflow shape, three patterns probably move the most dollars per minute of work:

Add a concurrency: block with cancel-in-progress: true on every PR-triggered workflow.
Set timeout-minutes on every job (default is 6 hours).
Make sure every setup-* action sets cache: <ecosystem>.

Free CLIs that automate the audit and the pin step:

npx ci-doctor             # 14-rule audit
npx ci-doctor --fix       # auto-apply the four safe fixes
npx pin-actions           # pin every uses: ref to a SHA
npx gha-budget            # estimate per-run $ + monthly

About this dataset