pomber/git-history vs vercel/next.js
vercel/next.js shows stronger signals overall
As of June 2026, next.js shows healthier maintenance signals than git-history. next.js rates Healthy overall while git-history rates Mixed. git-history last saw a commit 1 year ago with 7+ active contributors, while next.js was committed to today with 22+ active contributors. Both use the MIT license. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
pomber/git-history →
Stale — last commit 2y ago
last commit was 2y ago; top contributor handles 91% of recent commits
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Stale — last commit 2y ago
- ⚠Single-maintainer risk — top contributor 91% of recent commits
- ✓7 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
vercel/next.js →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; 2 cyclic import chains detected
- ✓In RepoPilot's curated trusted-corpus (29 projects)
- ✓Last commit today
- ✓22+ active contributors
- ✓Distributed ownership (top contributor 15% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: bring "Token-Permissions" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| git-history | next.js | |
|---|---|---|
| Stars | 13,687 | 140,248 |
| Last commit | 1y ago | today |
| License | MIT | MIT |
| Open issues | 94 | 4,153 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 9% | 4% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 2 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? pomber/git-history · vercel/next.js
Ask AI about pomber/git-history vs vercel/next.js
Open the chat with a comparison question pre-filled.