RepoPilot

ivanceras/svgbob vs tw93/pake

Both showing Mixed signals — pick on fit, not health

As of September 2026, svgbob and pake both show mixed maintenance signals. svgbob last saw a commit 4 months ago with 4+ active contributors, while pake was committed to 1 week ago with 15+ active contributors. svgbob is Apache-2.0-licensed while pake is GPL-3.0-licensed. pake has no known critical CVEs, while svgbob has 1.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

ivanceras/svgbob

Mixed

Slowing — last commit 5mo ago

MixedDependency

1 high-severity CVE in dependencies; top contributor handles 96% of recent commits

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

1 high-severity CVE in dependencies; Scorecard "Token-Permissions" is 0/10

  • Slowing — last commit 5mo ago
  • Small team — 4 contributors active in recent commits
  • Single-maintainer risk — top contributor 96% of recent commits
  • Scorecard: marked unmaintained (0/10)
  • 1 high-severity advisory in transitive deps
  • Last commit 5mo ago
  • 4 active contributors
  • Apache-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency Mixed to Healthy if: resolve the high-severity advisory
  • Deploy as-is Mixed to Healthy if: resolve the high-severity advisory

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

tw93/pake

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Concentrated ownership — top contributor handles 56% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 15 active contributors
  • GPL-3.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)

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

svgbobpake
Stars4,22361,322
Last commit4mo ago10d ago
LicenseApache-2.0GPL-3.0
Open issues390
Has tests
Has CI
Test coverage10%89%
Dependency CVEs0 critical · 1 high · 3 moderate · 0 lowNo CVEs
Architecture gradeAA
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? ivanceras/svgbob · tw93/pake

Ask AI about ivanceras/svgbob vs tw93/pake

Open the chat with a comparison question pre-filled.