elizaOS/eliza GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated 7/11/2026, 5:15:41 AM.

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

95 min/mo
recoverable (~5% of CI time) · across 17 patterns · ≈$1/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 17 fixes, each with the exact YAML ↓
8.8%
failure rate, 30d
2m
avg time to recover from a failure
100 workflows · 500 runs (16.7/day) · 2,067 CI-min (wall-clock) · ≈$12 at private-repo rates (30d)

Where the minutes go (30d)

(deleted or unlisted workflow)~248 min · 8 runs
Tests~175 min · 7 runs
(deleted or unlisted workflow)~169 min · 18 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Workflow runs on both push and pull_request · Cloud Tests

~33 min/mo

Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.

on:
  push:
    branches: [main]
  pull_request:

Full guide: how to fix this →

Missing dependency cache · Quality (Extended)

~32 min/mo

Set `cache: 'npm'` 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: 'npm'

Full guide: how to fix this →

Missing dependency cache · Cloud CF Deploy

~30 min/mo

Set `cache: 'npm'` 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: 'npm'

Full guide: how to fix this →

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

No job timeout · PR Title 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 path filters on triggers · PR Title Check

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

No concurrency control · Claude Code

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

No job timeout · Auto Label

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

Scheduled at the top of the hour · Docker CI Smoke

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Docker CI Smoke

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

Full-history clone (fetch-depth: 0) · Docker CI Smoke

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

Missing dependency cache · Quality (Fork)

~0 min/mo

Set `cache: 'npm'` 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: 'npm'

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · Quality (Fork)

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

Missing dependency cache · Scenario Matrix (develop)

~0 min/mo

Add `Swatinem/rust-cache@v2` (the de-facto cargo cache), or an `actions/cache@v4` step keyed on `Cargo.lock`.

- uses: Swatinem/rust-cache@v2

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · Scenario Matrix (develop)

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

Premium runners (macOS / Windows) · Tests

~0 min/mo

macOS bills ~10× and Windows ~2× 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 workflow runs in forks · Tests

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

No job timeout · Develop Staging Beta 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 →

Copy every fix as one block (10 snippets, annotated per workflow)
# Workflow runs on both push and pull_request — applies to: Cloud Tests
on:
  push:
    branches: [main]
  pull_request:

# Missing dependency cache (npm) — applies to: Quality (Extended), Cloud CF Deploy, Quality (Fork)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

# No job timeout — applies to: PR Title Check, Auto Label, Develop Staging Beta Release
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# No path filters on triggers — applies to: PR Title Check
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# No concurrency control — applies to: Claude Code
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Scheduled at the top of the hour — applies to: Docker CI Smoke
on:
  schedule:
    - cron: '55 7 * * *'  # was '0 7 * * *' — any non-:00 minute avoids the herd

# Scheduled workflow runs in forks — applies to: Docker CI Smoke, Tests
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Full-history clone (fetch-depth: 0) — applies to: Docker CI Smoke, Quality (Fork), Scenario Matrix (develop)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Missing dependency cache (cargo) — applies to: Scenario Matrix (develop)
- uses: Swatinem/rust-cache@v2

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

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 →

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

Share this scorecard: https://gitspider.com/scan/elizaOS/eliza
Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/elizaOS/eliza.svg)](https://gitspider.com/scan/elizaOS/eliza)