RepoPilot

chriskiehl/gooey vs d4vinci/scrapling

Both showing Mixed signals — pick on fit, not health

As of September 2026, gooey and scrapling both show mixed maintenance signals. gooey last saw a commit 5 months ago with 24+ active contributors, while scrapling was committed to 1 week ago with 7+ active contributors. gooey is MIT-licensed while scrapling is BSD-3-Clause-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.

chriskiehl/gooey

Mixed

Slowing — last commit 5mo ago

MixedDependency

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

  • Slowing — last commit 5mo ago
  • Concentrated ownership — top contributor handles 61% of recent commits
  • No CI workflows detected
  • Scorecard: default branch unprotected (0/10)
  • Last commit 5mo ago
  • 24+ active contributors
  • MIT licensed
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report); wire up GitHub Actions or equivalent

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

d4vinci/scrapling

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; 8 cyclic import chains — pervasive coupling

  • Single-maintainer risk — top contributor 88% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 3d ago
  • 7 active contributors
  • BSD-3-Clause 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

gooeyscrapling
Stars21,89178,796
Last commit5mo ago8d ago
LicenseMITBSD-3-Clause
Open issues18315
Has tests
Has CINo
Test coverage65%98%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeBC
Cycles38
Bottom-lineMixed signalsMixed signals

Want the full analysis? chriskiehl/gooey · d4vinci/scrapling

Ask AI about chriskiehl/gooey vs d4vinci/scrapling

Open the chat with a comparison question pre-filled.