Free CI/CD health check for GitHub Actions
Your CI is slower than it needs to be. Find out why in 60 seconds.
Paste a public GitHub repo. DevRescue checks your workflows and code for missing caches, runaway jobs, wasted runs and leaked secrets, and tells you exactly what to change.
We scanned the CI of 139 popular JS/TS repos.
Only 1 passed all three basic checks.
- PR workflows that keep running outdated builds after a new push
- 75%
- CI jobs with no timeout (GitHub’s default is 6 hours)
- 61%
- Repos re-downloading every dependency in at least one CI workflow
- 34%
Sample: most-starred repos with 1k–20k stars, active since Sept 2026, analyzed 2026-11-02. Method and raw data.
What it checks
CI/CD
- ✓ Dependency cache (npm, yarn, pnpm, bun)
- ✓ Concurrency on pull requests
- ✓ Job timeouts
Security
- ✓ Leaked AWS, GitHub, Slack, Stripe keys
- ✓ Private keys and hardcoded passwords
- ✓ SQL injection, XSS and eval patterns
Performance
- ✓ Missing React keys
- ✓ Whole-library imports (lodash, moment…)
- ✓ Inline objects and handlers
DevOps Speed-Boost Kit
Every finding comes with the fix.
The audit tells you what’s wrong. The Kit is the paste-ready fix for each problem, plus a CLI that keeps it from coming back.
- Health Check CLI — Scans your project locally (private repos too) and fails CI when the score drops. Zero dependencies.
- Optimized Node.js CI — Dependency cache, cancel-outdated-runs, timeouts, skip on docs-only changes. Copy, paste, push.
- actions/cache recipes — For monorepos, custom installs and node_modules caching.
- Next.js build cache — Stop cold `next build` on every run.
- Sharded test suite — Split slow Jest / Vitest / Playwright suites across 4 parallel runners.
- Emergency runbook — The 10 most common causes of slow or broken deploys, each with a 5-minute fix.
Instant download. Works with npm, yarn, pnpm and bun.
Get the Kit30-day money-back guarantee
FAQ
›Do you store my code?
No. For a repo audit we fetch the public files, analyze them in memory and discard them. Nothing is saved. The Kit CLI runs entirely on your machine.
›Can I audit a private repo?
Not on the website. Use the Health Check CLI from the Kit: it runs locally on any project, private or not.
›npm, yarn, pnpm, bun?
All four. The engine also knows when actions/setup-node already caches npm for you, so it won’t nag you about it.
›Is this a security audit?
No. It’s fast automated triage for CI/CD, leaked secrets and common performance mistakes. It can miss things, and it’s not a substitute for a professional audit or pentest.
›What if the Kit doesn’t help?
Email us within 30 days for a full refund. No questions asked.