RepoPilot

nickemanarin/screentogif vs studyzy/imewlconverter

Both showing Mixed signals — pick on fit, not health

As of September 2026, screentogif and imewlconverter both show mixed maintenance signals. screentogif last saw a commit 1 month ago with 13+ active contributors, while imewlconverter last saw a commit 1 month ago with 5+ active contributors. screentogif is MS-PL-licensed while imewlconverter 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.

nickemanarin/screentogif

Mixed

Mixed signals — read the receipts

ConcernsDependency

non-standard license (MS-PL); 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

  • Concentrated ownership — top contributor handles 66% of recent commits
  • Non-standard license (MS-PL) — review terms
  • No tests detected in the complete Git tree
  • Scorecard: default branch unprotected (0/10)
  • Last commit 5w ago
  • 13 active contributors
  • MS-PL licensed
  • CI configured

What would improve this?

  • Use as dependency Concerns to Mixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

studyzy/imewlconverter

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; dependency CVE scan unavailable

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; Scorecard "Token-Permissions" is 0/10…

  • Single-maintainer risk — top contributor 89% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit 4w ago
  • 5 active contributors
  • GPL-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 OpenSSF Scorecard

Signal-by-signal breakdown

screentogifimewlconverter
Stars27,59010,319
Last commit1mo ago1mo ago
LicenseMS-PLGPL-3.0
Open issues33188
Has testsNo
Has CI
Test coverage0%33%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? nickemanarin/screentogif · studyzy/imewlconverter

Ask AI about nickemanarin/screentogif vs studyzy/imewlconverter

Open the chat with a comparison question pre-filled.