RepoPilot

caldis/mos vs runjuu/inputsourcepro

Both showing Mixed signals — pick on fit, not health

As of September 2026, mos and inputsourcepro both show mixed maintenance signals. mos was committed to 3 weeks ago with 9+ active contributors, while inputsourcepro last saw a commit 4 months ago with 8+ 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.

caldis/mos

Mixed

Single-maintainer risk — review before adopting

MixedDependency

license evidence incomplete; dependency CVE scan unavailable

MixedFork & modify

license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; license evidence incomplete…

  • Single-maintainer risk — top contributor 88% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 3w ago
  • 9 active contributors
  • CI configured
  • Tests present

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

runjuu/inputsourcepro

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; test evidence incomplete…

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

dependency CVE scan unavailable

  • Concentrated ownership — top contributor handles 74% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Last commit 1d ago
  • 8 active contributors
  • GPL-3.0 licensed
  • CI configured

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

Signal-by-signal breakdown

mosinputsourcepro
Stars21,3443,095
Last commit27d ago4mo ago
LicenseUnknownGPL-3.0
Open issues40351
Has testsUnknown
Has CI
Test coverage14%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? caldis/mos · runjuu/inputsourcepro

Ask AI about caldis/mos vs runjuu/inputsourcepro

Open the chat with a comparison question pre-filled.