RepoPilot

heartcombo/devise vs shrinerb/shrine

Both showing Healthy signals — pick on fit, not health

As of September 2026, devise and shrine both show healthy maintenance signals. devise last saw a commit 2 months ago with 25+ active contributors, while shrine last saw a commit 2 months ago with 22+ 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

shrinerb/shrine

Healthy

Strong maintenance signals

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

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

  • Concentrated ownership — top contributor handles 75% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 5w ago
  • 22+ 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 dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

deviseshrine
Stars24,3563,286
Last commit2mo ago2mo ago
LicenseMITMIT
Open issues2351
Has tests
Has CI
Test coverage100%89%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCA
Cycles00
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? heartcombo/devise · shrinerb/shrine

Ask AI about heartcombo/devise vs shrinerb/shrine

Open the chat with a comparison question pre-filled.