RepoPilot

heartcombo/devise vs pay-rails/pay

heartcombo/devise shows stronger signals overall

As of September 2026, devise shows healthier maintenance signals than pay. devise rates Healthy overall while pay rates Mixed. devise last saw a commit 2 months ago with 25+ active contributors, while pay was committed to 1 week ago with 16+ active contributors. Both use the MIT 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.

heartcombo/devise

Healthy

Strong maintenance signals

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

  • Concentrated ownership — top contributor handles 59% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 3mo ago
  • 25+ active contributors
  • MIT licensed
  • CI configured
  • Tests present

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

pay-rails/pay

Mixed

Single-maintainer risk — review before adopting

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; Scorecard "Token-Permissions" is 0/10…

  • Single-maintainer risk — top contributor 81% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 16 active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • 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

devisepay
Stars24,3562,252
Last commit2mo ago9d ago
LicenseMITMIT
Open issues2350
Has tests
Has CI
Test coverage100%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCA
Cycles00
Bottom-lineHealthy signalsMixed signals

Want the full analysis? heartcombo/devise · pay-rails/pay

Ask AI about heartcombo/devise vs pay-rails/pay

Open the chat with a comparison question pre-filled.