RepoPilot

chrisbanes/android-pulltorefresh vs dromara/sa-token

Both showing Mixed signals — pick on fit, not health

As of September 2026, android-pulltorefresh and sa-token both show mixed maintenance signals. android-pulltorefresh last saw a commit 8 years ago with 7+ active contributors, while sa-token was committed to 1 week ago with 1+ active contributor. Both use the Apache-2.0 license. 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.

chrisbanes/android-pulltorefresh

Mixed

Stale — last commit 9y ago

ConcernsDependency

last commit was 9y ago; top contributor handles 93% of recent commits…

MixedFork & modify

test evidence incomplete; CI evidence incomplete…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 9y ago; CI evidence incomplete…

  • Stale — last commit 9y ago
  • Single-maintainer risk — top contributor 93% of recent commits
  • 7 active contributors
  • Apache-2.0 licensed

What would improve this?

  • Use as dependency Concerns to Mixed if: 1 commit in the last 365 days
  • 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

dromara/sa-token

Mixed

Solo project — review before adopting

MixedDependency

single-maintainer (no co-maintainers visible); no CI workflows detected…

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; no CI workflows detected…

  • Solo or near-solo (1 contributor active in recent commits)
  • No CI workflows detected
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • Apache-2.0 licensed
  • Tests present

What would improve this?

  • Use as dependency Mixed to Healthy if: onboard a second core maintainer
  • 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

android-pulltorefreshsa-token
Stars8,65419,037
Last commit8y ago9d ago
LicenseApache-2.0Apache-2.0
Open issues29107
Has testsUnknown
Has CIUnknownNo
Test coverage0%61%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? chrisbanes/android-pulltorefresh · dromara/sa-token

Ask AI about chrisbanes/android-pulltorefresh vs dromara/sa-token

Open the chat with a comparison question pre-filled.