C360Studio/semstreams 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.

873 min/mo
recoverable (~27% of CI time) · across 7 patterns · ≈$5/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 7 fixes, each with the exact YAML ↓
7.2%
failure rate, 30d · Above average
32m
avg time to recover from a failure
🕸️ Reliability: Above averageFailure rate beats ~59% of the 19 repos GitSpider watches.
Since : findings 6 → 7 · recoverable ~353 → ~873 min/mo
6 workflows · 500 runs (16.7/day) · 3,260 CI-min (wall-clock) · ≈$20 at private-repo rates (30d)

Where the minutes go (30d)

CI~1,944 min · 248 runs
Container Build~956 min · 94 runs
E2E Ladder~356 min · 156 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · CI

~583 min/mo · ≈$4/mo

`actions/setup-go@v4+` caches modules and build output by default, so upgrading to v4 or newer is the fix.

# actions/setup-go@v4+ caches modules and build output by default;
# upgrading to v4 or newer is the fix.
- uses: actions/setup-go@v5
  with:
    go-version: '1.22'

Full guide: how to fix this →

No concurrency control · CI

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

Full guide: how to fix this →

No concurrency control · Container Build

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

Full guide: how to fix this →

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

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 →

No job timeout · Container Build

~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 · Container Build

~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 · E2E Ladder

~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 (4 snippets, annotated per workflow)
# Missing dependency cache (go) (applies to: CI)
# actions/setup-go@v4+ caches modules and build output by default;
# upgrading to v4 or newer is the fix.
- uses: actions/setup-go@v5
  with:
    go-version: '1.22'

# No concurrency control (applies to: CI, Container Build)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No path filters on triggers (applies to: CI, Container Build, E2E Ladder)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

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

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

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/C360Studio/semstreams