GitSpider

jrl-umi3218/mc_rtc GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated 6/30/2026, 4:40:14 AM.

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

6,425 min/mo
recoverable (~50% of CI time) · across 14 patterns · ≈$39/mo
Rough estimate from wall-clock run time at standard Linux pricing. Matrix/parallel jobs and your actual runners will differ.
25.1%
failure rate, 30d
10h 43m
avg time to recover from a failure
9 workflows · 251 runs (8.4/day) · 12,850 CI-min (wall-clock) · ≈$77 at paid-Linux rates (30d)

Waste detected

Biggest wins first, each with the exact config fix.

Workflow runs on both push and pull_request · Package mc_rtc

~2650 min/mo · ≈$16/mo

Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.

on:
  push:
    branches: [main]
  pull_request:

Workflow runs on both push and pull_request · CI of mc_rtc

~1602 min/mo · ≈$10/mo

Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.

on:
  push:
    branches: [main]
  pull_request:

Missing dependency cache · CI of mc_rtc

~1136 min/mo · ≈$7/mo

Set `cache: 'npm'` (or `'pip'`, `'yarn'`, etc.) on your setup-* action, or add `actions/cache@v4` for the install dir.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

No concurrency control · Package mc_rtc

~749 min/mo · ≈$4/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

No concurrency control · CI of mc_rtc

~379 min/mo · ≈$2/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

Workflow runs on both push and pull_request · CI - Nix

~241 min/mo · ≈$1/mo

Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.

on:
  push:
    branches: [main]
  pull_request:

No concurrency control · CI - Nix

~145 min/mo · ≈$1/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

No job timeout · CI of mc_rtc

~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

Premium runners (macOS / Windows) · CI of mc_rtc

~0 min/mo

macOS bills ~10× and Windows ~2× 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

No job timeout · CI - Nix

~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

No path filters on triggers · CI - Nix

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

Premium runners (macOS / Windows) · CI - Nix

~0 min/mo

macOS bills ~10× and Windows ~2× 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

No job timeout · Package mc_rtc

~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

No job timeout · Sync with GitLab

~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

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 →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/jrl-umi3218/mc_rtc
Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/jrl-umi3218/mc_rtc.svg)](https://gitspider.com/scan/jrl-umi3218/mc_rtc)