RepoPilot

crmne/ruby_llm vs splitrb/split

Both showing Mixed signals — pick on fit, not health

As of September 2026, ruby_llm and split both show mixed maintenance signals. ruby_llm was committed to 1 week ago with 6+ active contributors, while split was committed to 4 days ago with 8+ 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.

crmne/ruby_llm

Mixed

Single-maintainer risk — review before adopting

MixedDependency

top contributor handles 94% of recent commits; 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

  • Single-maintainer risk — top contributor 94% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 6 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

splitrb/split

Mixed

Single-maintainer risk — review before adopting

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

  • Single-maintainer risk — top contributor 88% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 8 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

ruby_llmsplit
Stars4,3372,707
Last commit7d ago4d ago
LicenseMITMIT
Open issues1235
Has tests
Has CI
Test coverage100%89%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? crmne/ruby_llm · splitrb/split

Ask AI about crmne/ruby_llm vs splitrb/split

Open the chat with a comparison question pre-filled.