RepoPilot

quantumnous/new-api vs wei-shaw/sub2api

quantumnous/new-api shows stronger signals overall

As of September 2026, new-api shows healthier maintenance signals than sub2api. new-api rates Healthy overall while sub2api rates Mixed. new-api was committed to 1 week ago with 30+ active contributors, while sub2api was committed to 1 week ago with 20+ active contributors. new-api is AGPL-3.0-licensed while sub2api is LGPL-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.

quantumnous/new-api

Healthy

Strong maintenance signals

ConcernsDependency

copyleft license (AGPL-3.0) — review compatibility

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • AGPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 30+ active contributors
  • Distributed ownership (top contributor 32% 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 dependency CVEs from deps.dev and OpenSSF Scorecard

wei-shaw/sub2api

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (LGPL-3.0) — review compatibility

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Concentrated ownership — top contributor handles 50% of recent commits
  • LGPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 20 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, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

new-apisub2api
Stars47,20540,594
Last commit13d ago10d ago
LicenseAGPL-3.0LGPL-3.0
Open issues1,3333,080
Has tests
Has CI
Test coverage17%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeAC
Cycles00
Bottom-lineHealthy signalsMixed signals

Want the full analysis? quantumnous/new-api · wei-shaw/sub2api

Ask AI about quantumnous/new-api vs wei-shaw/sub2api

Open the chat with a comparison question pre-filled.