2dust/v2rayn vs lorisyounger/vpet
Both showing Mixed signals — pick on fit, not health
As of September 2026, v2rayn and vpet both show mixed maintenance signals. v2rayn was committed to 1 week ago with 21+ active contributors, while vpet was committed to 1 week ago with 4+ active contributors. v2rayn is GPL-3.0-licensed while vpet is Apache-2.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.
2dust/v2rayn
Mixed signals — read the receipts
copyleft license (GPL-3.0) — review compatibility; no tests detected in the complete Git tree…
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; dependency CVE scan unavailable
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 1d ago
- ✓21+ active contributors
- ✓Distributed ownership (top contributor 32% of recent commits)
- ✓GPL-3.0 licensed
- ✓CI configured
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
lorisyounger/vpet
Mixed signals — read the receipts
no tests detected in the complete Git tree; no CI workflows detected…
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…
- ⚠Small team — 4 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 79% of recent commits
- ⚠No CI workflows detected
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓4 active contributors
- ✓Apache-2.0 licensed
What would improve this?
- •Use as dependency Mixed to Healthy if: add a test suite
- •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
| v2rayn | vpet | |
|---|---|---|
| Stars | 115,575 | 6,768 |
| Last commit | 10d ago | 11d ago |
| License | GPL-3.0 | Apache-2.0 |
| Open issues | 34 | 27 |
| Has tests | No | No |
| Has CI | ✓ | No |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? 2dust/v2rayn · lorisyounger/vpet
Ask AI about 2dust/v2rayn vs lorisyounger/vpet
Open the chat with a comparison question pre-filled.