mozilla/browserquest vs vercel/next.js
vercel/next.js shows stronger signals overall
As of June 2026, next.js shows healthier maintenance signals than browserquest. next.js rates Healthy overall while browserquest rates Mixed. browserquest last saw a commit 2 years ago with 4+ active contributors, while next.js was committed to today with 22+ active contributors. browserquest is Other-licensed while next.js is MIT-licensed. 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.
mozilla/browserquest →
Stale — last commit 3y ago
non-standard license (Other); last commit was 3y ago…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 3y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 3y ago
- ⚠Small team — 4 contributors active in recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠No CI workflows detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓4 active contributors
- ✓Distributed ownership (top contributor 47% of recent commits)
- ✓Other licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; bring "Branch-Protection" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
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
| browserquest | next.js | |
|---|---|---|
| Stars | 9,364 | 140,248 |
| Last commit | 2y ago | today |
| License | Other | MIT |
| Open issues | 0 | 4,153 |
| Has tests | ✓ | ✓ |
| Has CI | — | ✓ |
| Test coverage | 5% | 4% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 2 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? mozilla/browserquest · vercel/next.js
Ask AI about mozilla/browserquest vs vercel/next.js
Open the chat with a comparison question pre-filled.