EPFL-ENAC/co2-calculator 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.

76 min/mo
recoverable (~8% 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 ↓
1.8%
failure rate, 30d
8m
avg time to recover from a failure
Since : findings 18 → 22 · recoverable ~161 → ~76 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
26 workflows · 500 runs (16.7/day) · 959 CI-min (wall-clock) · ≈$6 at private-repo rates (30d)

Where the minutes go (30d)

Tests~210 min · 73 runs
CodeQL - Code Quality~166 min · 103 runs
Security Checks~147 min · 74 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · Tests

~21 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 · Security Checks

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

Docker build without layer cache · deploy-storybook

~14 min/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 · deploy

~12 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

Full guide: how to fix this →

No concurrency control · Quality Checks

~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 · deploy-storybook

~5 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

Full guide: how to fix this →

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

No job timeout · Append issue number to title

~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 · Auto-format i18n

~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 · deploy-mkdocs

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

cancel-in-progress on a deploy workflow · deploy-mkdocs

~0 min/mo

This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too, so a queued deploy is silently dropped when a newer run arrives. Use a group-only `concurrency:` block on deploys.

concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

Full guide: how to fix this →

No job timeout · deploy-storybook

~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 · deploy-storybook

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

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

~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 · Quality Checks

~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 · Quality Checks

~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 · Security Checks

~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 · Security Checks

~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 · Security Checks

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Security Checks

~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) · Security Checks

~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 path filters on triggers · Tests

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

Copy every fix as one block (9 snippets, annotated per workflow)
# No concurrency control (applies to: Tests, Security Checks, Quality Checks)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Docker build without layer cache (applies to: deploy-storybook)
- uses: docker/build-push-action@v6
  with:
    cache-from: type=gha
    cache-to: type=gha,mode=max

# No concurrency control (applies to: deploy, deploy-storybook)
concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

# No job timeout (applies to: Append issue number to title, Auto-format i18n, deploy-mkdocs, deploy-storybook, deploy, Quality Checks, Security Checks)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# cancel-in-progress on a deploy workflow (applies to: deploy-mkdocs)
concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

# No path filters on triggers (applies to: deploy-storybook, deploy, Quality Checks, Security Checks, Tests)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

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

# Scheduled workflow runs in forks (applies to: Security Checks)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Full-history clone (fetch-depth: 0) (applies to: Security Checks)
- 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/EPFL-ENAC/co2-calculator.svg)](https://gitspider.com/scan/EPFL-ENAC/co2-calculator)

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/EPFL-ENAC/co2-calculator