RepoPilot

priler/jarvis vs tw93/pake

Both showing Mixed signals — pick on fit, not health

As of September 2026, jarvis and pake both show mixed maintenance signals. jarvis last saw a commit 6 months ago with 7+ active contributors, while pake was committed to 5 days ago with 15+ active contributors. 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.

priler/jarvis

Mixed

Single-maintainer risk — review before adopting

MixedDependency

top contributor handles 92% of recent commits; CI evidence incomplete…

MixedFork & modify

CI evidence incomplete; license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

CI evidence incomplete; license evidence incomplete…

  • Single-maintainer risk — top contributor 92% of recent commits
  • Last commit 3mo ago
  • 7 active contributors
  • Tests present

What would improve this?

  • Use as dependency Mixed to Healthy if: diversify commit ownership (top <90%)

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

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

jarvispake
Stars2,78561,322
Last commit6mo ago5d ago
LicenseUnknownGPL-3.0
Open issues140
Has tests
Has CIUnknown
Test coverage6%89%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? priler/jarvis · tw93/pake

Ask AI about priler/jarvis vs tw93/pake

Open the chat with a comparison question pre-filled.