JovieInc/Jovie 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.

0 min/mo
recoverable · across 21 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 21 fixes, each with the exact YAML ↓
5.4%
failure rate, 30d · Above average
0m
avg time to recover from a failure
🕸️ Reliability: Above averageFailure rate beats ~63% of the 19 repos GitSpider watches.
Since : findings 24 → 21 · recoverable ~7 → ~0 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
96 workflows · 500 runs (16.7/day) · 645 CI-min (wall-clock) · ≈$4 at private-repo rates (30d)

Where the minutes go (30d)

CI~289 min · 43 runs
Merge Queue Auto-Enroll~90 min · 64 runs
Production Controller~76 min · 5 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No path filters on triggers · CI

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

Tests wrapped in auto-retry · CI

~0 min/mo

Tests run under an auto-retry wrapper, so each retry re-bills the same minutes and masks the flaky tests it papers over. Track, fix or quarantine the flakes, then drop the wrapper.

Full guide: how to fix this →

environment: on a CI job · CI

~0 min/mo

A test/build job is bound to a GitHub environment, so every run counts as a deployment: PR and deployments-API noise. Use repository secrets or OIDC for non-deploy jobs.

Full guide: how to fix this →

No job timeout · Dependabot Auto-Merge

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

Premium runners (macOS / Windows) · CodeQL Security Analysis

~0 min/mo

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

Full guide: how to fix this →

Scheduled workflow runs in forks · CodeQL Security Analysis

~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 · Claude Code

~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) · Claude Code

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

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

~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 · Fork PR Gate

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

Missing dependency cache · desktop-release

~0 min/mo

Set `cache: 'pnpm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

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

Full guide: how to fix this →

Premium runners (macOS / Windows) · desktop-release

~0 min/mo

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

Full guide: how to fix this →

Premium runners (macOS / Windows) · iOS TestFlight

~0 min/mo

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

Full guide: how to fix this →

No path filters on triggers · PR Size Guard

~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 path filters on triggers · Merge Queue Auto-Enroll

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

Frequent scheduled runs · Runner Heartbeat

~0 min/mo

A schedule cron fires >4x/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.

on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

Full guide: how to fix this →

Scheduled workflow runs in forks · Runner Heartbeat

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

cancel-in-progress on a deploy workflow · Post-Deploy Probes

~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 path filters on triggers · Fleet Gate Refresh

~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 workflow runs in forks · Delivery Control Receipts

~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 (8 snippets, annotated per workflow)
# No path filters on triggers (applies to: CI, Fork PR Gate, PR Size Guard, Merge Queue Auto-Enroll, Fleet Gate Refresh)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# No job timeout (applies to: Dependabot Auto-Merge, Claude Code, Security Scanning)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Premium runners (macOS / Windows) (applies to: CodeQL Security Analysis, desktop-release, iOS TestFlight)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# Scheduled workflow runs in forks (applies to: CodeQL Security Analysis, Runner Heartbeat, Delivery Control Receipts)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

# Missing dependency cache (pnpm) (applies to: desktop-release)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

# Frequent scheduled runs (applies to: Runner Heartbeat)
on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

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

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

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/JovieInc/Jovie