GitSpider

nestjs/nest 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.

40 min/mo
recoverable (~6% of CI time) · across 5 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 5 fixes, each with the exact YAML ↓
5.0%
failure rate, 30d
3h 43m
avg time to recover from a failure
Since : findings 5 → 5 · recoverable ~38 → ~40 min/mo
6 workflows · 500 runs (16.7/day) · 717 CI-min (wall-clock) · ≈$4 at private-repo rates (30d)

Where the minutes go (30d)

CodeQL~400 min · 233 runs
CodeQL~186 min · 183 runs
Dependabot Updates~92 min · 73 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · CodeQL

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

No job timeout · CodeQL

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

~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 · 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 17 * * 4'  # was '0 17 * * 4' — 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 →

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

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

# No path filters on triggers (applies to: CodeQL)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

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

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

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/nestjs/nest.svg)](https://gitspider.com/scan/nestjs/nest)

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/nestjs/nest