kompiro/karasu 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.

2 min/mo
recoverable (~1% of CI time) · across 18 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 18 fixes, each with the exact YAML ↓
0.4%
failure rate, 30d
0m
avg time to recover from a failure
24 workflows · 500 runs (16.7/day) · 373 CI-min (wall-clock) · ≈$2 at private-repo rates (30d)

Where the minutes go (30d)

E2E~102 min · 15 runs
CI~88 min · 51 runs
VS Code E2E~27 min · 17 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Concurrency without cancel-in-progress · Pages

~2 min/mo

Concurrency group has no `cancel-in-progress: true`, so superseded runs queue instead of cancelling. Add it to supersede stale runs.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

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

No job timeout · ADR validate (skip)

~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 · ADR validate

~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 · AT coverage 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 job timeout · CI (docs-only)

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

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 →

cancel-in-progress on a deploy workflow · Deploy

~0 min/mo

This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too — 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 · E2E (skip)

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

Cache without restore-keys · E2E

~0 min/mo

The cache restores only on an exact key match, so any lockfile change means a full cold download. Add a `restore-keys:` prefix line for partial restores.

    key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
    restore-keys: |
      deps-${{ runner.os }}-

Full guide: how to fix this →

No job timeout · Pages

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

~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 · Reference docs check (skip)

~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 · Reference docs 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 job timeout · Secret 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 · Secret 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 workflow runs in forks · Secret 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 →

No job timeout · TPL validate

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

Copy every fix as one block (6 snippets, annotated per workflow)
# Concurrency without cancel-in-progress — applies to: Pages
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout — applies to: ADR validate (skip), ADR validate, AT coverage check, CI (docs-only), CI, Deploy, E2E (skip), Pages, Preview, Reference docs check (skip), Reference docs check, Secret Scan, TPL validate
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

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

# Cache without restore-keys — applies to: E2E
    key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
    restore-keys: |
      deps-${{ runner.os }}-

# No path filters on triggers — applies to: Secret Scan
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Scheduled workflow runs in forks — applies to: Secret Scan
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.

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/kompiro/karasu
Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/kompiro/karasu.svg)](https://gitspider.com/scan/kompiro/karasu)