GitSpider

square/retrofit 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.

121 min/mo
recoverable (~35% 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 ↓
25.6%
failure rate, 30d
8h 46m
avg time to recover from a failure
Since : findings 5 → 6 · recoverable ~29 → ~121 min/mo
5 workflows · 43 runs (1.4/day) · 346 CI-min (wall-clock) · ≈$2 at private-repo rates (30d)

Where the minutes go (30d)

build~302 min · 21 runs
CodeQL~43 min · 22 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · build

~91 min/mo · ≈$1/mo

Set `cache: 'gradle'` on your `actions/setup-java` step, or add an `actions/cache@v4` step keyed on your build file.

- uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '21'
    cache: 'gradle'

Full guide: how to fix this →

No concurrency control · build

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

Artifacts at default retention · build

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · build

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

Third-party actions pinned to a mutable ref · build

~0 min/mo

1 third-party action pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead. (6 more on a major-version tag like @v4; consider full-SHA pinning there too.)

uses: JamesIves/github-pages-deploy-action@<full-sha>  # was @releases/v3
Copy every fix as one block (6 snippets, annotated per workflow)
# Missing dependency cache (gradle) (applies to: build)
- uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '21'
    cache: 'gradle'

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

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

# Artifacts at default retention (applies to: build)
- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

# Premium runners (macOS / Windows) (applies to: build)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# Third-party actions pinned to a mutable ref (applies to: build)
uses: JamesIves/github-pages-deploy-action@<full-sha>  # was @releases/v3

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

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/square/retrofit