GitSpider

sveltejs/kit GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated .

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

617 min/mo
recoverable (~25% of CI time) · across 7 patterns · ≈$4/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 7 fixes, each with the exact YAML ↓
7.6%
failure rate, 30d
1h 10m
avg time to recover from a failure
Since : findings 11 → 7 · recoverable ~1,074 → ~617 min/mo
13 workflows · 500 runs (16.7/day) · 2,516 CI-min (wall-clock) · ≈$15 at private-repo rates (30d)

Where the minutes go (30d)

CI~2,003 min · 191 runs
CodeQL~415 min · 162 runs
Release~49 min · 29 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · CI

~601 min/mo · ≈$4/mo

Set `cache: 'pnpm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

Full guide: how to fix this →

Missing dependency cache · Release

~15 min/mo

Set `cache: 'pnpm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

Full guide: how to fix this →

No concurrency control · Autofix Lint

~1 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

Also found: 4 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

Premium runners (macOS / Windows) · CI

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

No job timeout · Release

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

No job timeout · Platform Tests (All)

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

No job timeout · Autofix Lint

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

Copy every fix as one block (4 snippets, annotated per workflow)
# Missing dependency cache (pnpm) (applies to: CI, Release)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

# No concurrency control (applies to: Autofix Lint)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Premium runners (macOS / Windows) (applies to: CI)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# No job timeout (applies to: Release, Platform Tests (All), Autofix Lint)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.

Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/sveltejs/kit.svg)](https://gitspider.com/scan/sveltejs/kit)

Want this on every push?

This scorecard is a one-time snapshot. Install the free GitHub App to track this repo continuously: new regressions caught as they land, trends over time, on your public and private repos. Team adds the offending commit on the PR + Slack alerts.

Install & monitor this repo →

💬 On Team, this same analysis posts automatically to every PR: the regression, and the exact commit that caused it, right where your team already looks. See plans →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/sveltejs/kit