grafana/pyroscope-rs 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.

201 min/mo
recoverable (~32% of CI time) · across 6 patterns · ≈$1/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 6 fixes, each with the exact YAML ↓
4.8%
failure rate, 30d
4m
avg time to recover from a failure
Since : findings 6 → 6 · recoverable ~197 → ~201 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
7 workflows · 186 runs (6.2/day) · 638 CI-min (wall-clock) · ≈$4 at private-repo rates (30d)

Where the minutes go (30d)

Rust~504 min · 51 runs
CodeQL~71 min · 42 runs
(deleted or unlisted workflow)~38 min · 41 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · Rust

~151 min/mo · ≈$1/mo

Add `Swatinem/rust-cache@v2` (the de-facto cargo cache), or an `actions/cache@v4` step keyed on `Cargo.lock`.

- uses: Swatinem/rust-cache@v2

Full guide: how to fix this →

No concurrency control · Rust

~50 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 · Rust

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

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

Docker build without layer cache · Rust

~0 min/mo

The Docker build has no layer cache, so every run re-executes every layer from scratch. Add `cache-from: type=gha` / `cache-to: type=gha,mode=max` to the build step.

- uses: docker/build-push-action@v6
  with:
    cache-from: type=gha
    cache-to: type=gha,mode=max

Full guide: how to fix this →

No job timeout · Release Please

~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 (5 snippets, annotated per workflow)
# Missing dependency cache (cargo) (applies to: Rust)
- uses: Swatinem/rust-cache@v2

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

# No job timeout (applies to: Rust, Release Please)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

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

# Docker build without layer cache (applies to: Rust)
- uses: docker/build-push-action@v6
  with:
    cache-from: type=gha
    cache-to: type=gha,mode=max

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/grafana/pyroscope-rs.svg)](https://gitspider.com/scan/grafana/pyroscope-rs)

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/grafana/pyroscope-rs