RepoPilot

kerryjiang/supersocket vs studyzy/imewlconverter

kerryjiang/supersocket shows stronger signals overall

As of September 2026, supersocket shows healthier maintenance signals than imewlconverter. supersocket rates Healthy overall while imewlconverter rates Mixed. supersocket last saw a commit 5 months ago with 3+ active contributors, while imewlconverter last saw a commit 1 month ago with 5+ active contributors. supersocket is Apache-2.0-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.

kerryjiang/supersocket

Healthy

Healthy across all four use cases

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Slowing — last commit 5mo ago
  • Small team — 3 contributors active in recent commits
  • Single-maintainer risk — top contributor 93% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 5mo ago
  • 3 active contributors
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and 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

supersocketimewlconverter
Stars4,23210,319
Last commit5mo ago1mo ago
LicenseApache-2.0GPL-3.0
Open issues21188
Has tests
Has CI
Test coverage22%33%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineHealthy signalsMixed signals

Want the full analysis? kerryjiang/supersocket · studyzy/imewlconverter

Ask AI about kerryjiang/supersocket vs studyzy/imewlconverter

Open the chat with a comparison question pre-filled.