clezcoding/claredtool 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 6 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 6 fixes, each with the exact YAML ↓
5.0%
failure rate, 30d
1h 23m
avg time to recover from a failure
Since : findings 7 → 6 · recoverable ~0 → ~0 min/mo
9 workflows · 159 runs (5.3/day) · 579 CI-min (wall-clock) · ≈$3 at private-repo rates (30d)

Where the minutes go (30d)

Dependabot Updates~226 min · 48 runs
ci~197 min · 35 runs
codeql~112 min · 11 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 →

Cache without restore-keys · ci

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

Scheduled workflow runs in forks · codeql

~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 path filters on triggers · gitleaks

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

Full-history clone (fetch-depth: 0) · gitleaks

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

Scheduled workflow runs in forks · zizmor

~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 (4 snippets, annotated per workflow)
# No path filters on triggers (applies to: ci, gitleaks)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

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

# Scheduled workflow runs in forks (applies to: codeql, zizmor)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

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

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, every PR gets an automatic comment when its CI run fails or runs slow, 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/clezcoding/claredtool