open-edge-platform/edge-ai-suites 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.

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

Where the minutes go (30d)

Documentation Check~613 min · 154 runs
Zizmor scan~415 min · 125 runs
[HLS - Multi Modal Patient Monitoring] SDLe Scans~316 min · 6 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Docker build without layer cache · [HLS - Multi Modal Patient Monitoring] SDLe Scans

~95 min/mo · ≈$1/mo

The Docker build has no layer cache, so every run re-executes every layer from scratch. Add `cache-from: type=gha` / `cache-to: type=gha,mode=max` to the build step.

- uses: docker/build-push-action@v6
  with:
    cache-from: type=gha
    cache-to: type=gha,mode=max

Full guide: how to fix this →

No concurrency control · Documentation Check

~61 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 · Zizmor scan

~41 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 · Skill Scanner

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

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

No job timeout · [HLS - Multi Modal Patient Monitoring] SDLe Scans

~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 · [HLS - Multi Modal Patient Monitoring] SDLe Scans

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

Larger hosted runner · [HLS - Multi Modal Patient Monitoring] SDLe Scans

~0 min/mo

Uses a larger hosted runner, which bills even on public repos (only standard runners are free). Keep big runners for jobs that measurably need the cores.

jobs:
  lint:
    runs-on: ubuntu-latest  # standard runner — free on public repos

Full guide: how to fix this →

No job timeout · Documentation 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 · Documentation 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 job timeout · Education-Suite-CI

~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 · Education-Suite-CI

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

No job timeout · FedAero-Suite-CI

~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 · FedAero-Suite-CI

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

System packages reinstalled every run · FedAero-Suite-CI

~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 · [FedAero] Package

~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 · [FedAero] Package

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

No job timeout · [Industrial Edge Insights Time Series and Multimodal] PR workflow

~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 · [metro-vision-ai-app-recipe] PR workflow

~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 · [metro-vision-ai-app-recipe] PR workflow

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

System packages reinstalled every run · [metro-vision-ai-app-recipe] PR workflow

~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 · [Robotics] CI

~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 · Skill Scanner

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Skill Scanner

~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) · Skill Scanner

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

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

Full guide: how to fix this →

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

Copy every fix as one block (11 snippets, annotated per workflow)
# Docker build without layer cache (applies to: [HLS - Multi Modal Patient Monitoring] SDLe Scans)
- uses: docker/build-push-action@v6
  with:
    cache-from: type=gha
    cache-to: type=gha,mode=max

# No concurrency control (applies to: Documentation Check, Zizmor scan, Skill Scanner)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: [HLS - Multi Modal Patient Monitoring] SDLe Scans, Documentation Check, Education-Suite-CI, FedAero-Suite-CI, [FedAero] Package, [Industrial Edge Insights Time Series and Multimodal] PR workflow, [metro-vision-ai-app-recipe] PR workflow, [Robotics] CI, Zizmor scan)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Artifacts at default retention (applies to: [HLS - Multi Modal Patient Monitoring] SDLe Scans, Education-Suite-CI, FedAero-Suite-CI, [FedAero] Package, [metro-vision-ai-app-recipe] PR workflow)
- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

# Larger hosted runner (applies to: [HLS - Multi Modal Patient Monitoring] SDLe Scans)
jobs:
  lint:
    runs-on: ubuntu-latest  # standard runner — free on public repos

# No path filters on triggers (applies to: Documentation Check, Zizmor scan)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# System packages reinstalled every run (applies to: FedAero-Suite-CI, [metro-vision-ai-app-recipe] PR workflow)
- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

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

# Scheduled workflow runs in forks (applies to: Skill Scanner, Zizmor scan)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

# Scheduled at the top of the hour (applies to: Zizmor scan)
on:
  schedule:
    - cron: '46 2 * * *'  # was '0 2 * * *' — 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/open-edge-platform/edge-ai-suites.svg)](https://gitspider.com/scan/open-edge-platform/edge-ai-suites)

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/open-edge-platform/edge-ai-suites