RepoPilot

halo-dev/halo vs tencent/shadow

Both showing Mixed signals — pick on fit, not health

As of September 2026, halo and shadow both show mixed maintenance signals. halo was committed to 2 weeks ago with 5+ active contributors, while shadow last saw a commit 5 months ago with 11+ active contributors. halo is GPL-3.0-licensed while shadow is BSD-3-Clause-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.

halo-dev/halo

Mixed

Mixed signals — read the receipts

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 "Token-Permissions" is 0/10; dependency CVE scan unavailable

  • Concentrated ownership — top contributor handles 60% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Last commit today
  • 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)

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

tencent/shadow

Mixed

Slowing — last commit 5mo ago

MixedDependency

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; dependency CVE scan unavailable

  • Slowing — last commit 5mo ago
  • Single-maintainer risk — top contributor 83% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 5mo ago
  • 11 active contributors
  • BSD-3-Clause licensed
  • CI configured
  • Tests present

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

Signal-by-signal breakdown

haloshadow
Stars39,6497,786
Last commit15d ago5mo ago
LicenseGPL-3.0BSD-3-Clause
Open issues11669
Has tests
Has CI
Test coverage31%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? halo-dev/halo · tencent/shadow

Ask AI about halo-dev/halo vs tencent/shadow

Open the chat with a comparison question pre-filled.