RepoPilot

microsoft/visualstudiouninstaller vs nickemanarin/screentogif

Both showing Mixed signals — pick on fit, not health

As of June 2026, visualstudiouninstaller and screentogif both show mixed maintenance signals. visualstudiouninstaller last saw a commit 7 years ago with 8+ active contributors, while screentogif last saw a commit 2 months ago with 13+ active contributors. visualstudiouninstaller is Other-licensed while screentogif is MS-PL-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.

microsoft/visualstudiouninstaller

Mixed

Stale — last commit 7y ago

ConcernsDependency

non-standard license (Other); last commit was 7y ago…

MixedFork & modify

no tests detected; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 7y ago; no CI workflows detected

  • Stale — last commit 7y ago
  • Single-maintainer risk — top contributor 80% of recent commits
  • Non-standard license (Other) — review terms
  • No CI workflows detected
  • No test directory detected
  • 8 active contributors
  • Other licensed

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms
  • Fork & modify MixedHealthy if: add a test suite
  • Deploy as-is MixedHealthy if: 1 commit in the last 180 days

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

nickemanarin/screentogif

Mixed

Mixed signals — read the receipts

ConcernsDependency

non-standard license (MS-PL)

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Concentrated ownership — top contributor handles 69% of recent commits
  • Non-standard license (MS-PL) — review terms
  • Last commit 2w ago
  • 13 active contributors
  • MS-PL licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

visualstudiouninstallerscreentogif
Stars3,96326,910
Last commit7y ago2mo ago
LicenseOtherMS-PL
Open issues44320
Has tests
Has CI
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? microsoft/visualstudiouninstaller · nickemanarin/screentogif

Ask AI about microsoft/visualstudiouninstaller vs nickemanarin/screentogif

Open the chat with a comparison question pre-filled.