actions/cache 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.

0 min/mo
recoverable · across 11 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 11 fixes, each with the exact YAML ↓
0.0%
failure rate, 30d · Top 25%
🕸️ Reliability: Top 25%Failure rate beats ~75% of the 16 repos GitSpider watches.

🏆 You're Top 25%. Show it off in your README:

[![GitSpider](https://gitspider.com/badge/actions/cache.svg)](https://gitspider.com/scan/actions/cache)
Since : findings 12 → 11 · recoverable ~1 → ~0 min/mo
13 workflows · 36 runs (1.2/day) · 20 CI-min (wall-clock) · ≈$0 at private-repo rates (30d)

Where the minutes go (30d)

Code scanning~12 min · 9 runs
Copilot~6 min · 1 runs
Assign issue~1 min · 8 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No job timeout · Tests

~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 →

Premium runners (macOS / Windows) · Tests

~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 →

System packages reinstalled every run · Tests

~0 min/mo

System packages install from the network on every run with no cache. Cache them (cache-apt-pkgs-action) or check whether the runner image already has the tool.

- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

Full guide: how to fix this →

No job timeout · Code scanning

~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 →

Premium runners (macOS / Windows) · Code scanning

~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 →

Scheduled at the top of the hour · Code scanning

~0 min/mo

The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.

on:
  schedule:
    - cron: '53 19 * * 0'  # was '0 19 * * 0' — any non-:00 minute avoids the herd

Full guide: how to fix this →

Scheduled workflow runs in forks · Code scanning

~0 min/mo

The schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.

jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

Full guide: how to fix this →

Missing dependency cache · License check

~0 min/mo

Set `bundler-cache: true` on `ruby/setup-ruby`, or add an `actions/cache@v4` step keyed on `Gemfile.lock`.

- uses: ruby/setup-ruby@v1
  with:
    bundler-cache: true

Full guide: how to fix this →

No job timeout · License check

~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 · Check dist content

~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 · Assign issue

~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 (6 snippets, annotated per workflow)
# No job timeout (applies to: Tests, Code scanning, License check, Check dist content, Assign issue)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

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

# System packages reinstalled every run (applies to: Tests)
- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

# Scheduled at the top of the hour (applies to: Code scanning)
on:
  schedule:
    - cron: '53 19 * * 0'  # was '0 19 * * 0' — any non-:00 minute avoids the herd

# Scheduled workflow runs in forks (applies to: Code scanning)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Missing dependency cache (bundler) (applies to: License check)
- uses: ruby/setup-ruby@v1
  with:
    bundler-cache: true

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

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/actions/cache