Chia-Network/chia-blockchain 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.

32 min/mo
recoverable · across 61 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 61 fixes, each with the exact YAML ↓
3.8%
failure rate, 30d · Top 25%
56m
avg time to recover from a failure
🕸️ 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/Chia-Network/chia-blockchain.svg)](https://gitspider.com/scan/Chia-Network/chia-blockchain)
Since : findings 61 → 61 · recoverable ~35 → ~32 min/mo
32 workflows · 500 runs (16.7/day) · 9,597 CI-min (wall-clock) · ≈$58 at private-repo rates (30d)

Where the minutes go (30d)

📦🚀 Build Installers - MacOS~1,947 min · 24 runs
📦🚀 Build Installer - Linux RPM AMD64~1,150 min · 26 runs
📦🚀 Build Installer - Linux DEB~1,114 min · 26 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · 🚨 Check PR Labels

~18 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 concurrency control · 🩹 Conflict Check

~9 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 concurrency control · 🚨 Dependency Review

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

Artifacts at default retention · 🚨🚀 Lint and upload source distribution

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Large build matrix · 🚨🚀 Lint and upload source distribution

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Premium runners (macOS / Windows) · 🚨🚀 Lint and upload source distribution

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

Third-party actions pinned to a mutable ref · 🚨🚀 Lint and upload source distribution

~0 min/mo

12 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: chia-network/actions/clean-workspace@<full-sha>  # was @main

Artifacts at default retention · 📦🚀 Build Installer - Windows 10

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · 📦🚀 Build Installer - Windows 10

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

Full-history clone (fetch-depth: 0) · 📦🚀 Build Installer - Windows 10

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

environment: on a CI job · 📦🚀 Build Installer - Windows 10

~0 min/mo

A test/build job is bound to a GitHub environment, so every run counts as a deployment: PR and deployments-API noise. Use repository secrets or OIDC for non-deploy jobs.

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · 📦🚀 Build Installer - Windows 10

~0 min/mo

6 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/setjobenv@<full-sha>  # was @main

No job timeout · 🚨 CodeQL

~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) · 🚨 GitHub Super Linter

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

Artifacts at default retention · 📦🚀 Build Installer - Linux RPM AMD64

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Large build matrix · 📦🚀 Build Installer - Linux RPM AMD64

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · 📦🚀 Build Installer - Linux RPM AMD64

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

Third-party actions pinned to a mutable ref · 📦🚀 Build Installer - Linux RPM AMD64

~0 min/mo

5 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/git-mark-workspace-safe@<full-sha>  # was @main

Artifacts at default retention · 📦🚀 Build Installer - Linux DEB

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Large build matrix · 📦🚀 Build Installer - Linux DEB

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · 📦🚀 Build Installer - Linux DEB

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

Third-party actions pinned to a mutable ref · 📦🚀 Build Installer - Linux DEB

~0 min/mo

6 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

No job timeout · 🏗️ Test Install Scripts

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

Large build matrix · 🏗️ Test Install Scripts

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Premium runners (macOS / Windows) · 🏗️ Test Install Scripts

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

Full-history clone (fetch-depth: 0) · 🏗️ Test Install Scripts

~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 · 🏗️ Test Install Scripts

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

Third-party actions pinned to a mutable ref · 🏗️ Test Install Scripts

~0 min/mo

3 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/setup-python@<full-sha>  # was @main

Large build matrix · 🚨 pre-commit

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Premium runners (macOS / Windows) · 🚨 pre-commit

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

Full-history clone (fetch-depth: 0) · 🚨 pre-commit

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

Third-party actions pinned to a mutable ref · 🚨 pre-commit

~0 min/mo

4 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

No job timeout · 🧪 test

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

Artifacts at default retention · 🧪 test

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · 🧪 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 →

Scheduled at the top of the hour · 🧪 test

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

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · 🧪 test

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

Third-party actions pinned to a mutable ref · 🧪 test

~0 min/mo

4 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead. (2 more on a major-version tag like @v4; consider full-SHA pinning there too.)

uses: Chia-Network/actions/setup-python@<full-sha>  # was @main

No job timeout · 📦🚀 Trigger Dev Docker Build

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

Third-party actions pinned to a mutable ref · 📦🚀 Trigger Dev Docker Build

~0 min/mo

2 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/github/glue@<full-sha>  # was @main

Artifacts at default retention · ⚡️ Benchmarks

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · ⚡️ Benchmarks

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

Third-party actions pinned to a mutable ref · ⚡️ Benchmarks

~0 min/mo

5 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

No job timeout · 🚨 Check Dependency Artifacts

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

Large build matrix · 🚨 Check Dependency Artifacts

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Premium runners (macOS / Windows) · 🚨 Check Dependency Artifacts

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

Third-party actions pinned to a mutable ref · 🚨 Check Dependency Artifacts

~0 min/mo

2 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

No job timeout · 🩹 Conflict 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 · 🩹 Conflict 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 →

Third-party actions pinned to a mutable ref · 🩹 Conflict Check

~0 min/mo

1 third-party action pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Chia-Network/actions/label-conflict@<full-sha>  # was @main

Artifacts at default retention · 📦🚀 Build Installers - MacOS

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · 📦🚀 Build Installers - MacOS

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

Full-history clone (fetch-depth: 0) · 📦🚀 Build Installers - MacOS

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

Third-party actions pinned to a mutable ref · 📦🚀 Build Installers - MacOS

~0 min/mo

6 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead. (1 more on a major-version tag like @v4; consider full-SHA pinning there too.)

uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

No job timeout · 🚨 Dependency Review

~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 PR Labels

~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 · 🚨 Check PR Labels

~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) · 🚨 Check commit signing

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

Third-party actions pinned to a mutable ref · 🚨 Check commit signing

~0 min/mo

1 third-party action pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: chia-network/actions/check-commit-signing@<full-sha>  # was @main

Artifacts at default retention · Dependency Cursor Review

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · Dependency Cursor Review

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

Copy every fix as one block (17 snippets, annotated per workflow)
# No concurrency control (applies to: 🚨 Check PR Labels, 🩹 Conflict Check, 🚨 Dependency Review)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Artifacts at default retention (applies to: 🚨🚀 Lint and upload source distribution, 📦🚀 Build Installer - Windows 10, 📦🚀 Build Installer - Linux RPM AMD64, 📦🚀 Build Installer - Linux DEB, 🧪 test, ⚡️ Benchmarks, 📦🚀 Build Installers - MacOS, Dependency Cursor Review)
- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

# Large build matrix (applies to: 🚨🚀 Lint and upload source distribution, 📦🚀 Build Installer - Linux RPM AMD64, 📦🚀 Build Installer - Linux DEB, 🏗️ Test Install Scripts, 🚨 pre-commit, 🚨 Check Dependency Artifacts)
strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

# Premium runners (macOS / Windows) (applies to: 🚨🚀 Lint and upload source distribution, 📦🚀 Build Installer - Windows 10, 🏗️ Test Install Scripts, 🚨 pre-commit, 🧪 test, 🚨 Check Dependency Artifacts, 📦🚀 Build Installers - MacOS)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# Third-party actions pinned to a mutable ref (applies to: 🚨🚀 Lint and upload source distribution)
uses: chia-network/actions/clean-workspace@<full-sha>  # was @main

# Full-history clone (fetch-depth: 0) (applies to: 📦🚀 Build Installer - Windows 10, 🚨 GitHub Super Linter, 📦🚀 Build Installer - Linux RPM AMD64, 📦🚀 Build Installer - Linux DEB, 🏗️ Test Install Scripts, 🚨 pre-commit, 🧪 test, ⚡️ Benchmarks, 📦🚀 Build Installers - MacOS, 🚨 Check commit signing, Dependency Cursor Review)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Third-party actions pinned to a mutable ref (applies to: 📦🚀 Build Installer - Windows 10)
uses: Chia-Network/actions/setjobenv@<full-sha>  # was @main

# No job timeout (applies to: 🚨 CodeQL, 🏗️ Test Install Scripts, 🧪 test, 📦🚀 Trigger Dev Docker Build, 🚨 Check Dependency Artifacts, 🩹 Conflict Check, 🚨 Dependency Review, 🚨 Check PR Labels)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Third-party actions pinned to a mutable ref (applies to: 📦🚀 Build Installer - Linux RPM AMD64)
uses: Chia-Network/actions/git-mark-workspace-safe@<full-sha>  # was @main

# Third-party actions pinned to a mutable ref (applies to: 📦🚀 Build Installer - Linux DEB, 🚨 pre-commit, ⚡️ Benchmarks, 🚨 Check Dependency Artifacts, 📦🚀 Build Installers - MacOS)
uses: Chia-Network/actions/clean-workspace@<full-sha>  # was @main

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

# Third-party actions pinned to a mutable ref (applies to: 🏗️ Test Install Scripts, 🧪 test)
uses: Chia-Network/actions/setup-python@<full-sha>  # was @main

# Scheduled at the top of the hour (applies to: 🧪 test)
on:
  schedule:
    - cron: '16 13 * * *'  # was '0 13 * * *' — any non-:00 minute avoids the herd

# Third-party actions pinned to a mutable ref (applies to: 📦🚀 Trigger Dev Docker Build)
uses: Chia-Network/actions/github/glue@<full-sha>  # was @main

# No path filters on triggers (applies to: 🩹 Conflict Check, 🚨 Check PR Labels)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Third-party actions pinned to a mutable ref (applies to: 🩹 Conflict Check)
uses: Chia-Network/actions/label-conflict@<full-sha>  # was @main

# Third-party actions pinned to a mutable ref (applies to: 🚨 Check commit signing)
uses: chia-network/actions/check-commit-signing@<full-sha>  # was @main

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/Chia-Network/chia-blockchain