RepoPilot

pojavlauncherteam/pojavlauncher vs xuxueli/xxl-job

Both showing Mixed signals — pick on fit, not health

As of September 2026, pojavlauncher and xxl-job both show mixed maintenance signals. pojavlauncher last saw a commit 11 months ago with 9+ active contributors, while xxl-job last saw a commit 1 month ago with 4+ active contributors. pojavlauncher is LGPL-3.0-licensed while xxl-job 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.

pojavlauncherteam/pojavlauncher

Mixed

Slowing — last commit 8mo ago

ConcernsDependency

copyleft license (LGPL-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

last commit was 8mo ago; dependency CVE scan unavailable

  • Slowing — last commit 8mo ago
  • Concentrated ownership — top contributor handles 55% of recent commits
  • LGPL-3.0 is copyleft — check downstream compatibility
  • Last commit 8mo ago
  • 9 active contributors
  • LGPL-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

xuxueli/xxl-job

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; top contributor handles 95% 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 — 4 contributors active in recent commits
  • Single-maintainer risk — top contributor 95% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit 6w ago
  • 4 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 OpenSSF Scorecard

Signal-by-signal breakdown

pojavlauncherxxl-job
Stars8,92130,516
Last commit11mo ago1mo ago
LicenseLGPL-3.0GPL-3.0
Open issues12474
Has tests
Has CI
Test coverage0%12%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? pojavlauncherteam/pojavlauncher · xuxueli/xxl-job

Ask AI about pojavlauncherteam/pojavlauncher vs xuxueli/xxl-job

Open the chat with a comparison question pre-filled.