danielraffel/pulp 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.

2 min/mo
recoverable · across 43 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 43 fixes, each with the exact YAML ↓
8.2%
failure rate, 30d
7m
avg time to recover from a failure
Since : findings 67 → 43 · recoverable ~565 → ~2 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
82 workflows · 500 runs (16.7/day) · 9,026 CI-min (wall-clock) · ≈$54 at private-repo rates (30d)

Where the minutes go (30d)

Coverage~1,963 min · 23 runs
Build and Test~1,482 min · 31 runs
CodeQL~868 min · 21 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · Vellum freeze

~2 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: 42 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

Premium runners (macOS / Windows) · Android Build

~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 path filters on triggers · API contracts

~0 min/mo

Runs on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.

on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · API contracts

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

System packages reinstalled every run · API contracts

~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 · Auto-release watchdog

~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 · Auto-Release on Version Bump

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

Workflow can trigger itself · Auto-Release on Version Bump

~0 min/mo

Runs on push, pushes back with a custom token, and has no recursion guard, so this shape can trigger itself in a loop. Add `[skip ci]` to the commit, a `paths:` filter, or a `github.actor` gate.

      - run: |
          git commit -m "chore: update [skip ci]"
          git push

Full guide: how to fix this →

No path filters on triggers · Build and Test

~0 min/mo

Runs on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.

on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

Full guide: how to fix this →

Premium runners (macOS / Windows) · Build and Test

~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 · Conflict-marker guard

~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) · Control shipping native matrix

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

Premium runners (macOS / Windows) · Coverage

~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 · Docs Consistency

~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 · Deploy Docs

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

cancel-in-progress on a deploy workflow · Deploy Docs

~0 min/mo

This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too, so a queued deploy is silently dropped when a newer run arrives. Use a group-only `concurrency:` block on deploys.

concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

Full guide: how to fix this →

System packages reinstalled every run · Deploy Docs

~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 · Docs (Material preview)

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

Full-history clone (fetch-depth: 0) · Docs (Material preview)

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

System packages reinstalled every run · Docs (Material preview)

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

Premium runners (macOS / Windows) · Example validation

~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 · IWYU advisory

~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 · License Audit

~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) · Non-Skia build guard

~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 · Required gate liveness

~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 · Sanitizer 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) · Sanitizer 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 →

No job timeout · Source-tree pollution 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 →

Full-history clone (fetch-depth: 0) · Source-tree pollution check

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

No job timeout · Vellum freeze

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

Full-history clone (fetch-depth: 0) · Vellum freeze

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

No job timeout · Vellum observatory dispatch

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

Full-history clone (fetch-depth: 0) · Vellum observatory dispatch

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

No job timeout · Vellum routing contract

~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 · Vellum trusted gate

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

Full-history clone (fetch-depth: 0) · Vellum trusted gate

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

No job timeout · Version-at-Land (single-writer, push)

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

Frequent scheduled runs · Version-at-Land (single-writer, push)

~0 min/mo

A schedule cron fires >4x/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.

on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

Full guide: how to fix this →

No job timeout · Versioning & Skill-Sync

~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 · WebCLAP Cloudflare

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

Cache without restore-keys · WebCLAP Cloudflare

~0 min/mo

The cache restores only on an exact key match, so any lockfile change means a full cold download. Add a `restore-keys:` prefix line for partial restores.

    key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
    restore-keys: |
      deps-${{ runner.os }}-

Full guide: how to fix this →

Scheduled at the top of the hour · WebCLAP Cloudflare

~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: '20 8 * * 1'  # was '0 8 * * 1' — any non-:00 minute avoids the herd

Full guide: how to fix this →

No job timeout · Workflow 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 (11 snippets, annotated per workflow)
# No concurrency control (applies to: Vellum freeze)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Premium runners (macOS / Windows) (applies to: Android Build, Build and Test, Control shipping native matrix, Coverage, Example validation, Non-Skia build guard, Sanitizer Tests)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# No path filters on triggers (applies to: API contracts, Build and Test)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Full-history clone (fetch-depth: 0) (applies to: API contracts, Docs (Material preview), Source-tree pollution check, Vellum freeze, Vellum observatory dispatch, Vellum trusted gate)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# System packages reinstalled every run (applies to: API contracts, Deploy Docs, Docs (Material preview))
- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

# No job timeout (applies to: Auto-release watchdog, Auto-Release on Version Bump, Conflict-marker guard, Docs Consistency, Deploy Docs, Docs (Material preview), IWYU advisory, License Audit, Required gate liveness, Sanitizer Tests, Source-tree pollution check, Vellum freeze, Vellum observatory dispatch, Vellum routing contract, Vellum trusted gate, Version-at-Land (single-writer, push), Versioning & Skill-Sync, WebCLAP Cloudflare, Workflow lint)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Workflow can trigger itself (applies to: Auto-Release on Version Bump)
      - run: |
          git commit -m "chore: update [skip ci]"
          git push

# cancel-in-progress on a deploy workflow (applies to: Deploy Docs)
concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

# Frequent scheduled runs (applies to: Version-at-Land (single-writer, push))
on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

# Cache without restore-keys (applies to: WebCLAP Cloudflare)
    key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
    restore-keys: |
      deps-${{ runner.os }}-

# Scheduled at the top of the hour (applies to: WebCLAP Cloudflare)
on:
  schedule:
    - cron: '20 8 * * 1'  # was '0 8 * * 1' — any non-:00 minute avoids the herd

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/danielraffel/pulp.svg)](https://gitspider.com/scan/danielraffel/pulp)

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/danielraffel/pulp