RepoPilot

dapperlib/dapper vs shadowsocks/shadowsocks-windows

Both showing Mixed signals — pick on fit, not health

As of September 2026, dapper and shadowsocks-windows both show mixed maintenance signals. dapper was committed to 3 weeks ago with 26+ active contributors, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. 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.

dapperlib/dapper

Mixed

Evidence incomplete — review before adopting

MixedDependency

license evidence incomplete; dependency CVE scan unavailable

MixedFork & modify

license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; license evidence incomplete…

  • Concentrated ownership — top contributor handles 67% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Could not verify license from the available repository evidence
  • Last commit 2w ago
  • 26+ active contributors
  • CI configured
  • Tests present

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

shadowsocks/shadowsocks-windows

Mixed

Stale — last commit 2y ago

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; last commit was 2y ago…

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

last commit was 2y ago; Scorecard "Branch-Protection" is 1/10…

  • Stale — last commit 2y ago
  • GPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (1/10)
  • 11 active contributors
  • Distributed ownership (top contributor 44% of recent commits)
  • 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: 1 commit in the last 180 days

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

Signal-by-signal breakdown

dappershadowsocks-windows
Stars18,37559,569
Last commit27d ago1y ago
LicenseUnknownGPL-3.0
Open issues546203
Has tests
Has CI
Test coverage58%9%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? dapperlib/dapper · shadowsocks/shadowsocks-windows

Ask AI about dapperlib/dapper vs shadowsocks/shadowsocks-windows

Open the chat with a comparison question pre-filled.