RepoHeath - Real-Time GitHub Repo Health Dashboard for Maintainers

One-click GitHub repo audit that flags stale dependencies, inactive maintainers, security vulnerabilities, and engagement decay — then sends you a Slack alert when red flags spike. No more surprise abandonware.

𝕏 Post Reddit HN

Difficulty

low-code

What is it?

Open source maintainers spend hours manually checking if their repos are healthy: are dependencies current, is the community still engaged, are critical issues aging, are PRs stalling. RepoHealth aggregates GitHub API data (commits, issues, PRs, releases, contributor velocity) plus Dependabot/security alerts into a single dashboard with trend lines and alerts. The core insight is that maintainers want ONE metric that says 'your repo is degrading' without false alarms. Built as a 5-minute GitHub OAuth setup, then automatic weekly scans, with Slack/email alerts when metrics drop below custom thresholds. Why 100% buildable right now: GitHub GraphQL API is mature and free-tier friendly, Slack incoming webhooks are rock-solid, Supabase RLS handles per-user data perfectly, and the entire MVP (repo sync, metric calculation, alerting) can be built with Next.js + Claude for data aggregation logic in 2 weeks flat.

Why now?

GitHub's GraphQL API matured significantly in 2024–2025; Slack alerting is now industry standard for developer workflows; maintainer burnout is peak conversation on Twitter/X right now.

▸GitHub OAuth login with automatic repo detection (Implementation: use GitHub GraphQL to fetch repos, store in Supabase with RLS)
▸Metric sync engine that fetches commits, PR velocity, issue age, contributor count weekly (Implementation: cron job via Vercel, Claude for anomaly detection)
▸Dashboard with trend charts and red/yellow/green status (Implementation: Recharts + Tailwind)
▸Slack alert rules (e.g., 'alert if commit frequency drops 30% week-over-week') (Implementation: Slack incoming webhooks triggered by metric thresholds)
▸Email digest summarizing top issues (Implementation: Resend email templates, scheduled via cron)

Target Audience

2,000+ active open source maintainers on GitHub managing 10+ star repos, especially those with 5+ active contributors.

Example Use Case

Maya, maintainer of a 15k-star React library, sets up RepoHealth in 5 minutes. Three weeks later, an alert fires: PR response time jumped from 2 days to 8 days, commit frequency dropped 40%, and open issues aged past 30 days. She spots that her co-maintainer went silent and adjusts the team structure. Without RepoHealth, she would have noticed only when the community complained.

User Stories

▸As an open source maintainer, I want to see if my repo health is degrading, so that I can catch contributor churn or dependency debt before it becomes a crisis.
▸As a maintainer, I want Slack alerts when PR response time spikes, so that I stay on top of community engagement without manually checking GitHub daily.
▸As a maintainer, I want to compare my repo's metrics to historical trends, so that I know if we're improving or declining.

Acceptance Criteria

GitHub OAuth: done when user can log in, grant repo access, and repo list populates. Metric Sync: done when metrics fetch weekly without errors and store in Postgres. Dashboard: done when repo cards load in under 2 seconds and trend charts render. Slack Alert: done when Slack webhook fires when a custom threshold is breached and message includes repo name and metric delta.

Is it worth building?

$9/month × 150 paying maintainers = $1,350 MRR at month 3. $29/month × 200 power users = $5,800 MRR at month 6.

Unit Economics

CAC: $0 (organic ProductHunt + Twitter). LTV: $108 (12 months at $9/month). Payback: immediate (no acquisition cost). Gross margin: 85% (minimal hosting overhead).

Business Model

SaaS subscription with free tier (1 repo monitored).

Monetization Path

Free tier (1 repo, weekly digest). $9/month (5 repos, daily alerts, Slack integration). $29/month (unlimited repos, custom thresholds, team access).

Revenue Timeline

First dollar: week 3. $1k MRR: month 3. $5k MRR: month 7.

Estimated Monthly Cost

GitHub GraphQL API: free tier covers 5,000 calls/hr. Slack: free tier. Vercel: $20. Supabase: $25. Stripe fees: ~$15. Resend: $20. Total: ~$80/month.

Profit Potential

Sustainable at $3k–$8k MRR; niche but loyal customer base.

Scalability

High — can expand to GitHub org audits, metric benchmarking, and comparative health scoring across open source ecosystems.

Success Metrics

Week 1: 200 signups via ProductHunt. Week 2: 15 paid. Month 2: 45 paying users, 70% retention.

Launch & Validation Plan

Survey 30 maintainers on Twitter/X (ask 'what repo metric keeps you up at night'), interview 5 in detail, build landing page with GitHub OAuth demo, recruit 8 beta testers, and validate that Slack alerts fire correctly.

Customer Acquisition Strategy

First customer: post on r/golang, r/rust, r/Python with a free setup offer and free access. Then: ProductHunt launch, tweet results, GitHub topics targeting, sponsorship of popular open source projects.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): GitHub OAuth, weekly metric sync, basic dashboard, Slack alerts. V2 (week 3-4): custom threshold rules, email digest, multiple repos, historical trend comparison. V3 (month 2+): team accounts, GitHub org scanning, benchmarking dashboard, Dependabot integration.

Milestone Plan

Phase 1 (Week 1–2): GitHub OAuth working, repo auto-detect, metric sync cron job running, Supabase RLS configured. Done when 10 test repos auto-populate metrics. Phase 2 (Week 3–4): dashboard UI complete, Slack webhook tested, Stripe subscription flow live. Done when beta users can create custom alerts and receive Slack notifications. Phase 3 (Month 2): email digest working, multiple repo support, public landing page optimized, ProductHunt launch prep. Done when 5+ beta users opt for paid plan.

How do you build it?

Tech Stack

Next.js, GitHub GraphQL API, Supabase, Slack API, Stripe, Resend — build with Cursor for backend logic, Lovable for dashboard UI, v0 for cards/charts.

Time to Ship

2 weeks

Required Skills

GitHub GraphQL, Slack bot setup, basic Next.js dashboard.

Resources

GitHub GraphQL explorer, Slack API docs, Supabase quickstart, Next.js Chart.js integration.

MVP Scope

Pages: /login (GitHub OAuth), /dashboard (repo list + health cards), /repo/[id] (detail page with charts), /settings (alert rules). API routes: /api/github-sync, /api/metrics, /api/slack-webhook. Supabase tables: users, repos, metrics, alerts. Components: RepoCard, TrendChart, AlertForm, SlackConfig.

Core User Journey

GitHub OAuth login -> repo auto-discovered -> first metric dashboard loads in 30 seconds -> receives first Slack alert within 7 days -> upgrades to paid plan.

Architecture Pattern

GitHub OAuth -> token stored in Supabase -> cron job queries GraphQL API every 7 days -> metrics calculated and stored -> anomaly detector runs -> Slack webhook fired if threshold exceeded -> email digest sent via Resend.

Data Model

User has many Repos. Repo has many Metrics (one per week). Repo has many Alerts. Alert has AlertRules.

Integration Points

GitHub GraphQL API for repo data and commit history, Slack API for incoming webhooks and alerts, Stripe for payments, Resend for email digests, Supabase for data persistence.

V1 Scope Boundaries

V1 excludes: team collaboration features, GitHub org-wide scanning, comparative benchmarking against other repos, mobile app, third-party data sources (Snyk, etc).

Success Definition

An open source maintainer finds the product on ProductHunt, sets it up without contacting founder, receives a Slack alert that changes a decision, and pays for month two.

Challenges

GitHub API rate limits (60 reqs/hr on personal tokens) require smart batching. False positives in anomaly detection annoy users fast.

Avoid These Pitfalls

Do not attempt real-time metric calculation — weekly snapshots are enough and save API quota. Do not add GitHub org management until paying customers demand it. Do not over-engineer anomaly detection; simple percent-change thresholds with user customization beat complex ML.

Security Requirements

Auth: Supabase Auth with GitHub OAuth. RLS: all user-level tables have row-level security enabling users to see only their own repos and metrics. Rate limiting: 10 req/min per GitHub API call via Vercel middleware. Input validation: repo names and alert thresholds validated before storage. GDPR: data deletion endpoint removes all user repos and metrics upon request.

Infrastructure Plan

Hosting: Vercel (frontend + API routes). Database: Supabase (Postgres). CI/CD: GitHub Actions. Cron jobs: Vercel Functions (weekly metric sync). Environments: dev (localhost), staging (Vercel preview branch), prod (main branch). Monitoring: Sentry for errors, Vercel Analytics for page load times. Cost breakdown: Vercel $20, Supabase $25, Resend $20, Sentry $29. Total: ~$94/month.

Performance Targets

Expected DAU at launch: 50. Requests per day: 300. API response time: under 800ms (GitHub GraphQL calls are slower). Dashboard page load: under 2.5s (LCP). Caching: CDN for static assets, Supabase query caching for metrics within 24h.

Go-Live Checklist

☐Security audit: GitHub OAuth token handling reviewed
☐Payment: Stripe webhook tested, subscription created
☐Errors: Sentry configured and tested
☐Monitoring: Vercel Analytics dashboard active
☐Domain: custom domain registered and SSL live
☐Legal: privacy policy and terms published
☐Beta: 8 users tested and signed off
☐Rollback: previous Vercel deployment preserved
☐Launch: ProductHunt post queued, Twitter/X thread drafted, r/golang/r/rust/r/python posts ready.

How to build it, step by step

1. npx create-next-app repohealth. 2. npm install @supabase/supabase-js stripe resend @slack/web-api recharts. 3. Set up Supabase tables (users, repos, metrics, alerts). 4. Build GitHub OAuth flow with Supabase Auth. 5. Create /api/github-sync endpoint to fetch repo data via GraphQL. 6. Build /dashboard page with RepoCard component. 7. Add Slack webhook handler and AlertRules UI. 8. Create cron job via Vercel Functions to run metric sync weekly. 9. Add Stripe checkout flow. 10. Deploy to Vercel and test end-to-end.

Generated

March 25, 2026

Model

claude-haiku-4-5-20251001

← Back to All Ideas