repo-evallisted

# repo-eval Score a GitHub repo 0-100 on **momentum** (popularity trajectory) and **maintenance** (how well it is run), then drop it on a quadrant. Two axes decouple: a repo can be popular-but-abandoned or niche-but-impeccable. Read them together, never alone. - **Momentum** comes from the [OSS Insight API](https://ossinsight.io/docs/api) (no auth): stargazers history, issue/PR-creator history, org breakdown. - **Maintenance** comes from `gh` (your existing auth): time-to-first-response, time-to-merge, PR acceptance rate, issue half-life, open-PR backlog age, release cadence, self-merge rate, contributor concentration, CI. These are computed **month-by-month** over a ≥12-month window (`--months`, default 18) and fitted to a slope, so trends — not just current levels — drive the verdict (e.g. response time *creeping up* = dying, flat = mature). The script always prints the **raw metrics** beside the scores — the verdict is auditable, not a black box. See [REFERENCE.md](REFERENCE.md) for every metric definition, the scoring thresholds, and the gotchas (squash-merge, bot noise, mature-vs-dying). ## Quick start ```bash # Full evaluation (needs network for OSS Insight + an authenticated gh) python3 scripts/repo_eval.py vercel/next.js # One axis at a time python3 scripts/repo_eval.py vercel/next.js --momentum-only python3 scripts/repo_eval.py vercel/next.js --maintenance-only # Machine-readable (includes the per-month trend series under maintenance.monthly) python3