librespeed/speedtest vs vercel/next.js
Both showing Healthy signals — pick on fit, not health
As of September 2026, speedtest and next.js both show healthy maintenance signals. speedtest last saw a commit 1 month ago with 13+ active contributors, while next.js was committed to today with 25+ active contributors. speedtest is LGPL-3.0-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.
librespeed/speedtest
Strong maintenance signals
copyleft license (LGPL-3.0) — review compatibility
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠LGPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2w ago
- ✓13 active contributors
- ✓Distributed ownership (top contributor 37% of recent commits)
- ✓LGPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- •Deploy as-is Mixed to Healthy if: 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 dependency CVEs from deps.dev and OpenSSF Scorecard
vercel/next.js
Strong maintenance signals
dependency CVE scan unavailable
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; 8 cyclic import chains — pervasive coupling…
- ✓In RepoPilot's curated trusted-corpus (29 projects)
- ✓Last commit today
- ✓25+ active contributors
- ✓Distributed ownership (top contributor 16% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to 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 OpenSSF Scorecard
Signal-by-signal breakdown
| speedtest | next.js | |
|---|---|---|
| Stars | 15,108 | 142,360 |
| Last commit | 1mo ago | today |
| License | LGPL-3.0 | MIT |
| Open issues | 12 | 3,396 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 8 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? librespeed/speedtest · vercel/next.js
Ask AI about librespeed/speedtest vs vercel/next.js
Open the chat with a comparison question pre-filled.