`pmndrs/jotai` GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated 9/28/2026, 5:40:41 AM UTC.

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

0 min/mo

recoverable · across 7 patterns

Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent

See all 7 fixes, each with the exact YAML ↓

10.1%

failure rate, 30d

14m

avg time to recover from a failure

10 workflows · 69 runs (2.3/day) · 91 CI-min (wall-clock) · ≈$1 at private-repo rates (30d)

Where the minutes go (30d)

Test Multiple Versions~19 min · 11 runs

Test Old TypeScript~18 min · 11 runs

Test~17 min · 11 runs

or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No job timeout · `Test Multiple Versions`

~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 · `Test Multiple Builds`

~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 · `Test Old TypeScript`

~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 · `Ecosystem 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 · `Test`

~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 · `Compressed Size`

~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 Release`

~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 (1 snippet, annotated per workflow)

# No job timeout (applies to: Test Multiple Versions, Test Multiple Builds, Test Old TypeScript, Ecosystem CI, Test, Compressed Size, Preview Release)
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](https://gitspider.com/badge/pmndrs/jotai.svg)](https://gitspider.com/scan/pmndrs/jotai)

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/pmndrs/jotai