RepoPilot

nuke-build/nuke vs shadowsocks/shadowsocks-windows

nuke-build/nuke shows stronger signals overall

As of June 2026, nuke shows healthier maintenance signals than shadowsocks-windows. nuke rates Healthy overall while shadowsocks-windows rates Mixed. nuke last saw a commit 6 months ago with 6+ active contributors, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. nuke is MIT-licensed while shadowsocks-windows is Other-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.

nuke-build/nuke

Healthy

Healthy across all four use cases

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

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.

  • Slowing — last commit 5mo ago
  • Single-maintainer risk — top contributor 93% of recent commits
  • Last commit 5mo ago
  • 6 active contributors
  • MIT licensed
  • CI configured
  • Tests present

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

shadowsocks/shadowsocks-windows

Mixed

Stale — last commit 1y ago

ConcernsDependency

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

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.

MixedDeploy as-is

last commit was 1y ago; no CI workflows detected

  • Stale — last commit 1y ago
  • Non-standard license (Other) — review terms
  • No CI workflows detected
  • 11 active contributors
  • Distributed ownership (top contributor 44% of recent commits)
  • Other licensed
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms
  • 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

Signal-by-signal breakdown

nukeshadowsocks-windows
Stars3,72859,548
Last commit6mo ago1y ago
LicenseMITOther
Open issues120200
Has tests
Has CI
Test coverage2%12%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? nuke-build/nuke · shadowsocks/shadowsocks-windows

Ask AI about nuke-build/nuke vs shadowsocks/shadowsocks-windows

Open the chat with a comparison question pre-filled.