RepoPilot

2dust/v2rayn vs microsoft/visualstudiouninstaller

Both showing Mixed signals — pick on fit, not health

As of September 2026, v2rayn and visualstudiouninstaller both show mixed maintenance signals. v2rayn was committed to 1 week ago with 21+ active contributors, while visualstudiouninstaller last saw a commit 7 years ago with 8+ active contributors. v2rayn is GPL-3.0-licensed while visualstudiouninstaller 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.

2dust/v2rayn

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; no tests detected in the complete Git tree…

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

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

microsoft/visualstudiouninstaller

Mixed

Stale — last commit 8y ago

MixedDependency

last commit was 8y ago; no tests detected in the complete Git tree…

MixedFork & modify

no tests detected in the complete Git tree; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 8y ago; Scorecard "Branch-Protection" is 0/10…

  • Stale — last commit 8y ago
  • Single-maintainer risk — top contributor 80% of recent commits
  • No CI workflows detected
  • No tests detected in the complete Git tree
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 8 active contributors
  • MIT licensed

What would improve this?

  • Use as dependency Mixed to Healthy if: 1 commit in the last 365 days; add a test suite
  • Fork & modify Mixed to Healthy if: add a test suite
  • Deploy as-is Mixed to 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

Signal-by-signal breakdown

v2raynvisualstudiouninstaller
Stars115,5753,963
Last commit11d ago7y ago
LicenseGPL-3.0MIT
Open issues3444
Has testsNoNo
Has CINo
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? 2dust/v2rayn · microsoft/visualstudiouninstaller

Ask AI about 2dust/v2rayn vs microsoft/visualstudiouninstaller

Open the chat with a comparison question pre-filled.