RepoPilot

grasscutters/grasscutter vs halo-dev/halo

Both showing Mixed signals — pick on fit, not health

As of September 2026, grasscutter and halo both show mixed maintenance signals. grasscutter last saw a commit 6 months ago with 23+ active contributors, while halo was committed to 1 week ago with 5+ active contributors. grasscutter is AGPL-3.0-licensed while halo 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.

grasscutters/grasscutter

Mixed

Slowing — last commit 6mo ago

ConcernsDependency

copyleft license (AGPL-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; dependency CVE scan unavailable

  • Slowing — last commit 6mo ago
  • AGPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit 6mo ago
  • 23+ active contributors
  • Distributed ownership (top contributor 30% of recent commits)
  • AGPL-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

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

Signal-by-signal breakdown

grasscutterhalo
Stars16,80439,649
Last commit6mo ago11d ago
LicenseAGPL-3.0GPL-3.0
Open issues152116
Has tests
Has CI
Test coverage0%31%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? grasscutters/grasscutter · halo-dev/halo

Ask AI about grasscutters/grasscutter vs halo-dev/halo

Open the chat with a comparison question pre-filled.