DFE-Digital/single-unique-identifier 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.

10 min/mo
recoverable (~2% of CI time) · across 22 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 22 fixes, each with the exact YAML ↓
4.3%
failure rate, 30d · Top 25%
7h 28m
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/DFE-Digital/single-unique-identifier.svg)](https://gitspider.com/scan/DFE-Digital/single-unique-identifier)
Since : findings 18 → 22 · recoverable ~8 → ~10 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
25 workflows · 253 runs (8.4/day) · 506 CI-min (wall-clock) · ≈$3 at private-repo rates (30d)

Where the minutes go (30d)

CodeQL~271 min · 42 runs
TruffleHog Secret Scan~73 min · 38 runs
Build, Test, Deploy: "Get An Identifier" Solution~63 min · 31 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · TruffleHog Secret Scan

~7 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 · Trivy Repository Scan

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

No concurrency control · Trivy IaC Scan

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

No concurrency control · TruffleHog Deep Secret Scan

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

No job timeout · Trivy Repository Scan

~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 · Trivy Repository Scan

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Trivy Repository Scan

~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 · TruffleHog Secret Scan

~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 · TruffleHog Secret Scan

~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) · TruffleHog Secret Scan

~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 · Trivy IaC Scan

~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 · Trivy IaC Scan

~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 job timeout · TruffleHog Deep Secret Scan

~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 workflow runs in forks · TruffleHog Deep Secret Scan

~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) · TruffleHog Deep Secret Scan

~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 · Rotate Key Vault Secret

~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 · Rotate Key Vault Secret

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Rotate Key Vault Secret

~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 · Build, Test, Deploy: "UI Test Harness" Solution

~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 · Build, Test, Deploy: "Auth Emulator" Solution

~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 · Build, Test, Deploy: "Get An Identifier" Solution

~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 · Terraform Get An Identifier

~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 (7 snippets, annotated per workflow)
# No concurrency control (applies to: TruffleHog Secret Scan, Trivy Repository Scan, Trivy IaC Scan, TruffleHog Deep Secret Scan)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: Trivy Repository Scan, TruffleHog Secret Scan, Trivy IaC Scan, TruffleHog Deep Secret Scan, Rotate Key Vault Secret, Build, Test, Deploy: "UI Test Harness" Solution, Build, Test, Deploy: "Auth Emulator" Solution, Build, Test, Deploy: "Get An Identifier" Solution, Terraform Get An Identifier)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled at the top of the hour (applies to: Trivy Repository Scan)
on:
  schedule:
    - cron: '27 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

# Scheduled workflow runs in forks (applies to: Trivy Repository Scan, TruffleHog Deep Secret Scan, Rotate Key Vault Secret)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# No path filters on triggers (applies to: TruffleHog Secret Scan, Trivy IaC Scan)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Full-history clone (fetch-depth: 0) (applies to: TruffleHog Secret Scan, TruffleHog Deep Secret Scan)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Scheduled at the top of the hour (applies to: Rotate Key Vault Secret)
on:
  schedule:
    - cron: '8 3 * * 1'  # was '0 3 * * 1' — any non-:00 minute avoids the herd

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/DFE-Digital/single-unique-identifier