fork-health-score

Calculate a GitHub fork health score by aggregating push recency, enabled skill count, and 30-day PR throughput into a unified 0–100 metric. This synthesizes multiple repository signals into a single score to quickly gauge fork activity and overall fleet health.

Fork health monitoring handles inactive repositories by bucketing them into STALE or QUIET tiers based on PR throughput and push recency. It excludes bot accounts from the audit to ensure the generated fleet leaderboard reflects genuine human developer activity.

Yes, you can audit fork activity using live GitHub API calls when fresh cohort data is unavailable. The audit automatically falls back to live API requests to retrieve push recency and PR throughput, ensuring the fork health score remains accurate and up-to-date.

The best way to rank active forks is generating a top-10 ACTIVE leaderboard using the computed 0–100 health score. This approach applies cohort data to bucket forks into ACTIVE, WARM, STALE, or QUIET tiers, providing operators clear visibility into fleet health.

Generate a weekly fork health leaderboard by running the audit to compute per-fork scores and update state files. This outputs a leaderboard article and per-fork breakdown for auditing, trend analysis, and drift detection across the repository fleet.