RepoPilot

buresdv/cork vs caldis/mos

Both showing Mixed signals — pick on fit, not health

As of June 2026, cork and mos both show mixed maintenance signals. cork last saw a commit 1 month ago with 4+ active contributors, while mos last saw a commit 1 month ago with 1+ active contributor. 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.

buresdv/cork

Mixed

Missing license — unclear to depend on

ConcernsDependency

no license — legally unclear; top contributor handles 94% of recent commits…

ConcernsFork & modify

no license — can't legally use code; no tests detected

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code

  • Small team — 4 contributors active in recent commits
  • Single-maintainer risk — top contributor 94% of recent commits
  • No license — legally unclear to depend on
  • No test directory detected
  • Last commit 1d ago
  • 4 active contributors
  • CI configured

What would improve this?

  • Use as dependency ConcernsMixed if: publish a permissive license (MIT, Apache-2.0, etc.)
  • Fork & modify ConcernsMixed if: add a LICENSE file
  • Deploy as-is ConcernsMixed if: add a LICENSE file

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

caldis/mos

Mixed

Solo project — review before adopting

ConcernsDependency

non-standard license (Other); single-maintainer (no co-maintainers visible)

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Solo or near-solo (1 contributor active in recent commits)
  • Non-standard license (Other) — review terms
  • Last commit 1d ago
  • Other licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

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

Signal-by-signal breakdown

corkmos
Stars4,41220,047
Last commit1mo ago1mo ago
LicenseOther
Open issues67360
Has tests
Has CI
Test coverage100%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? buresdv/cork · caldis/mos

Ask AI about buresdv/cork vs caldis/mos

Open the chat with a comparison question pre-filled.