vitejs/vite - GitHub Actions cost & CI smells

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

Workflows

Per-run $ (modeled)

$1.09

Monthly $ @ 30/day

$979.2

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. vitejs/vite'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-concurrency`	6
`missing-cache`	2
`stale-cache-key`	1
`wide-trigger`	1

Per-workflow breakdown

Workflow	Jobs	Per-run $	Findings
`ci.yml`	5	$0.26	4
`issue-template-check.yml`	2	$0.13	2
`pull-request-template-check.yml`	2	$0.13	3
`copilot-setup-steps.yml`	1	$0.06	3
`ecosystem-ci-trigger.yml`	1	$0.06	1
`issue-close-require.yml`	1	$0.06	1
`issue-labeled.yml`	1	$0.06	1
`lock-closed-issues.yml`	1	$0.06	1
`preview-release.yml`	1	$0.06	3
`publish.yml`	1	$0.06	3
`release-tag.yml`	1	$0.06	2
`semantic-pull-request.yml`	1	$0.06	2

Examples of what ci-doctor reports

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

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

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

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

issue-template-check.yml · WARN missing-timeout
Job 'post-results' has no timeout-minutes. Default is 360 (6h). A hung job can drain your CI budget.

pull-request-template-check.yml · WARN missing-concurrency
No top-level concurrency block. New pushes will not cancel in-flight runs of stale commits, doubling spend on rapid-push branches.

What you can do

If you maintain vitejs/vite 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