RepoPilot

kelseyhightower/confd vs sagernet/sing-box

Both showing Mixed signals — pick on fit, not health

As of September 2026, confd and sing-box both show mixed maintenance signals. confd last saw a commit 2 years ago with 26+ active contributors, while sing-box was committed to 5 days ago with 2+ active contributors. confd is MIT-licensed while sing-box 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.

kelseyhightower/confd

Mixed

Stale — last commit 2y ago

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.

MixedDeploy as-is

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

  • Stale — last commit 2y ago
  • Concentrated ownership — top contributor handles 59% of recent commits
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 2 moderate-severity advisories on direct dependencies
  • 26+ active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • 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 dependency CVEs from deps.dev and OpenSSF Scorecard

sagernet/sing-box

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; top contributor handles 99% of recent commits

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

  • Small team — 2 contributors active in recent commits
  • Single-maintainer risk — top contributor 99% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit 2d ago
  • 2 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 dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

confdsing-box
Stars8,43037,880
Last commit2y ago5d ago
LicenseMITGPL-3.0
Open issues178327
Has tests
Has CI
Test coverage0%12%
Dependency CVEs0 critical · 0 high · 2 moderate · 0 low0 critical · 0 high · 9 moderate · 0 low
Architecture gradeA
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? kelseyhightower/confd · sagernet/sing-box

Ask AI about kelseyhightower/confd vs sagernet/sing-box

Open the chat with a comparison question pre-filled.