torvalds/linux vs v-lavrenko/yari
Both showing Mixed signals — pick on fit, not health
As of September 2026, linux and yari both show mixed maintenance signals. linux was committed to today with 33+ active contributors, while yari last saw a commit 6 months ago with 1+ active contributor. linux is GPL-2.0-licensed while yari is GPL-3.0-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.
torvalds/linux
Evidence incomplete — review before adopting
copyleft license (GPL-2.0) — review compatibility; CI evidence incomplete…
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; CI evidence incomplete…
- ⚠GPL-2.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠Could not verify CI from the available repository evidence
- ✓Last commit today
- ✓33+ active contributors
- ✓Distributed ownership (top contributor 41% of recent commits)
- ✓GPL-2.0 licensed
- ✓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 OpenSSF Scorecard
v-lavrenko/yari
Slowing — last commit 6mo ago
copyleft license (GPL-3.0) — review compatibility; single-maintainer (no co-maintainers visible)…
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; no CI workflows detected…
- ⚠Slowing — last commit 6mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6mo ago
- ✓GPL-3.0 licensed
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 OpenSSF Scorecard
Signal-by-signal breakdown
| linux | yari | |
|---|---|---|
| Stars | 249,287 | 8 |
| Last commit | today | 6mo ago |
| License | GPL-2.0 | GPL-3.0 |
| Open issues | 3 | 0 |
| Has tests | ✓ | No |
| Has CI | Unknown | No |
| Test coverage | — | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? torvalds/linux · v-lavrenko/yari
Ask AI about torvalds/linux vs v-lavrenko/yari
Open the chat with a comparison question pre-filled.