RepoPilot

ruby/ruby vs stefankroes/ancestry

Both showing Healthy signals — pick on fit, not health

As of June 2026, ruby and ancestry both show healthy maintenance signals. ruby last saw a commit 1 month ago with 27+ active contributors, while ancestry last saw a commit 1 month ago with 2+ active contributors. ruby is Other-licensed while ancestry is MIT-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.

ruby/ruby

Healthy

Healthy across the board

ConcernsDependency

non-standard license (Other)

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Non-standard license (Other) — review terms
  • Last commit today
  • 27+ active contributors
  • Distributed ownership (top contributor 40% of recent commits)
  • Other licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

stefankroes/ancestry

Healthy

Healthy across all four use cases

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Small team — 2 contributors active in recent commits
  • Single-maintainer risk — top contributor 99% of recent commits
  • Last commit 6d ago
  • 2 active contributors
  • MIT licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

rubyancestry
Stars23,5733,858
Last commit1mo ago1mo ago
LicenseOtherMIT
Open issues58529
Has tests
Has CI
Test coverage18%100%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? ruby/ruby · stefankroes/ancestry

Ask AI about ruby/ruby vs stefankroes/ancestry

Open the chat with a comparison question pre-filled.