RepoPilot

aahung/unshaky vs caldis/mos

Both showing Mixed signals — pick on fit, not health

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

aahung/unshaky

Mixed

Stale — last commit 3y ago

MixedDependency

last commit was 3y ago; no tests detected in the complete Git tree…

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

last commit was 3y ago; Scorecard "Branch-Protection" is 0/10…

  • Stale — last commit 3y ago
  • Concentrated ownership — top contributor handles 75% of recent commits
  • No tests detected in the complete Git tree
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 13 active contributors
  • MIT licensed
  • CI configured

What would improve this?

  • Use as dependency Mixed to Healthy if: 1 commit in the last 365 days
  • Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days

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

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

Signal-by-signal breakdown

unshakymos
Stars3,08521,344
Last commit2y ago27d ago
LicenseMITUnknown
Open issues19403
Has testsNo
Has CI
Test coverage0%14%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? aahung/unshaky · caldis/mos

Ask AI about aahung/unshaky vs caldis/mos

Open the chat with a comparison question pre-filled.