389ds/389-ds-base 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.

8 min/mo
recoverable · across 20 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 20 fixes, each with the exact YAML ↓
23.0%
failure rate, 30d
48m
avg time to recover from a failure
Since : findings 22 → 20 · recoverable ~0 → ~8 min/mo
13 workflows · 500 runs (16.7/day) · 16,835 CI-min (wall-clock) · ≈$101 at private-repo rates (30d)

Where the minutes go (30d)

Test~7,366 min · 64 runs
LMDB Test~6,149 min · 56 runs
Compile~1,008 min · 70 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · Backport

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

Artifacts at default retention · Compile

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

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 →

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Test

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

System packages reinstalled every run · Test

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

Scheduled at the top of the hour · npm-audit-ci

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

Full guide: how to fix this →

Scheduled workflow runs in forks · npm-audit-ci

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

Artifacts at default retention · LMDB 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 →

Scheduled at the top of the hour · LMDB 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: '25 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

Full guide: how to fix this →

Scheduled workflow runs in forks · LMDB Test

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

System packages reinstalled every run · LMDB Test

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

Scheduled at the top of the hour · Rust Tests

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Rust 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 →

Artifacts at default retention · CodeQL

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

Scheduled at the top of the hour · CodeQL

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

Full guide: how to fix this →

Scheduled workflow runs in forks · CodeQL

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

Scheduled workflow runs in forks · Nightly Dispatch

~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 · Backport

~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) · Backport

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

# Artifacts at default retention (applies to: Compile, Test, LMDB Test, CodeQL)
- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

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

# Scheduled workflow runs in forks (applies to: Test, npm-audit-ci, LMDB Test, Rust Tests, CodeQL, Nightly Dispatch)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

# Scheduled at the top of the hour (applies to: npm-audit-ci)
on:
  schedule:
    - cron: '54 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

# Scheduled at the top of the hour (applies to: LMDB Test)
on:
  schedule:
    - cron: '25 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

# Scheduled at the top of the hour (applies to: Rust Tests)
on:
  schedule:
    - cron: '46 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

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

# No job timeout (applies to: Backport)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

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

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/389ds/389-ds-base.svg)](https://gitspider.com/scan/389ds/389-ds-base)

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, every PR gets an automatic comment when its CI run fails or runs slow, 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/389ds/389-ds-base